Bug 2038103

Summary: Please branch and build perl-Devel-Cover for EPEL-9
Product: [Fedora] Fedora EPEL Reporter: Paul Howarth <paul>
Component: perl-Devel-CoverAssignee: Tom "spot" Callaway <spotrh>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel9CC: jose.p.oliveira.oss, perl-devel, spotrh
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: perl-Devel-Cover-1.36-6.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-23 00:54:30 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:

Description Paul Howarth 2022-01-07 09:58:24 UTC
Could you please branch and build perl-Devel-Cover for EPEL-9 ?

If you prefer, you could add me (FAS: pghmcfc) as a committer and I'll do it myself.

Comment 1 Paul Howarth 2022-01-14 09:53:19 UTC
Will you be able to branch and build perl-Devel-Cover in epel9?
I would be happy to be a co-maintainer if you do not wish
to build it on epel9 (FAS pghmcfc).

Thanks for all the EPEL-9 work yesterday by the way!

Comment 2 Fedora Update System 2022-01-14 18:05:21 UTC
FEDORA-EPEL-2022-b8fc12215b has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-b8fc12215b

Comment 3 Fedora Update System 2022-01-15 01:48:02 UTC
FEDORA-EPEL-2022-b8fc12215b 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-b8fc12215b

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

Comment 4 Fedora Update System 2022-01-23 00:54:30 UTC
FEDORA-EPEL-2022-b8fc12215b has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.