Bug 2217852

Summary: python27:2.7 - pytz: FTBFS due to tzdata changes
Product: Red Hat Enterprise Linux 8 Reporter: Lumír Balhar <lbalhar>
Component: pytzAssignee: Lumír Balhar <lbalhar>
Status: CLOSED ERRATA QA Contact: Lukáš Zachar <lzachar>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.9CC: cstratak, fweimer, lbalhar, python-maint, rhel-cs-apps-subsystem-qe, torsava
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python27-2.7-8090020230724122240.449e760b pytz-2017.2-13 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 2216116 Environment:
Last Closed: 2023-11-14 15:36:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lumír Balhar 2023-06-27 09:45:13 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:32:26 UTC 
https://gitlab.com/redhat/centos-stream/rpms/pytz/-/merge_requests/9
Comment 2 Lumír Balhar 2023-07-17 10:58:12 UTC 
Merged, and will wait for the next modular build.
Comment 7 errata-xmlrpc 2023-11-14 15:36:09 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: python27:2.7 security and bug fix 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:7042