Bug 1557460

Summary:	python-libs package dosn't provide python2-libs
Product:	Red Hat Enterprise Linux 7	Reporter:	Michal Ambroz <rebus>
Component:	python	Assignee:	Python Maintainers <python-maint>
Status:	CLOSED ERRATA	QA Contact:	Jan Kepler <jkejda>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.7	CC:	cstratak, jkejda, pviktori
Target Milestone:	rc	Keywords:	FastFix
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-2.7.5-72.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-30 07:55:14 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michal Ambroz 2018-03-16 15:31:19 UTC

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 2 Petr Viktorin (pviktori) 2018-03-16 15:51:37 UTC

It's best to do this in EPEL as a stub package.
See: https://fedoraproject.org/wiki/User:Tibbs/EPELPythonStubPackages

But, depending directly on python2-libs strikes me as quite unusual; can I ask why you need to do it?

Comment 3 Michal Ambroz 2018-03-23 12:18:51 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 4 Petr 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).

Comment 8 errata-xmlrpc 2018-10-30 07:55:14 UTC

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