Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
The latest Fedora Python Packaging guidelines [1] state that python modules should have a virtual provides for python2-%{srcname}. Obviously RHEL is not Fedora, but I think this enhancement makes sense for the RHEL package as well. Similar virtual provides already exist on the base python packages.
$ rpm -q --provides python | grep ^python2
python2 = 2.7.5
$ rpm -q --provides python-devel | grep ^python2
python2-devel = 2.7.5-18.el7_1.1
Benefits:
EPEL package maintainers (like myself) can require the virtual python2 name in our spec files. This allows the same spec file to be used for both Fedora and EPEL.
Drawbacks:
None that I am aware of.
Version-Release number of selected component (if applicable):
0.9.8-3.el7
Actual results:
python-setuptools does not provide python2-setuptools
Expected results:
python-setuptools should provide python2-setuptools
Additional info:
[1]: http://fedoraproject.org/wiki/Packaging:Python#Provides
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2017:1900
Description of problem: The latest Fedora Python Packaging guidelines [1] state that python modules should have a virtual provides for python2-%{srcname}. Obviously RHEL is not Fedora, but I think this enhancement makes sense for the RHEL package as well. Similar virtual provides already exist on the base python packages. $ rpm -q --provides python | grep ^python2 python2 = 2.7.5 $ rpm -q --provides python-devel | grep ^python2 python2-devel = 2.7.5-18.el7_1.1 Benefits: EPEL package maintainers (like myself) can require the virtual python2 name in our spec files. This allows the same spec file to be used for both Fedora and EPEL. Drawbacks: None that I am aware of. Version-Release number of selected component (if applicable): 0.9.8-3.el7 Actual results: python-setuptools does not provide python2-setuptools Expected results: python-setuptools should provide python2-setuptools Additional info: [1]: http://fedoraproject.org/wiki/Packaging:Python#Provides