Bug 2309116 (perl-XML-DOM-epel10)

Summary: Add perl-XML-DOM to EPEL 10
Product: [Fedora] Fedora EPEL Reporter: Jitka Plesnikova <jplesnik>
Component: perl-XML-DOMAssignee: Orion Poplawski <orion>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: epel10CC: gary.buhrmaster, orion, perl-devel
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: perl-XML-DOM-1.46-25.el10_0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-09-06 22:01:54 UTC Type: ---
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: 2309377, 2309378    
Bug Blocks: 2303880, 2308867    

Description Jitka Plesnikova 2024-09-02 10:04:45 UTC
Please branch and build perl-XML-DOM in epel10. I can take care of the build if you grant me access. My FAS username is jplesnik.

Reproducible: Always

Comment 1 Orion Poplawski 2024-09-03 02:04:08 UTC
I've added you to the package.  Thanks for taking care of this.

Comment 2 Fedora Update System 2024-09-05 11:20:23 UTC
FEDORA-EPEL-2024-391a34cb31 (perl-XML-DOM-1.46-25.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-391a34cb31

Comment 3 Fedora Update System 2024-09-06 05:01:03 UTC
FEDORA-EPEL-2024-391a34cb31 has been pushed to the Fedora EPEL 10.0 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-391a34cb31

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

Comment 4 Fedora Update System 2024-09-06 22:01:54 UTC
FEDORA-EPEL-2024-391a34cb31 (perl-XML-DOM-1.46-25.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository.
If problem still persists, please make note of it in this bug report.