Bug 2042867 - Please branch and build perl-Data-Compare for EPEL 9
Summary: Please branch and build perl-Data-Compare for EPEL 9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: perl-Data-Compare
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paul Howarth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-20 09:45 UTC by Paul Howarth
Modified: 2022-03-11 13:43 UTC (History)
3 users (show)

Fixed In Version: perl-Data-Compare-1.27-1.el9
Clone Of:
Environment:
Last Closed: 2022-03-11 13:43:13 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Paul Howarth 2022-01-20 09:45:24 UTC 
Could you please branch and build perl-Data-Compare for EPEL 9 ?

If you like you could add me (FAS: pghmcfc) as a committer to the package and I'll do it myself.
Comment 1 Paul Howarth 2022-02-04 10:52:52 UTC 
Will you be able to branch and build perl-Data-Compare in epel9?
I would be happy to be a co-maintainer if you do not wish
to build it on epel9 (FAS: pghmcfc).
Comment 2 Paul Howarth 2022-03-01 12:53:13 UTC 
https://pagure.io/releng/fedora-scm-requests/issue/42618
Comment 3 Fedora Update System 2022-03-02 16:26:09 UTC 
FEDORA-EPEL-2022-cf1a4cc94c has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-cf1a4cc94c
Comment 4 Fedora Update System 2022-03-03 16:49:41 UTC 
FEDORA-EPEL-2022-cf1a4cc94c 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-cf1a4cc94c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 5 Fedora Update System 2022-03-11 13:43:13 UTC 
FEDORA-EPEL-2022-cf1a4cc94c 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.