Bug 2082714 - Please branch and build python-iso8601 in epel9
Summary: Please branch and build python-iso8601 in epel9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-iso8601
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Carl George 🤠
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-06 20:39 UTC by Carl George 🤠
Modified: 2022-11-09 11:46 UTC (History)
2 users (show)

Fixed In Version: python-iso8601-1.1.0-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-09 11:46:56 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Carl George 🤠 2022-05-06 20:39:08 UTC 
Please branch and build python-iso8601 in epel9.

If you do not wish to maintain python-iso8601 in epel9, or do not think you will be able to do this in a timely manner, I would be happy to be a co-maintainer of the package (FAS carlwgeorge).
Comment 1 Carl George 🤠 2022-10-14 22:50:53 UTC 
Will you be able to branch and build python-iso8601 in epel9?  I would be happy to be a co-maintainer if you do not wish to build it on epel9 (FAS: carlwgeorge>).
Comment 2 Fedora Update System 2022-10-31 18:56:26 UTC 
FEDORA-EPEL-2022-147a6502fe has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-147a6502fe
Comment 3 Fedora Update System 2022-11-01 16:35:26 UTC 
FEDORA-EPEL-2022-147a6502fe 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-147a6502fe

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 4 Fedora Update System 2022-11-09 11:46:56 UTC 
FEDORA-EPEL-2022-147a6502fe has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.