Heads up: Another targeted mass rebuild of ~4k Python packages will happen in Fedora 43+
Hello Fedora packagers.
Unfortunately, we need to rebuild all Fedora 43 (and 44) packages with Python 3.14 .pyc files. To obtain a list, use:
$ repoquery --repo=rawhide --refresh -f *.cpython-314.pyc --source (3931 unique packages)
This is needed because Python 3.14 just bumped the pyc "magic number" (version) due to a severe bugfix [1].
Packages with old .pyc files will have slower import times and might report AVC denials in restricted contexts. However, they remain functional, there is no need to panic.
The plan, as of now, is:
1. Either wait for Python 3.14.0rc2 release or backport the change. 2. Wait for the Fedora 43 branching to finish. 3. Bump and build all 3931 packages in rawhide (except kernel). 4. FF-merge into f43 and build all packages that match the criteria: a) the rawhide and f43 branches were not different before 3. b) they have no update stuck in bodhi/gating. 5. Open bugzillas for the remaining packages (failed or skipped rebuild).
The rebuild can be done in any order (i.e. all at once) and does not need to happen in a side tag.
I will follow up when things start moving. Let me know if I should alter the plan somehow.
[1] https://github.com/python/cpython/pull/137427
On 12. 08. 25 13:00, Miro Hrončok wrote:
Hello Fedora packagers.
Unfortunately, we need to rebuild all Fedora 43 (and 44) packages with Python 3.14 .pyc files. To obtain a list, use:
$ repoquery --repo=rawhide --refresh -f *.cpython-314.pyc --source (3931 unique packages)
This is needed because Python 3.14 just bumped the pyc "magic number" (version) due to a severe bugfix [1].
Packages with old .pyc files will have slower import times and might report AVC denials in restricted contexts. However, they remain functional, there is no need to panic.
The plan, as of now, is:
1. Either wait for Python 3.14.0rc2 release or backport the change.
Let's wait. rc2 should be released on Thursday.
https://discuss.python.org/t/early-3-14-0-rc2-and-extra-rc3/102151
2. Wait for the Fedora 43 branching to finish.
That's more or less done now it seems and will likely officially be done by Thursday.
3. Bump and build all 3931 packages in rawhide (except kernel). 4. FF-merge into f43 and build all packages that match the criteria: a) the rawhide and f43 branches were not different before 3. b) they have no update stuck in bodhi/gating.
Considering the rebuilds will go trough bodhi, we don't actually need to do that :)
5. Open bugzillas for the remaining packages (failed or skipped rebuild).
The rebuild can be done in any order (i.e. all at once) and does not need to happen in a side tag.
I will follow up when things start moving. Let me know if I should alter the plan somehow.
On 12. 08. 25 22:22, Miro Hrončok wrote:
On 12. 08. 25 13:00, Miro Hrončok wrote:
Hello Fedora packagers.
Unfortunately, we need to rebuild all Fedora 43 (and 44) packages with Python 3.14 .pyc files. To obtain a list, use:
$ repoquery --repo=rawhide --refresh -f *.cpython-314.pyc --source (3931 unique packages)
This is needed because Python 3.14 just bumped the pyc "magic number" (version) due to a severe bugfix [1].
Packages with old .pyc files will have slower import times and might report AVC denials in restricted contexts. However, they remain functional, there is no need to panic.
The plan, as of now, is:
1. Either wait for Python 3.14.0rc2 release or backport the change.
Let's wait. rc2 should be released on Thursday.
https://discuss.python.org/t/early-3-14-0-rc2-and-extra-rc3/102151
2. Wait for the Fedora 43 branching to finish.
That's more or less done now it seems and will likely officially be done by Thursday.
3. Bump and build all 3931 packages in rawhide (except kernel). 4. FF-merge into f43 and build all packages that match the criteria: a) the rawhide and f43 branches were not different before 3. b) they have no update stuck in bodhi/gating.
Considering the rebuilds will go trough bodhi, we don't actually need to do that :)
5. Open bugzillas for the remaining packages (failed or skipped rebuild).
The rebuild can be done in any order (i.e. all at once) and does not need to happen in a side tag.
I will follow up when things start moving. Let me know if I should alter the plan somehow.
The current plan is, for each affected package:
1. check if a f44 build is running, abort if so 2. check if the latest f44 build is completed but tagged in a side tag only, abort if so 3. check if rawhide and f43 branches are different, abort f43 build if so 4. check builds for f43 as we did in first two steps, abort f43 is so 5. bump + push + build (and optionally ff merge + push + build f43)
All builds will go trough bodhi, so any fatal gating failures would not be ignored.
On 14. 08. 25 12:02, Miro Hrončok wrote:
On 12. 08. 25 22:22, Miro Hrončok wrote:
On 12. 08. 25 13:00, Miro Hrončok wrote:
Hello Fedora packagers.
Unfortunately, we need to rebuild all Fedora 43 (and 44) packages with Python 3.14 .pyc files. To obtain a list, use:
$ repoquery --repo=rawhide --refresh -f *.cpython-314.pyc --source (3931 unique packages)
This is needed because Python 3.14 just bumped the pyc "magic number" (version) due to a severe bugfix [1].
Packages with old .pyc files will have slower import times and might report AVC denials in restricted contexts. However, they remain functional, there is no need to panic.
The plan, as of now, is:
1. Either wait for Python 3.14.0rc2 release or backport the change.
Let's wait. rc2 should be released on Thursday.
https://discuss.python.org/t/early-3-14-0-rc2-and-extra-rc3/102151
2. Wait for the Fedora 43 branching to finish.
That's more or less done now it seems and will likely officially be done by Thursday.
3. Bump and build all 3931 packages in rawhide (except kernel). 4. FF-merge into f43 and build all packages that match the criteria: a) the rawhide and f43 branches were not different before 3. b) they have no update stuck in bodhi/gating.
Considering the rebuilds will go trough bodhi, we don't actually need to do that :)
5. Open bugzillas for the remaining packages (failed or skipped rebuild).
The rebuild can be done in any order (i.e. all at once) and does not need to happen in a side tag.
I will follow up when things start moving. Let me know if I should alter the plan somehow.
The current plan is, for each affected package:
1. check if a f44 build is running, abort if so 2. check if the latest f44 build is completed but tagged in a side tag only, abort if so 3. check if rawhide and f43 branches are different, abort f43 build if so 4. check builds for f43 as we did in first two steps, abort f43 is so 5. bump + push + build (and optionally ff merge + push + build f43)
All builds will go trough bodhi, so any fatal gating failures would not be ignored.
The rebuild has started.
On 15. 08. 25 12:41, Miro Hrončok wrote:
On 14. 08. 25 12:02, Miro Hrončok wrote:
On 12. 08. 25 22:22, Miro Hrončok wrote:
On 12. 08. 25 13:00, Miro Hrončok wrote:
Hello Fedora packagers.
Unfortunately, we need to rebuild all Fedora 43 (and 44) packages with Python 3.14 .pyc files. To obtain a list, use:
$ repoquery --repo=rawhide --refresh -f *.cpython-314.pyc --source (3931 unique packages)
This is needed because Python 3.14 just bumped the pyc "magic number" (version) due to a severe bugfix [1].
Packages with old .pyc files will have slower import times and might report AVC denials in restricted contexts. However, they remain functional, there is no need to panic.
The plan, as of now, is:
1. Either wait for Python 3.14.0rc2 release or backport the change.
Let's wait. rc2 should be released on Thursday.
https://discuss.python.org/t/early-3-14-0-rc2-and-extra-rc3/102151
2. Wait for the Fedora 43 branching to finish.
That's more or less done now it seems and will likely officially be done by Thursday.
3. Bump and build all 3931 packages in rawhide (except kernel). 4. FF-merge into f43 and build all packages that match the criteria: a) the rawhide and f43 branches were not different before 3. b) they have no update stuck in bodhi/gating.
Considering the rebuilds will go trough bodhi, we don't actually need to do that :)
5. Open bugzillas for the remaining packages (failed or skipped rebuild).
The rebuild can be done in any order (i.e. all at once) and does not need to happen in a side tag.
I will follow up when things start moving. Let me know if I should alter the plan somehow.
The current plan is, for each affected package:
1. check if a f44 build is running, abort if so 2. check if the latest f44 build is completed but tagged in a side tag only, abort if so 3. check if rawhide and f43 branches are different, abort f43 build if so 4. check builds for f43 as we did in first two steps, abort f43 is so 5. bump + push + build (and optionally ff merge + push + build f43)
All builds will go trough bodhi, so any fatal gating failures would not be ignored.
The rebuild has started.
All builds submitted. Exceptions:
f44 build complete but not tagged to f44, will try again later:
gdal-3.11.3-3.fc44 libarrow-21.0.0-1.fc44 libgexiv2-0.15.1-1.fc44 libtdb-1.4.14-1.fc44 libtevent-0.17.1-1.fc44 orca-49~beta-1.fc44 samba-4.23.0-0.1.rc1.fc44
f43 and rawhide branches differ, will ask maintainers to handle f43 builds:
amdsmi anaconda argparse-manpage COPASI dogtag-pki google-api-python-client gr-hpsdr libguestfs llvm marisa mqtt-randompub osbuild poetry python-advisory-parser python-aiosqlite python-alembic python-colcon-parallel-executor python-charset-normalizer python-img2pdf python-kdcproxy python-ptrace python-pyftdi python-torch python-torchdata root setools strongswan
The rest is finished or running. Will resubmit all failed ones later.
-
Miro Hrončok