This bug was fixed in the package tzdata - 2022f-0ubuntu0.22.04.1 --------------- tzdata (2022f-0ubuntu0.22.04.1) jammy; urgency=medium
* Update ICU data to 2022f (LP: #1995601) -- Benjamin Drung <bdr...@ubuntu.com> Mon, 07 Nov 2022 10:49:33 +0100 ** Changed in: tzdata (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: tzdata (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1995601 Title: tzdata 2022f ICU data update Status in tzdata package in Ubuntu: Triaged Status in tzdata source package in Focal: Fix Released Status in tzdata source package in Jammy: Fix Released Status in tzdata source package in Kinetic: Fix Released Status in tzdata source package in Lunar: Triaged Bug description: The ICU data we embed in tzdata was out of sync on the 2022f-0ubuntu1 upload, still matching the 2022e data instead. It's been updated upstream, so we need to do another round of SRUs for it: https://github.com/unicode-org/icu- data/commit/ad9d2568d02b2130f1ba34f876fc82cad32c522f The following Python script should work with the update and crash on obsolete data: from datetime import datetime from icu import ICUtzinfo, TimeZone tz = ICUtzinfo(TimeZone.createTimeZone("America/Chihuahua")) before = datetime(2022, 10, 1) after = datetime(2022, 11, 2) assert(tz.utcoffset(before) == tz.utcoffset(after)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1995601/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp