Bug 1787246 - pygame: Remove (sub)packages from Fedora 32+: pygame-devel, python2-pygame
Summary: pygame: Remove (sub)packages from Fedora 32+: pygame-devel, python2-pygame
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: pygame
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1738043 (view as bug list)
Depends On:
Blocks: PY2REMOVAL F31_PY2REMOVAL PYTHON2_EOL
TreeView+ depends on / blocked
 
Reported: 2020-01-01 21:23 UTC by Miro Hrončok
Modified: 2020-01-06 15:50 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-06 15:50:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Miro Hrončok 2020-01-01 21:23:51 UTC
In line with the Retire Python 2 Fedora change [0], the following (sub)packages of pygame were marked for removal:

 * pygame-devel
 * python2-pygame

There was no approved FESCo exception for this package.

Please remove them from your package in Rawhide (Fedora 32).

Please don't remove packages from Fedora 31/30/29, removing packages from a released Fedora branch is forbidden and out of scope of this request.

If there is no objection in two weeks, we will remove the package(s) as soon as we get to it. This change might not match your packaging style, so we'd prefer if you did the change. If you need more time, please let us know here.

If you do the change yourself, it would help us a lot by reducing the amount of packages we need to mass change.

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].

This text is automated. We are sorry if you already communicated with us about this in another place.

[0] https://fedoraproject.org/wiki/Changes/RetirePython2

Comment 1 Miro Hrončok 2020-01-01 21:27:34 UTC
*** Bug 1738043 has been marked as a duplicate of this bug. ***


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