Bug 2030333 - Please branch and build python-coverage in epel9
Summary: Please branch and build python-coverage in epel9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-coverage
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2032723 (view as bug list)
Depends On:
Blocks: 2032544
TreeView+ depends on / blocked
 
Reported: 2021-12-08 13:58 UTC by Jason Montleon
Modified: 2022-01-17 18:58 UTC (History)
6 users (show)

Fixed In Version: python-coverage-6.2-1.el9
Clone Of:
Environment:
Last Closed: 2021-12-19 01:25:45 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.