Bug 2314523

Summary: Please branch and build python-zope-testrunner in epel10
Product: [Fedora] Fedora EPEL Reporter: Michel Lind <michel>
Component: python-zope-testrunnerAssignee: Kaleb KEITHLEY <kkeithle>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel10CC: aurelien, epel-packagers-sig, infra-sig, kkeithle, michel, romain.geissler
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-zope-testrunner-6.6-2.el10_0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-01-21 03:33:45 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: 2311680, 2311697, 2314524, 2325263, 2331259, 2333354, 2333355, 2339002    
Bug Blocks: 1914423, 2314522, 2324169    

Description Michel Lind 2024-09-24 21:15:37 UTC
Please branch and build python-zope-testrunner in epel10.

Comment 1 Kaleb KEITHLEY 2024-12-19 18:03:47 UTC
scratch build at https://koji.fedoraproject.org/koji/taskinfo?taskID=127021135

Comment 2 Kaleb KEITHLEY 2024-12-19 18:05:36 UTC
(In reply to Kaleb KEITHLEY from comment #1)
> scratch build at
> https://koji.fedoraproject.org/koji/taskinfo?taskID=127021135

oops, wrong bz

Comment 3 Kaleb KEITHLEY 2025-01-20 14:24:51 UTC
*** Bug 2339000 has been marked as a duplicate of this bug. ***

Comment 4 Fedora Update System 2025-01-20 15:04:44 UTC
FEDORA-EPEL-2025-10d0d71448 (python-zope-testrunner-6.6-2.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-10d0d71448

Comment 5 Fedora Update System 2025-01-21 03:33:45 UTC
FEDORA-EPEL-2025-10d0d71448 (python-zope-testrunner-6.6-2.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.