Bug 2030333

Summary: Please branch and build python-coverage in epel9
Product: [Fedora] Fedora Reporter: Jason Montleon <jmontleo>
Component: python-coverageAssignee: Tom "spot" Callaway <spotrh>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: aurelien, chedi.toueiti, dradez, lewk, mrunge, spotrh
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-coverage-6.2-1.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-12-19 01:25:45 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: 2032544    

Description Jason Montleon 2021-12-08 13:58:07 UTC
Please branch and build python-coverage in epel9.

If you do not wish to maintain <package> 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 Fedora Update System 2021-12-10 18:45:59 UTC
FEDORA-EPEL-2021-0814169d36 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-0814169d36

Comment 2 Fedora Update System 2021-12-11 02:11:15 UTC
FEDORA-EPEL-2021-0814169d36 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-2021-0814169d36

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

Comment 3 Tom "spot" Callaway 2021-12-15 19:23:25 UTC
*** Bug 2032723 has been marked as a duplicate of this bug. ***

Comment 4 Fedora Update System 2021-12-19 01:25:45 UTC
FEDORA-EPEL-2021-0814169d36 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Dan Radez 2022-01-17 18:58:26 UTC
Sry for the changes here. I've gotten myself mixed up.