#8529 F31 system wide change: stop composing and distributing i686 trees
Closed: Fixed 4 years ago by mohanboddu. Opened 4 years ago by kevin.

Please consider the release engineering impact of this change proposal targeting Fedora 31:

https://fedoraproject.org/wiki/Changes/Noi686Repositories


If we stop composing Modules tree, then nobody would be able to build:

  1. modules (not sure if it is a problem, but if people want to debug any build failures they won't be able to).
  2. packages which rely on default modules (I know that "Ursa Prime" is not a thing yet, but once it is available - it will be broken for i686 users).

This will also make it impossible for people to locally do multi-lib builds. It will remove COPR’s ability to do the same.

If we stop composing Modules tree, then nobody would be able to build:

modules (not sure if it is a problem, but if people want to debug any build failures they won't be able to).

I don't think this is the case. We should still be able to build i686 modules. Does mbs use non koji produced repos?

packages which rely on default modules (I know that "Ursa Prime" is not a thing yet, but once it is available - it will be broken for i686 users).

I also don't think so. koji will still have a i686 buildroot and we will still have i686 modules to add to it.

This will also make it impossible for people to locally do multi-lib builds. It will remove COPR’s ability to do the same.

Depends on what you mean by 'locally'. But lets discuss this on the list better than here...

Actually, thinking about it, I don't see any reason to keep making i686 modules... unless:

  • Do we allow x86_64 users to install i686 modules?
  • Do modules even have multilib support? (if so, I guess we use i686 modules to do that), but I didn't think they did.

If there's no i686 installs (because we no longer make media or ship a kernel), is there a reason to make i686 modules?

For visibility, FESCo approved this change proposal today.

Currently, when a release reaches EOL, the repos for that release (eventually) move over to archives.fedoraproject.org. Will this now be done for the koji buildroot repos too?

I only see repos in https://kojipkgs.fedoraproject.org/repos/ going back to f24; have the older ones been garbage-collected, gone forever, and will that eventually happen to f31-build and future repos?

Currently, when a release reaches EOL, the repos for that release (eventually) move over to archives.fedoraproject.org. Will this now be done for the koji buildroot repos too?

Nope.

I only see repos in https://kojipkgs.fedoraproject.org/repos/ going back to f24; have the older ones been garbage-collected, gone forever, and will that eventually happen to f31-build and future repos?

Yes, they are no longer made, but they are not gone forever, koji records all the packages that were in the buildroot when a package was built, and you can reconstruct that exact buildroot and (re)build the package.

This work is done. Closing the ticket.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
- Issue tagged with: change-ack, f31

4 years ago

Login to comment on this ticket.

Metadata