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.
Hello,
rebuilding an EPEL7 package for yara I actually noticed that the python-libs package doesn't provide the python2-libs. This is supprising and unexpected, because python package does provide also python2, the python-devel package does also provide python2-devel. The only one different is the python-libs, which doesn't provide the python2-libs.
Please can you consider adding that advertisement to the python-libs package for consistency with other packages generated from the same python-....src.rpm ?
Thank you
Michal Ambroz
Comment 2Petr Viktorin (pviktori)
2018-03-16 15:51:37 UTC
Hello,
> depending directly on python2-libs strikes me as quite unusual;
> can I ask why you need to do it?
Yes. Technically I didn't really needed to have that listed explicitly in EPEL, as the package is brought in automatically. That was also fix for my case.
But I was having it in some package historically from previous maintainer - it was working untill now so I was not changing.
BuildRequires: python
BuildRequires: python-libs
BuildRequires: python-setuptools
Fedora is now moving BuildRequires from "python-*" to "python2-*" so I have changed all build requirements as a good cinizen ... and voila found that this doesn't work:
python2
python2-libs
python2-setuptools
As I said ... it just looks odd that you provide python2 from python package, python2-setuptools from python-setup, but not python2-libs from python-libs.
What looks good usually also works better.
From the compatibility reasons I do not understand the hesitation to not provide python2-libs as well from python-libs with next bugfix release of python-libs.
Comment 4Petr Viktorin (pviktori)
2018-03-23 17:55:02 UTC
Ah, it's not hesitation to fix the issue, but worry that "the next release" might be too late to be useful for you.
I don't see a problem fixing this in the next bugfix (not security) release (although that I'm not the (only) one to decide that). After all the bug is still open :)
But RHEL processes generally take quite long, so I provided a workaround and asked for the use case (to see if a new release should be made just for this, and to see if I can help your particular case better).
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/RHSA-2018:3041