Bug 1221655

Summary: nothing provides 'gfxboot-branding-openSUSE' needed by the to be installed openSUSEway-0.16.0-1.3.noarch
Product: [openSUSE] openSUSE Tumbleweed Reporter: Zaoliang Luo <zluo>
Component: OtherAssignee: Denys Kondratenko <stdden>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: dimstar
Version: Current   
Target Milestone: ---   
Hardware: aarch64   
OS: openSUSE Tumbleweed   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Zaoliang Luo 2024-03-19 07:49:42 UTC 
localhost:~ # zypper se openSUSEway
Loading repository data...
Reading installed packages...

S | Name                 | Summary                                          | Type
--+----------------------+--------------------------------------------------+--------
  | openSUSEway          | The openSUSEway desktop environment meta package | package
  | openSUSEway          | The openSUSEway desktop environment pattern      | pattern
  | patterns-openSUSEway | The openSUSEway desktop environment pattern      | package
localhost:~ # zypper in openSUSEway
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: nothing provides 'gfxboot-branding-openSUSE' needed by the to be installed openSUSEway-0.16.0-1.3.noarch
 Solution 1: do not install openSUSEway-0.16.0-1.3.noarch
 Solution 2: break openSUSEway-0.16.0-1.3.noarch by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/c/d/?] (c):
Comment 1 Denys Kondratenko 2024-03-19 14:04:31 UTC 
yeah... That package is not present on aarch.
https://build.opensuse.org/package/show/openSUSE:Factory/branding-openSUSE

could you please press ignore and see if there are any other packages that aren't present for aarch?
Comment 2 Denys Kondratenko 2024-03-19 14:07:22 UTC 
it is actually noarch package. What repos do you have in a system ?

zypper lr -d
Comment 3 Dominique Leuenberger 2024-03-19 14:15:08 UTC 
(In reply to Denys Kondratenko from comment #2)
> it is actually noarch package. What repos do you have in a system ?
> 
> zypper lr -d

This will likely be the repo created by openSUSE:Factory:ARM

The ports are all built independently, binaries from .e.g openSUSE:Factory are not inherited to users of openSUSE:Factory:ARM ( different release cadences -unlike on Leap 15.x)

> osc ls -b openSUSE:Factory:ARM branding-openSUSE

gfxboot-branding-openSUSE does indeed not exist in :ARM.
(this in turn makes openSUSEway not really being noarch - as it must adapt to architectures)
Comment 4 Denys Kondratenko 2024-03-19 14:25:17 UTC 
> The ports are all built independently, binaries from .e.g openSUSE:Factory
> are not inherited to users of openSUSE:Factory:ARM ( different release
> cadences -unlike on Leap 15.x)
> 
> > osc ls -b openSUSE:Factory:ARM branding-openSUSE
> 
> gfxboot-branding-openSUSE does indeed not exist in :ARM.
> (this in turn makes openSUSEway not really being noarch - as it must adapt
> to architectures)

OK, thanks!

yes, we need to add aarch support.

Any guidelines for that? Like special macros?

https://github.com/openSUSE/openSUSEway/issues/158
Comment 5 Dominique Leuenberger 2024-03-19 14:28:20 UTC 
openSUSe-branding uses this construct to define if gfxboot is available (and thus branding for it should be created)

%ifarch x86_64 %{ix86}
%define gfxboot 1
%endif


In your case, you can probably just wrap the dependency, like

%ifarch x86_64 %{ix86}
Requires:       gfxboot-branding-openSUSE
%endif
Comment 6 Denys Kondratenko 2024-03-20 06:20:40 UTC 
Overall there are more issues that just gfx-branding, many openSUSEway dependencies are absent. So currently aarch64 is not supported by openSUSEway.

Development and feedback can be done in upstream: https://github.com/openSUSE/openSUSEway/issues/158