Bug 2038103 - Please branch and build perl-Devel-Cover for EPEL-9
Summary: Please branch and build perl-Devel-Cover for EPEL-9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: perl-Devel-Cover
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-07 09:58 UTC by Paul Howarth
Modified: 2022-01-23 00:54 UTC (History)
3 users (show)

Fixed In Version: perl-Devel-Cover-1.36-6.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-23 00:54:30 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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