Bug 2029244

Summary: Please branch and build python-cram in epel9
Product: [Fedora] Fedora EPEL Reporter: Carl George 🎩 <carl>
Component: python-cramAssignee: Carl George 🎩 <carl>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel9CC: ktdreyer
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-cram-0.7-10.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-13 01:44:47 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: 2029243    

Description Carl George 🎩 2021-12-05 23:44:26 UTC
Please branch and build python-cram in epel9.

If you do not wish to maintain python-cram 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.

Comment 1 Carl George 🎩 2021-12-21 21:44:23 UTC
Will you be able to branch and build python-cram in epel9?  I would be happy to be a co-maintainer if you do not wish to build it on epel9.

Comment 2 Fedora Update System 2022-01-05 17:52:59 UTC
FEDORA-EPEL-2022-d3c939dd31 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-d3c939dd31

Comment 3 Fedora Update System 2022-01-06 02:05:01 UTC
FEDORA-EPEL-2022-d3c939dd31 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-d3c939dd31

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

Comment 4 Fedora Update System 2022-01-13 01:44:47 UTC
FEDORA-EPEL-2022-d3c939dd31 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.