Bug 2036936

Summary:	Please branch and build python3-colorama in epel9
Product:	[Fedora] Fedora EPEL	Reporter:	Phil Baker <baker1tex>
Component:	python-colorama	Assignee:	Mikel Olasagasti Uranga <mikel>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel9	CC:	me, mikel, mrunge, python-sig, sgallagh
Target Milestone:	---
Target Release:	---
Hardware:	noarch
OS:	Linux
Whiteboard:
Fixed In Version:	python-colorama-0.4.4-12.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-01-23 00:54:33 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:
Bug Depends On:
Bug Blocks:	2036838

Description Phil Baker 2022-01-04 13:15:31 UTC

Greetings,

Could you please branch and build python3-colorama for EPEL 9?

Note: 
python3-colorama is a dependent package of tldr. Bug 2036838 requests branch and build of tldr for EPEL9.


Thank you, and kind regards,
Phil Baker

Comment 1 Stephen Gallagher 2022-01-04 14:52:50 UTC

Reassigning to the main `python-colorama` package, since this one was a special case for EPEL 7 only.

Comment 2 Fedora Update System 2022-01-14 21:16:47 UTC

FEDORA-EPEL-2022-b4b9807f29 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-b4b9807f29

Comment 3 Fedora Update System 2022-01-15 01:48:06 UTC

FEDORA-EPEL-2022-b4b9807f29 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-b4b9807f29

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2022-01-23 00:54:33 UTC

FEDORA-EPEL-2022-b4b9807f29 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.