Bug 2034695

Summary: Branch and build python-freezegun in EPEL 9
Product: [Fedora] Fedora EPEL Reporter: Neal Gompa <ngompa13>
Component: python-freezegunAssignee: Carl George 🤠 <carl>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel9CC: carl, cstratak, dradez, infra-sig, kevin, rbean
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-freezegun-1.1.0-1.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-12-31 01:48:08 UTC Type: Task
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, 2034692, 2042002    

Description Neal Gompa 2021-12-21 17:44:03 UTC
Please branch and build python-freezegun for EPEL 9, as it's required for python-progressbar2.

Comment 1 Carl George 🤠 2021-12-23 02:42:37 UTC
Branch requested.

https://pagure.io/releng/fedora-scm-requests/issue/40031

Comment 2 Fedora Update System 2021-12-28 23:32:10 UTC
FEDORA-EPEL-2021-7e23ac077a has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-7e23ac077a

Comment 3 Fedora Update System 2021-12-29 02:07:41 UTC
FEDORA-EPEL-2021-7e23ac077a 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-7e23ac077a

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

Comment 4 Fedora Update System 2021-12-31 01:48:08 UTC
FEDORA-EPEL-2021-7e23ac077a has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Carl George 🤠 2022-01-25 17:59:31 UTC
*** Bug 2042000 has been marked as a duplicate of this bug. ***