Bug 2036510

Summary: Please branch and build perl-Config-General for EPEL-9
Product: [Fedora] Fedora EPEL Reporter: Paul Howarth <paul>
Component: perl-Config-GeneralAssignee: Paul Howarth <paul>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel9CC: lionel.cons, lkundrak, nathanael, perl-devel
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: perl-Config-General-2.63-7.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-26 17:58:56 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-02 16:43:31 UTC
Could you please branch and build perl-Config-General 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-09 15:30:46 UTC
Will you be able to branch and build perl-Config-General in epel9?
I would be happy to be a co-maintainer if you do not wish
to build it on epel9.

Comment 2 lionel.cons 2022-01-14 10:55:47 UTC
+1

Comment 4 Fedora Update System 2022-01-18 16:13:12 UTC
FEDORA-EPEL-2022-69dd4e3245 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-69dd4e3245

Comment 5 Fedora Update System 2022-01-19 02:55:42 UTC
FEDORA-EPEL-2022-69dd4e3245 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-69dd4e3245

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

Comment 6 Fedora Update System 2022-01-26 17:58:56 UTC
FEDORA-EPEL-2022-69dd4e3245 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.