Learn more about these different git repos.
Other Git URLs
When we update Python to a new version (3.N+1), we mass rebuild all the Python packages in Fedora and we pummel them until they are either rebuilt or retired.
See https://fedoraproject.org/wiki/SIGs/Python/UpgradingPython for the current procedure, namely https://fedoraproject.org/wiki/SIGs/Python/UpgradingPython#Rebuild_everything_else
We do that in a side tag. We use repoquery to figure out what packages still need to be rebuilt.
We don't currently rebuild modules that depend on Python at all. We don't know how:
We don't know how to query all modular packages on rawhide to figure out which need to be rebuilt.
We don't know how to "rebuild such modules in the side tag" (or how achieve similar results). This is potentially especially problematic, if non-modular packages BuildRequire affected modular packages (even transitively).
See this e-mail on devel and the thread that is below that (don't know how to link a subthread, sorry).
Note: When I say "we", I mean the Fedora's Python SIG and/or Red Hat Python Maint, but it is currently usually done by me.
Given the recent synchronization of Python and Fedora schedules, we will most likely be usually doing this right after branching. This is both bad and good:
However, I would rather not use this as a long term strategy.
Metadata Update from @sgallagh:
- Issue priority set to: high
- Issue tagged with: Meeting
Metadata Update from @asamalik:
- Issue untagged with: Meeting
- Issue tagged with: needs-design
to comment on this ticket.