RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2217853 - python38:3.8 - pytz: FTBFS due to tzdata changes
Summary: python38:3.8 - pytz: FTBFS due to tzdata changes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pytz
Version: 8.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Lumír Balhar
QA Contact: Lukáš Zachar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-27 09:46 UTC by Lumír Balhar
Modified: 2023-11-14 17:07 UTC (History)
6 users (show)

Fixed In Version: pytz-2019.3-4
Doc Type: No Doc Update
Doc Text:
Clone Of: 2216116
Environment:
Last Closed: 2023-11-14 15:36:21 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-160899 0 None None None 2023-06-27 09:49:30 UTC
Red Hat Product Errata RHSA-2023:7050 0 None None None 2023-11-14 15:36:58 UTC

Description Lumír Balhar 2023-06-27 09:46:36 UTC 
+++ This bug was initially created as a clone of Bug #2216116 +++

This upstream commit is needed to get pytz building again:

commit 07aa4d962dae5cb7ced4f61fe85a9001a01676df
Author: Stuart Bishop <stuart>
Date:   Sat Aug 13 12:00:26 2022 +1000

    Revert inclusion of PACKRATDATA=backzone
    
    Per https://github.com/python/tzdata/issues/53#issuecomment-1213628767
    
    I chose to include backzone in pytz in an attempt to head off problems:
    
      Changes to past timestamps
    
        Finish moving to 'backzone' the location-based zones whose
        timestamps since 1970 are duplicates; adjust links accordingly.
        This change ordinarily affects only pre-1970 timestamps, and with
        the new PACKRATLIST option it does not affect any timestamps.
        In this round the affected zones are Antarctica/Vostok,
        Asia/Brunei, Asia/Kuala_Lumpur, Atlantic/Reykjavik,
        Europe/Amsterdam, Europe/Copenhagen, Europe/Luxembourg,
        Europe/Monaco, Europe/Oslo, Europe/Stockholm, Indian/Christmas,
        Indian/Cocos, Indian/Kerguelen, Indian/Mahe, Indian/Reunion,
        Pacific/Chuuk, Pacific/Funafuti, Pacific/Majuro, Pacific/Pohnpei,
        Pacific/Wake and Pacific/Wallis, and the affected links are
        Arctic/Longyearbyen, Atlantic/Jan_Mayen, Iceland, Pacific/Ponape,
        Pacific/Truk, and Pacific/Yap.
    
    This upstream change modifies some of the pre-1970 transitions in obscure
    ways that almost zero users will actually care about, and where quite
    likely dubious in any case. Such as the times pre-1970 when Belfast was
    not on London time or when Amsterdam switched from being 18-20 minutes
    ahead of GMT to GMT. Changes to historical timezones has always happened
    in the upstream database, and normally they are called corrections
    (which only causes breakage if you area storing wallclock times rather
    than UTC timestamps).

--- Additional comment from Lumír Balhar on 2023-06-27 09:41:06 UTC ---

It seems that the problem now causes FTBFS of pytz in python27 and python38 modules in RHEL 8. I'm gonna clone this bugzilla for them.
Comment 1 Lumír Balhar 2023-07-14 08:38:32 UTC 
https://gitlab.com/redhat/centos-stream/rpms/pytz/-/merge_requests/10
Comment 2 Lumír Balhar 2023-07-17 10:57:39 UTC 
Merged, and will wait for the next modular build.
Comment 7 errata-xmlrpc 2023-11-14 15:36:21 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: python38:3.8 and python38-devel:3.8 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:7050
Note You need to log in before you can comment on or make changes to this bug.