Bug 2046230

Summary: Please branch and build perl-User-Identity for EPEL-9
Product: [Fedora] Fedora EPEL Reporter: Paul Howarth <paul>
Component: perl-User-IdentityAssignee: Sergio Basto <sergio>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel9CC: perl-devel, sergio, spotrh
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: perl-User-Identity-1.00-5.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-02-06 02:15:35 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: 2041283    
Bug Blocks:    

Description Paul Howarth 2022-01-26 12:55:42 UTC
Could you please branch and build perl-User-Identity for EPEL-9 ?

If you prefer, you could add me (FAS: pghmcfc) as a committer and I'll do it myself.

Comment 1 Sergio Basto 2022-01-28 00:44:06 UTC
branched requested https://pagure.io/releng/fedora-scm-requests/issue/41422 

I think I changed the numbers, but it doesn't matter the information is: the branch was requested

Comment 2 Fedora Update System 2022-01-28 16:12:37 UTC
FEDORA-EPEL-2022-07bba0280f has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-07bba0280f

Comment 3 Fedora Update System 2022-01-29 06:45:14 UTC
FEDORA-EPEL-2022-07bba0280f 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-07bba0280f

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

Comment 4 Fedora Update System 2022-02-06 02:15:35 UTC
FEDORA-EPEL-2022-07bba0280f has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.