Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1980460 - Obsolete packages that used to require Python 3.9 but are gone in Fedora 35
Summary: Obsolete packages that used to require Python 3.9 but are gone in Fedora 35
Keywords:
Status: ASSIGNED
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-obsolete-packages
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Hrnčiar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F37FinalFreezeException, FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2021-07-08 17:14 UTC by Miro Hrončok
Modified: 2022-05-11 14:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Miro Hrončok 2021-07-08 17:14:47 UTC
Packages that required Python 3.9 in Fedora 33 or 34 and are gone (retired, removed subpackages) from Fedora 35 must be obsoleted, or else they have broken dependencies (e.g. on python(abi) = 3.9 or python3.9dist(...)) and block the upgrade path to Fedora 35.

I'll use this bug to track this.


We can do this in batches to unblock rawhide users but most importantly we need to do this:

- right after entering beta freeze (with a freeze exception)
- right after entering final freeze (with a freeze exception)

We need to do it after the freezes start to include packages removed right before it started.

We'll need to repeat this later for Fedora 36 milestones as well.

See also bz1856098 (same bug for Python 3.8 packages removed from Fedora 33).
See also bz1754151 (same bug for Python 3.7 packages removed from Fedora 32).


Note You need to log in before you can comment on or make changes to this bug.