https://bugzilla.redhat.com/show_bug.cgi?id=2263999
--- Comment #12 from Ben Beasley <code(a)musicinmybrain.net> ---
(In reply to Sandro from comment #11)
I agree. With Koji honoring ExcludeArch for selecting builders all
would be
fine. I thought with using ExclusiveArch, preferably with a macro that
defines 64-bit arches not including noarch, koji might be wrangled into
submission. Of course, fixing the way Koji selects builders for noarch
packages is the preferred solution.
So, forgive me if you’re not confused or misled in the way I think you might
be, but
BuildArch: noarch
ExcludeArch: %{ix86}
does work today in the way you would expect.
The problem is that it shouldn’t be needed: noarch packages *should not* block
arched packages from dropping i686. A lot of arched packages would be leaf
packages, if not for a few dozen noarch Python packages that depend on them.
Because noarch packages *could* be assigned to an i686 builder, their
dependencies have to maintain i686 support, or they’ll FTBFS randomly. But
adding ExcludeArch to all those noarch packages is tedious, so it tends not to
happen, and so everything ends up having to keep i686 support. If noarch
packages were just never built on i686 by policy, then none of that would be
necessary, and we would only have to worry about arched dependent packages.
That’s what
https://pagure.io/koji/issue/3809 is about.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2263999
Report this comment as SPAM:
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=rep...