Bug 2302853
| Summary: | Obsolete packages that used to require Python 3.12 but are gone in Fedora 42 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Karolina Surma <ksurma> |
| Component: | fedora-obsolete-packages | Assignee: | Karolina Surma <ksurma> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 42 | CC: | awilliam, gbcox, j, lbrabec, maxwell, mhroncok |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | fedora-obsolete-packages-41-12 fedora-obsolete-packages-41-14 fedora-obsolete-packages-42-20 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-04-17 19:01:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2244836, 2291266, 2322527 | ||
|
Description
Karolina Surma
2024-08-05 10:34:53 UTC
The first batch was shipped via https://src.fedoraproject.org/rpms/fedora-obsolete-packages/pull-request/94 == https://bodhi.fedoraproject.org/updates/FEDORA-2024-26e04543f7 The beta freeze batch is https://src.fedoraproject.org/rpms/fedora-obsolete-packages/pull-request/96 (+ 95 for rawhide) FEDORA-2024-694198f36d (fedora-obsolete-packages-41-6) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-694198f36d FEDORA-2024-694198f36d has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-694198f36d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-694198f36d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. +3 in https://pagure.io/fedora-qa/blocker-review/issue/1625 , marking accepted FE. FEDORA-2024-694198f36d (fedora-obsolete-packages-41-6) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report. The final freeze batch is here: https://src.fedoraproject.org/rpms/fedora-obsolete-packages/pull-request/100 (+ https://src.fedoraproject.org/rpms/fedora-obsolete-packages/pull-request/101 for Rawhide) FEDORA-2024-98109a7796 (fedora-obsolete-packages-41-12) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-98109a7796 FEDORA-2024-98109a7796 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-98109a7796` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-98109a7796 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. +3 in https://pagure.io/fedora-qa/blocker-review/issue/1706 , marking accepted. FEDORA-2024-98109a7796 (fedora-obsolete-packages-41-12) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report. Just wanted to advise here that this issue apparently isn't fixed. If it was closed on October 18 I would assume that 12 days would be sufficient for it to be properly propagated. (In reply to Petr Pisar from comment #4) > python3-fedmsg was removed from Fedora and does not exist in Fedora 41 (bug > #2291518). It blocks your upgrade because Fedora 40's python3-fedmsg is > built against old python which does not exist in Fedora 41. The package was > obsoleted in fedora-obsolete-packages-41-11. In repositories since > 2024-10-18. Maybe your Fedora mirror is not up-to-date. Please try again. It > should have already been resolved. > > The fedmod, future, module-build-service, python-twitter, and smartcols are > the same case. > > This is all fixed via bz2302853. See bz2322527 bz2322527 is a ug in dnf. This has been properly obsoleted in fedora-obsolete-packages. (In reply to Miro Hrončok from comment #13) > bz2322527 is a ug in dnf. > > This has been properly obsoleted in fedora-obsolete-packages. Wait, what? You're the one that said in bz2322527 that: "This is all fixed via bz2302853." It is still occurring, so it is obviously not fixed. What did you mean by your statement that it as "all fixed"? Are you saying there is still a code defect within DNF5? > Are you saying there is still a code defect within DNF5? Yes, as described in https://bugzilla.redhat.com/show_bug.cgi?id=2322527#c5 FEDORA-2024-6b911eb10a (fedora-obsolete-packages-41-13) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-6b911eb10a FEDORA-2024-6b911eb10a has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-6b911eb10a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-6b911eb10a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2024-f9a42073f3 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-f9a42073f3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-f9a42073f3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2024-f9a42073f3 (fedora-obsolete-packages-41-14) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report. Discussed during the 2025-04-07 blocker review meeting [1]: * AGREED: 2302853 - punt - This got reopened from F41, but it's not clear whether it was intentional to keep the FE request flag, or just a mistake. If this should go through freeze, please provide some justification details, thank you. [1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2025-04-07/f42-blocker-review.2025-04-07-16.01.log.html Yes, this was intentional. That's why I removed AcceptedFreezeException from whiteboard, removed F41FinalFreezeException tracker, added F42FinalFreezeException tracker, moved this to the 42 version, reopened it and renamed it to mention Fedora 42 instead of Fedora 41. If this was done by mistake, it would have been a very weird one. We do this every even Fedora release, the last time in https://bugzilla.redhat.com/show_bug.cgi?id=2233409#c24 At every release boundary, we need to obsolete the removed Python 3.N-1 packages. We do this deliberately after the freeze because that's when the list of removed packagers is stable. FEDORA-2025-2e6721ebec (fedora-obsolete-packages-42-20) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-2e6721ebec Doing it after the freeze is fine, but this was rather too late after the freeze. The freeze was on April 1. This wasn't proposed until six days later, the Monday of go/no-go week, which is usually when we want to have the RC already built by. Going forward, can we plan to do this *immediately* after freezes? Thanks! FEDORA-2025-2e6721ebec has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-2e6721ebec` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-2e6721ebec See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. > Going forward, can we plan to do this *immediately* after freezes? Thanks!
Absolutely. That was always the idea. Not doing it this time was a planning error on our part.
FEDORA-2025-2e6721ebec (fedora-obsolete-packages-42-20) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report. |