Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-677

pytz: FTBFS due to tzdata changes [rhel8]

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • rhel-8.9.0
    • rhel-8.9.0
    • pytz
    • pytz-2017.2-10.el8
    • None
    • None
    • rhel-sst-pt-python-ruby-nodejs
    • 21
    • 25
    • None
    • Dev ack
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • If docs needed, set a value
    • None

      +++ 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@stuartbishop.net>
      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.

      — Additional comment from Lumír Balhar on 2023-06-27 10:35:50 UTC —

      And also for the non-modular version in RHEL 8.

              lbalhar@redhat.com Lumir Balhar
              lbalhar@redhat.com Lumir Balhar
              python-maint python-maint
              bot rhel-cs-apps-subsystem-qe bot rhel-cs-apps-subsystem-qe
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: