Bug 2031449 - Please branch and build perl-Unicode-String in epel9
Summary: Please branch and build perl-Unicode-String in epel9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: perl-Unicode-String
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Emmanuel Seyman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-12 02:43 UTC by Gary Buhrmaster
Modified: 2021-12-22 01:57 UTC (History)
5 users (show)

Fixed In Version: perl-Unicode-String-2.10-18.el9
Clone Of:
Environment:
Last Closed: 2021-12-22 01:57:18 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Gary Buhrmaster 2021-12-12 02:43:16 UTC 
Please branch and build perl-Unicode-String in epel9.
Comment 1 Paul Howarth 2021-12-12 10:25:35 UTC 
https://pagure.io/releng/fedora-scm-requests/issue/39394
Comment 2 Paul Howarth 2021-12-13 16:36:27 UTC 
Whoops, I'm not co-maintainer on this one so Emmanuel will need to do it...
Comment 3 Emmanuel Seyman 2021-12-13 17:15:34 UTC 
I should really put the perl-maint group as co-maint for all my packages...

https://pagure.io/releng/fedora-scm-requests/issue/39476
Comment 4 Fedora Update System 2021-12-13 19:59:23 UTC 
FEDORA-EPEL-2021-3d5e3cc56a has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-3d5e3cc56a
Comment 5 Fedora Update System 2021-12-14 01:46:41 UTC 
FEDORA-EPEL-2021-3d5e3cc56a 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-2021-3d5e3cc56a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2021-12-22 01:57:18 UTC 
FEDORA-EPEL-2021-3d5e3cc56a 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.