Bug 2031806

Summary: perl-Mouse for EPEL 9
Product: [Fedora] Fedora EPEL Reporter: Xavier Bachelot <xavier>
Component: perl-MouseAssignee: Paul Howarth <paul>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel9CC: emmanuel, iarnell, paul, perl-devel
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: perl-Mouse-2.5.10-9.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-29 06:18:58 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:
Bug Depends On: 2037655    
Bug Blocks: 2032430, 2032433, 2033349, 2037658    

Description Xavier Bachelot 2021-12-13 13:23:28 UTC
Hi,

Could you please branch and build perl-Mouse for EPEL 9 ?

Regards,
Xavier

Comment 1 Paul Howarth 2021-12-13 14:55:41 UTC
I expect this to take a long time because Moose and all of its extensive test dependency list need to be done first.
Many of those packages are owned by Ralf (who doesn't do EPEL) and may need to get co-maintainership.

Comment 3 Fedora Update System 2022-01-21 15:38:40 UTC
FEDORA-EPEL-2022-1526c502bd has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-1526c502bd

Comment 4 Fedora Update System 2022-01-22 01:39:01 UTC
FEDORA-EPEL-2022-1526c502bd 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-1526c502bd

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

Comment 5 Fedora Update System 2022-01-29 06:18:58 UTC
FEDORA-EPEL-2022-1526c502bd has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.