Bug 1477596

Summary:	add Provides python2-greenlet
Product:	Red Hat Enterprise Linux 7	Reporter:	Jon Schlueter <jschluet>
Component:	python-greenlet	Assignee:	John Keck <jkeck>
Status:	CLOSED WONTFIX	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.4	CC:	carl, ipa-qe, jwboyer, lsm5, npmccallum, tvignaud
Target Milestone:	rc	Keywords:	Extras
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1477347	Environment:
Last Closed:	2021-01-15 07:40:35 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 Jon Schlueter 2017-08-02 12:39:34 UTC

Description of problem:

for compatibility with python2-XXX naming convention would it be possible to add Provides: python2-greenlet

it would be nice to be able to use yum install python2-greenlet

Version-Release number of selected component (if applicable):

python-greenlet-0.4.2-4.el7

How reproducible:

Always

Steps to Reproduce:
1. yum install python2-greenlet


Actual results:

$ sudo yum install python2-greenlet
No package python2-greenlet available.


Expected results:

$ sudo yum install python2-greenlet
should just install the package



Additional info:

the following 2 should behave the same

$ sudo yum install python2-greenlet
$ sudo yum install python-greenlet

Comment 3 Josh Boyer 2017-08-03 12:18:21 UTC

Copying Lokesh on this bug, as he did the updates in the distant past.

Lokesh, I did the build for python-greenlet for 7.4 for multi-arch.  I can probably do this commit as well if there are no objections from you or your team.

Comment 5 RHEL Program Management 2021-01-15 07:40:35 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.