Bug 2059352

Summary: Please branch and build gwenhywfar in epel9
Product: [Fedora] Fedora EPEL Reporter: Dalton Miner <daltonminer>
Component: gwenhywfarAssignee: Gwyn Ciesla <gwync>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel9CC: carl, davdunc, davide, gwync, michel, ngompa13, notting
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gwenhywfar-5.9.0-1.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-04 16:23:07 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: 1914423, 2068798    

Description Dalton Miner 2022-02-28 21:07:01 UTC
Please branch and build gwenhywfar in epel9.

If you do not wish to maintain gwenhywfar 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 dminer);
please add me through https://src.fedoraproject.org/rpms/gwenhywfar/adduser

Comment 1 Neal Gompa 2022-02-28 21:26:07 UTC
If you do not wish to maintain gwenhywfar in epel9,
or do not think you will be able to do this in a timely manner,
the EPEL Packagers SIG would be happy to be a co-maintainer of the package;
please add the epel-packagers-sig group through
https://src.fedoraproject.org/rpms/gwenhywfar/addgroup
and grant it commit access, or collaborator access on epel* branches.

Comment 2 Fedora Update System 2022-03-03 18:52:48 UTC
FEDORA-EPEL-2022-42603bcd0f has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-42603bcd0f

Comment 3 Fedora Update System 2022-03-04 16:23:07 UTC
FEDORA-EPEL-2022-42603bcd0f has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.