Bug 2031806 - perl-Mouse for EPEL 9
Summary: perl-Mouse for EPEL 9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: perl-Mouse
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paul Howarth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2037655
Blocks: 2032430 2032433 2033349 2037658
TreeView+ depends on / blocked
 
Reported: 2021-12-13 13:23 UTC by Xavier Bachelot
Modified: 2022-01-29 06:18 UTC (History)
4 users (show)

Fixed In Version: perl-Mouse-2.5.10-9.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-29 06:18:58 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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 2 Paul Howarth 2022-01-06 08:51:52 UTC 
https://pagure.io/releng/fedora-scm-requests/issue/40527
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.
Note You need to log in before you can comment on or make changes to this bug.