On 9/11/25 19:36, Stephen Gallagher wrote:
On Thu, Sep 11, 2025 at 5:44 PM Kevin Fenzi <ke...@scrye.com> wrote:
On Thu, Sep 11, 2025 at 03:05:35PM +0200, Karolina Surma via devel-announce
wrote:
Hello,
Yes, that's right.
The Python's "magic numer" has had to be bumped again[1] resulting in us
needing to recreate the Python 3.14 .pyc files one more time in both Fedora
43 and 44.
Python 3.14.0rc3 is planned to be released on Tuesday, September 16th, 2025.
This is also the planned Beta Freeze end for Fedora 43.
To obtain a list of packages, use:
$ repoquery --repo=rawhide --refresh -f *.cpython-314.pyc --source
(3743 packages atm)
and respectively:
$ repoquery --repo=fedora --releasever 43 --refresh -f *.cpython-314.pyc
--source
(3751 packages atm)
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. Wait for Python 3.14.0rc3 release.
2. Wait for the Fedora 43 Beta Freeze to finish.
3. Bump and build all 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.
c) their latest commit hash has been successfully built and shipped for
Fedora 43.
5. Open Bodhi updates for packages built for Fedora 43.
How are you planning on doing the updates?
In groups? one at a time? all at once?
I don't think bodhi can handle ~3700 packages in one update. :(
This is something we actually wanted to try for ELN. I feel like I
remember a conversation from the recent past where we figured out that
the major impediment to doing this had actually been fixed (it was
related to HTTP timeouts trying to add all of the packages, I think).
I'm pretty sure we'd been given the green light to try this for the
~2500 packages in ELN. I'm CCing Yaakov Selkowitz and Adam Williamson
directly who could correct me if I'm misremembering.
So maybe it's worth giving it a try? If it fails, we can always fall
back to the direct tagging option.
Karolina: Either way, I think we need to do this in a side-tag, if
only to have an easy way to look up what potentially needs tagging.
Since we're past the Bodhi activation point, we can't rely on
automation to create all of the individual updates (short of
submitting them as a single update from a side-tag).
To clarify, we do want to try a massive update, but *only* from a single
side tag. We do NOT recommend trying to make a massive update from
individual builds. Because of how bodhi works, we believe there is a
major difference in performance between these two possibilities, and
that only the former has a decent chance of success.
--
Yaakov Selkowitz
Principal Software Engineer, Emerging RHEL
Red Hat, Inc.
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
