Bug 2346664

Summary: Please branch and build python-ddt in epel10
Product: [Fedora] Fedora EPEL Reporter: Davide Cavalca <davide>
Component: python-ddtAssignee: Carl George 🎩 <carl>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel10CC: carl, igor.raits, python-packagers-sig
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-ddt-1.7.2-2.el10_1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-25 02:39:01 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:    
Bug Blocks: 1914423    

Description Davide Cavalca 2025-02-19 19:40:17 UTC
Please branch and build python-ddt in epel10.

Comment 1 Davide Cavalca 2025-02-19 19:40:55 UTC
Also please consider adding mkdocs-sig as a co-maintainer as this is a dependency of the MkDocs package stack.

Comment 2 Fedora Update System 2025-02-20 03:59:18 UTC
FEDORA-EPEL-2025-d9d2c1cf16 (python-ddt-1.7.2-2.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-d9d2c1cf16

Comment 3 Carl George 🎩 2025-02-20 04:11:32 UTC
Submitted and added that SIG as a co-maintainer.

Comment 4 Fedora Update System 2025-02-21 03:16:41 UTC
FEDORA-EPEL-2025-d9d2c1cf16 has been pushed to the Fedora EPEL 10.1 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-d9d2c1cf16

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

Comment 5 Fedora Update System 2025-02-25 02:39:01 UTC
FEDORA-EPEL-2025-d9d2c1cf16 (python-ddt-1.7.2-2.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.