#11163 Do not use x86 builders for noarch packages
Closed: Fixed a year ago by kevin. Opened a year ago by mattia.

Describe what you would like us to do:

When building noarch packages we must avoid using builders on x86 architectures, since some packages are no more available there.

For example, I've been trying to build an update for staging Bodhi, but the build fails because skopeo is not available on x86 builders:
https://koji.fedoraproject.org/koji/buildinfo?buildID=2165145

When do you need this to be done by? (YYYY/MM/DD)

The sooner, the better :-)


Just to be clear, this is about 32 bit x86 architectures versus 64 bit x86?

This is not something that can be done on the koji level.

You need to add a

ExclusiveArch: %{golang_arches_future}

to match skopeo, or a

ExcludeArch: i686

It should do the right thing, even on noarch packages these days.

Just to be clear, this is about 32 bit x86 architectures versus 64 bit x86?

I mean, using a 32 bit x86 vm builder for building a noarch package.

This is not something that can be done on the koji level.

You need to add a

ExclusiveArch: %{golang_arches_future}

to match skopeo, or a

ExcludeArch: i686

It should do the right thing, even on noarch packages these days.

I'll try.
I also wonder why bodhi specfile has BRs against dnf, skopeo and createrepo... it seems odd. I'll try to remove them.

Feel free to close the ticket if you think there's nothing to be adjusted. I think it's uncommon for noarch packages to require arched packages as BuildRequires, but I'll leave you the choice.

Could those be there for tests?

But yeah, I think it can be adjusted in the spec... if there's something further feel free to reopen.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.

Metadata