Hi, Am Freitag, 13. August 2021, 10:36:30 CEST schrieb Takashi Iwai:
On Thu, 12 Aug 2021 17:48:16 +0200, Fabian Vogt wrote:
Hi,
Am Donnerstag, 12. August 2021, 17:38:38 CEST schrieb Adrian Schröter:
On Donnerstag, 12. August 2021, 17:32:57 CEST Antonio Larrosa wrote:
Hi,
Someone mentioned that the pipewire *-32bit packages were not being generated in multimedia:libs for Leap (even if pipewire has a proper baselibs.conf file).
I noticed then that the -32bit packages were not being generated in multimedia:libs for any package at all and it seems to be caused by the Leap repositories having only the x86_64 arch in the project's meta. But afaik, we don't want to publish i586 packages for Leap, right?
Is the correct way to fix this to add the i586 arch in the meta and then disable the "Publish flag" for the i586 arch? or is there some other recommended way?
should work.
There is not much alternative at least when you do not want to go via additional steps like product building.
Note that the way -32bit packages are enabled in Leap is through the prjconf:
%ifarch i586 i686 BuildFlags: onlybuild:pipewire %endif
Otherwise everything will be "excluded".
Alternatively, add i586 to openSUSE_Leap_15.3, but disable the build for all as default, and selectively enable the build for pipewire and other library packages without publishing flag -- I suppose it would work?
As long as the repository builds against SLE/Leap, the prjconf with its onlybuild flags is pulled in and the build enable flag won't suffice.
IMO, it's less obscure than prjconf and even package maintainer can change, so likely suitable for a devel project.
Yep, onlybuild is not great. It was used instead of build disabling because it can be defined once in the prjconf instead of in every project (main project, stagings, devel prj, maintenance, ...) separately. Cheers, Fabian
thanks,
Takashi