The verification of the Stable Release Update for tzdata has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
-- 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/1992692 Title: tzdata 2022e release Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Trusty: Fix Released Status in tzdata source package in Xenial: Fix Released Status in tzdata source package in Bionic: Fix Released Status in tzdata source package in Focal: Fix Released Status in tzdata source package in Jammy: Fix Released Bug description: New timezone data, with the following timezones impacted: - Palestine transitions are now Saturdays at 02:00. This means 2022 falls back 10-29 at 02:00, not 10-28 at 01:00. - Simplify three Ukraine zones into one. - Jordan and Syria switch from +02/+03 with DST to year-round +03. icu update to 2022e: https://unicode- org.atlassian.net/browse/ICU-22178 Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with 'zdump -v $region/$timezone_that_changed' (this needs to be greped for in /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. [Test Case for all releases] 1) zdump -v Asia/Gaza | grep 'Oct.*2022' -> should indicate Oct 29, not Oct 28 2) zdump -v Asia/Damascus | tail -> last dates should be in 2022, not in 2499 [Test Case for releases >= 20.04 LTS] For releases with ICU timezone data verification is done using the following with dates before and after the change: 1) sudo apt-get install python3-icu 2) Run the following python script: from datetime import datetime from icu import ICUtzinfo, TimeZone tz = ICUtzinfo(TimeZone.createTimeZone("Asia/Gaza")) always_before = datetime(2022, 10, 1) now_before = datetime(2022, 10, 29) always_after = datetime(2022, 11, 1) assert(tz.utcoffset(always_before) == tz.utcoffset(now_before)) assert(tz.utcoffset(now_before) != tz.utcoffset(always_after)) The assertions would crash on 2022c. [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1992692/+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
