There are already some bugzillas open for some of the packages, e.g.:
Of course I could prepare the patches and ask a proven packager for a rebuild, but maybe
that would be too invasive so I want to get some feedback first on what could be the best
course of action in this case.
Associate Software Engineer
Python Maintenance Team, Red Hat
----- Original Message -----
From: "Stephen Gallagher" <sgallagh(a)redhat.com>
Sent: Friday, September 2, 2016 12:56:30 PM
Subject: Re: BuildRequires on obsoleted packages provided by Python
On 09/02/2016 06:44 AM, Kalev Lember wrote:
On 08/31/2016 02:10 PM, Charalampos Stratakis wrote:
> Hello all,
> While checking out the SPEC file of python, it seems there were some packages that,
while separate at some point, they got included in python's stdlib and then obsoleted
as standalone packages (thus to cope with the change, python was obsoleting these packages
and providing them as well in the SPEC). So every package that currently (Build)Requires
any of these packages will essentially drag python with it.
> I will remove these provides soon, since the packages were orphaned long time ago,
but the packages that still require them, will need to be fixed and (Build)Require python
My suggestion would be to request provenpackager access and just fix all
those packages yourself in rawhide. If you file bugs, these are probably
going to take quite a bit of time to get fixed and you won't be able to
drop the compatibility provides for several Fedora releases.
Or just prep the patches and ask a provenpackager to apply them for you, which
is probably faster than getting access yourself.
devel mailing list