Bug 2032189

Summary:	Branch and build cabextract in epel9
Product:	[Fedora] Fedora EPEL	Reporter:	Neal Gompa <ngompa13>
Component:	cabextract	Assignee:	Rex Dieter <rdieter>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel9	CC:	carl, davide, daxelrod, fedora, janfrode, jorti, matt, michel, ms, rdieter, redhat-bugzilla
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cabextract-1.9.1-3.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-01-22 01:34:22 UTC	Type:	---
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:	1914423

Description Neal Gompa 2021-12-14 08:00:08 UTC

Please branch and build cabextract in epel9.

Comment 1 Davide Cavalca 2022-01-19 22:00:38 UTC

Will you be able to branch and build cabextract in epel9?
The EPEL Packaging SIG would be happy to be a co-maintainer
if you do not wish to build it on epel9.

Comment 2 Robert Scheck 2022-01-19 23:28:34 UTC

https://pagure.io/releng/fedora-scm-requests/issue/41140

Comment 3 Fedora Update System 2022-01-20 23:02:51 UTC

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

Comment 4 Fedora Update System 2022-01-21 17:38:02 UTC

FEDORA-EPEL-2022-df4eba53d1 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-df4eba53d1

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

Comment 5 Fedora Update System 2022-01-22 01:34:22 UTC

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