Bug 2111050

Summary:	Please branch and build tlp in epel9
Product:	[Fedora] Fedora EPEL	Reporter:	Pablo Greco <pablo>
Component:	tlp	Assignee:	Jeremy Newton <alexjnewt>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel9	CC:	alexjnewt, oliver, wtogami
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tlp-1.5.0-2.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-04 00:37:39 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 Pablo Greco 2022-07-26 11:51:28 UTC

Please branch and build tlp in epel9.

If you do not wish to maintain tlp in epel9,
or do not think you will be able to do this in a timely manner,
I would be happy to be a co-maintainer of the package (FAS pgreco);
please add me through https://src.fedoraproject.org/rpms/tlp/adduser

Comment 1 Jeremy Newton 2022-07-26 13:47:34 UTC

No I don't mind. It's pretty easy to maintain EPEL for tlp.

I just forgot to go around and add epel9 for some of my packages.

Comment 2 Fedora Update System 2022-07-26 16:45:02 UTC

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

Comment 3 Fedora Update System 2022-07-27 03:22:29 UTC

FEDORA-EPEL-2022-6e72ca0631 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-6e72ca0631

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

Comment 4 Fedora Update System 2022-08-04 00:37:39 UTC

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