[opensuse-packaging] factory-repo-checker and noarch packages
Hi all, hi Stephan, I am trying to submit quilt to openSUSE:Factory. It gets rejected by factory-repo-checker with the reason: quilt is disabled or does not build against factory. Please fix and resubmit Quilt is enabled against openSUSE_Factory in devel:tools:scm, but only for x86_64. It is a noarch package so I see no reason to waste build resources to build it on more than one architecture. I suspect this is the reason for the reject above. Can we please fix factory-repo-checker so that it is happy with noarch packages as long as they are enabled on at least one architecture and do not fail to build on any architecture? Thanks, -- Jean Delvare Suse L3 Support -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Am 09.12.2013 19:09, schrieb Jean Delvare:
Can we please fix factory-repo-checker so that it is happy with noarch packages as long as they are enabled on at least one architecture and do not fail to build on any architecture? Yeah, I'm sure we can. It's here: https://github.com/coolo/factory-auto/ Just fork it and do a pull request.
Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Monday 2013-12-09 19:09, Jean Delvare wrote:
I am trying to submit quilt to openSUSE:Factory. It gets rejected by factory-repo-checker with the reason:
quilt is disabled or does not build against factory. Please fix and resubmit
Quilt is enabled against openSUSE_Factory in devel:tools:scm, but only for x86_64. It is a noarch package so I see no reason to waste build resources to build it on more than one architecture.
I remember that bs_sched used to make a significant distinction between BS architectures and RPM file architectures. If you disabled building quilt.i586, there would be no quilt.noarch.rpm in /srv/obs/build/openSUSE:Factory/standard/i586/quilt, and other packages that BuildRequire quilt would not start and instead show "unresolvable". -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hi Jan, Le Monday 09 December 2013 à 20:04 +0100, Jan Engelhardt a écrit :
On Monday 2013-12-09 19:09, Jean Delvare wrote:
Quilt is enabled against openSUSE_Factory in devel:tools:scm, but only for x86_64. It is a noarch package so I see no reason to waste build resources to build it on more than one architecture.
I remember that bs_sched used to make a significant distinction between BS architectures and RPM file architectures. If you disabled building quilt.i586, there would be no quilt.noarch.rpm in /srv/obs/build/openSUSE:Factory/standard/i586/quilt, and other packages that BuildRequire quilt would not start and instead show "unresolvable".
Oh well, I'll just re-enable the i586 build then. Thanks for the warning. But it would be great to encourage noarch packages to be built only once, rather than on all architectures. That would save a lot of build power. Noarch packages may be small and fast to build on average, but they still account for over 13% of all packages on my openSUSE 13.1 system. -- Jean Delvare Suse L3 Support -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tuesday 2013-12-10 09:05, Jean Delvare wrote:
I remember that bs_sched used to make a significant distinction between BS architectures and RPM file architectures. If you disabled building quilt.i586, there would be no quilt.noarch.rpm in /srv/obs/build/openSUSE:Factory/standard/i586/quilt, and other packages that BuildRequire quilt would not start and instead show "unresolvable".
Noarch packages may be small and fast to build on average, but they still account for over 13% of all packages on my openSUSE 13.1 system.
Not all .noarch.rpm files stem from a package that has "BuildArch: noarch" in the main subpackage. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hi Jan, Le Thursday 12 December 2013 à 21:46 +0100, Jan Engelhardt a écrit :
On Tuesday 2013-12-10 09:05, Jean Delvare wrote:
Noarch packages may be small and fast to build on average, but they still account for over 13% of all packages on my openSUSE 13.1 system.
Not all .noarch.rpm files stem from a package that has "BuildArch: noarch" in the main subpackage.
That's true, but the noarch subpackages should be the same in all builds. So we could decide that only one arch (say x86_64) builds them. I won't take care of it, it's not my area and I'm busy enough as is. All I'm saying is that it should be possible. -- Jean Delvare Suse L3 Support -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 13.12.2013 10:45, Jean Delvare wrote:
I won't take care of it, it's not my area and I'm busy enough as is. All I'm saying is that it should be possible.
Happy Hackweek X :) Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Fri, 13 Dec 2013 10:45, Jean Delvare
Le Thursday 12 December 2013 à 21:46 +0100, Jan Engelhardt a écrit :
On Tuesday 2013-12-10 09:05, Jean Delvare wrote:
Noarch packages may be small and fast to build on average, but they still account for over 13% of all packages on my openSUSE 13.1 system.
Not all .noarch.rpm files stem from a package that has "BuildArch: noarch" in the main subpackage.
That's true, but the noarch subpackages should be the same in all builds. So we could decide that only one arch (say x86_64) builds them.
I won't take care of it, it's not my area and I'm busy enough as is. All I'm saying is that it should be possible.
May I trow an Idea in here? - When You touch up that logic, how about the following: If only ONE Arch / Sub-arch is selected, this arch also builds the 'noarch' stuff, no matter what arch? {see: PPC, ARM(32/64), iA(32/64)} Also, if we make 'noarch' as direct selectable arch available, OBS could select the arch with the most resources available to build the package in question. - Yamaban.
participants (4)
-
Jan Engelhardt -
Jean Delvare -
Stephan Kulow -
Yamaban