Bug 2211359

Summary: Please branch and build python-warlock in epel9
Product: [Fedora] Fedora EPEL Reporter: Joel Capitao <jcapitao>
Component: python-warlockAssignee: Joel Capitao <jcapitao>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel9CC: apevec, mrunge
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-warlock-1.3.3-11.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-06-17 01:36:20 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: 2104767    

Description Joel Capitao 2023-05-31 08:45:18 UTC
Please branch and build python-warlock in epel9.

Comment 1 Joel Capitao 2023-06-08 08:15:53 UTC
Will you be able to branch and build python-warlock in epel9?
I would be happy to be a co-maintainer if you do not wish
to build it on epel9 (FAS: jcapitao).

Comment 2 Joel Capitao 2023-06-08 08:27:00 UTC
Build from rawhide is successful https://koji.fedoraproject.org/koji/taskinfo?taskID=101931090

Comment 5 Fedora Update System 2023-06-08 10:02:33 UTC
FEDORA-EPEL-2023-0347128420 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-0347128420

Comment 6 Fedora Update System 2023-06-09 02:08:45 UTC
FEDORA-EPEL-2023-0347128420 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-2023-0347128420

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

Comment 7 Fedora Update System 2023-06-17 01:36:20 UTC
FEDORA-EPEL-2023-0347128420 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.