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 1807844 - Retire python2-typing in Fedora 33+
Summary: Retire python2-typing in Fedora 33+
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: python2-typing
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paul Howarth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PY2REMOVAL F31_PY2REMOVAL
TreeView+ depends on / blocked
 
Reported: 2020-02-27 11:00 UTC by Miro Hrončok
Modified: 2020-02-27 11:07 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-27 11:07:37 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Miro Hrončok 2020-02-27 11:00:50 UTC 
In line with the Mass Python 2 Package Removal [0], all (sub)packages of python2-typing were marked for removal:

 * python2-typing

According to our query, those (sub)packages only provide a Python 2 importable module. If this is not true, please tell us why, so we can fix our query.

Please retire your package in Rawhide (Fedora 33).

Please don't remove packages from Fedora 32/31/30.

If there is no objection in a week, we will retire the package for you.

We hope this doesn't come to you as a surprise. If you want to know our motivation for this, please read the change document [0].

[0] https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal
Comment 1 Paul Howarth 2020-02-27 11:04:37 UTC 
Hi Miro,

I see this is no longer needed for python2-dns (or anything else) so please feel free to retire it straight away.

Paul.
Comment 2 Miro Hrončok 2020-02-27 11:07:37 UTC 
Thanks.
Note You need to log in before you can comment on or make changes to this bug.