Bug 2349172 - Please upgrade pytz to version 2025.1 in EPEL 10
Summary: Please upgrade pytz to version 2025.1 in EPEL 10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: pytz
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2347063
TreeView+ depends on / blocked
 
Reported: 2025-03-01 16:00 UTC by Romain Geissler
Modified: 2025-03-03 00:56 UTC (History)
1 user (show)

Fixed In Version: pytz-2025.1-1.el10_1
Clone Of:
Environment:
Last Closed: 2025-03-03 00:56:12 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Romain Geissler 2025-03-01 16:00:37 UTC 
Hi,

Please upgrade pytz to version 2025.1 in EPEL 10. It seems that the latest version of python-dateparser does require at least pytz >= 2024.2 and I guess by definition there is no problem updating pytz to have an up to date database.

Checking right now, using the rawhide branch content in EPEL 10 works fine.

I may help co-maintaining the EPEL branches if needed (fas id: romaingeissler1a).
Comment 1 Fedora Update System 2025-03-01 22:25:02 UTC 
FEDORA-EPEL-2025-774f8ac1dd (pytz-2025.1-1.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-774f8ac1dd
Comment 2 Fedora Update System 2025-03-02 01:22:19 UTC 
FEDORA-EPEL-2025-774f8ac1dd 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-774f8ac1dd

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 3 Fedora Update System 2025-03-03 00:56:12 UTC 
FEDORA-EPEL-2025-774f8ac1dd (pytz-2025.1-1.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.
Note You need to log in before you can comment on or make changes to this bug.