[Touch-packages] [Bug 1992692] Re: tzdata 2022e release
This bug was fixed in the package tzdata - 2022e-0ubuntu0.20.04.0 --- tzdata (2022e-0ubuntu0.20.04.0) focal; urgency=medium * New upstream releases (LP: #1992692): - 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. (LP: #1969671) - Jordan and Syria switch from +02/+03 with DST to year-round * debian/tzdata.templates and debian/tzdata.config: - Convert Europe/Kiev into Europe/Kyiv - Remove Uzhgorod and Zaporozhye * Update the ICU timezone data to 2022e -- Benjamin Drung Mon, 17 Oct 2022 15:48:16 +0200 -- 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
[Touch-packages] [Bug 1992692] Re: tzdata 2022e release
This bug was fixed in the package tzdata - 2022e-0ubuntu0.18.04.0 --- tzdata (2022e-0ubuntu0.18.04.0) bionic; urgency=medium * New upstream releases (LP: #1992692): - 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. (LP: #1969671) - Jordan and Syria switch from +02/+03 with DST to year-round * debian/tzdata.templates and debian/tzdata.config: - Convert Europe/Kiev into Europe/Kyiv - Remove Uzhgorod and Zaporozhye -- Benjamin Drung Mon, 17 Oct 2022 15:59:56 +0200 ** Changed in: tzdata (Ubuntu Bionic) 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/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
[Touch-packages] [Bug 1992692] Re: tzdata 2022e release
This bug was fixed in the package tzdata - 2022e-0ubuntu0.22.04.0 --- tzdata (2022e-0ubuntu0.22.04.0) jammy; urgency=medium * New upstream releases (LP: #1992692): - 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. (LP: #1969671) - Jordan and Syria switch from +02/+03 with DST to year-round * debian/tzdata.templates and debian/tzdata.config: - Convert Europe/Kiev into Europe/Kyiv - Remove Uzhgorod and Zaporozhye * Update the ICU timezone data to 2022e -- Benjamin Drung Mon, 17 Oct 2022 15:51:00 +0200 ** Changed in: tzdata (Ubuntu Jammy) 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/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
[Touch-packages] [Bug 1992692] Re: tzdata 2022e release
Both regressions were retried and succeeded. -- 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 Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed 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
[Touch-packages] [Bug 1992692] Re: tzdata 2022e release
Hi, I verified the 2022e-0ubuntu0.XX.04.0 packages on jammy, focal and bionic using fresh LXC containers. I'll look into the autopkgtest regressions as well. ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-jammy ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-jammy -- 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 Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed 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
[Touch-packages] [Bug 1992692] Re: tzdata 2022e release
Hello Benjamin, or anyone else affected, Accepted tzdata into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2022e-0ubuntu0.22.04.0 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: tzdata (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy ** Changed in: tzdata (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- 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 Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed 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
[Touch-packages] [Bug 1992692] Re: tzdata 2022e release
tzdata updates were published to both trusty/esm and xenial/esm. Thanks! ** Also affects: tzdata (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: tzdata (Ubuntu Trusty) Status: New => Fix Released ** Changed in: tzdata (Ubuntu Xenial) Status: New => 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/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: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New 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
[Touch-packages] [Bug 1992692] Re: tzdata 2022e release
FYI, because of the way python has incorrectly handled timezomes in the past, the python3-icu tests fail, at least when run in a timezone that is -0700 for releases like bionic and older. For example, taking the very similar testcase for the prior 2022c update in LP: #1986984, on ubuntu 18.04 it results: ubuntu@sec-bionic-amd64:~$ apt policy tzdata | grep Installed: WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Installed: 2022c-0ubuntu0.18.04.0 ubuntu@sec-bionic-amd64:~$ python3 Python 3.6.9 (default, Jun 29 2022, 11:45:57) [GCC 8.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> from datetime import datetime >>> from icu import ICUtzinfo, TimeZone >>> tz = ICUtzinfo(TimeZone.createTimeZone("America/Santiago")) >>> always_before = datetime(2022, 9, 1) >>> now_before = datetime(2022, 9, 8) >>> always_after = datetime(2022, 9, 12) >>> assert(tz.utcoffset(always_before) == tz.utcoffset(now_before)) >>> assert(tz.utcoffset(now_before) != tz.utcoffset(always_after)) Traceback (most recent call last): File "", line 1, in AssertionError >>> tz.utcoffset(now_before) datetime.timedelta(-1, 75600) >>> tz.utcoffset(always_after) datetime.timedelta(-1, 75600) For ensuring the ESM releases were handling the changes correctly, I created a python3-tz[1] based script at https://git.launchpad.net/qa- regression-testing/tree/scripts/test-tzdata.py and in fact, just pushed an added testcase for this bug that looks like https://git.launchpad.net/qa-regression-testing/tree/scripts/test- tzdata.py#n95 Thanks. [1] The pytz project documents a lot of the issues with timezone handling in older pythons at their project page: https://pytz.sourceforge.net/ -- 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 Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New 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
[Touch-packages] [Bug 1992692] Re: tzdata 2022e release
Uploaded SRU to bionic, focal, and jammy. -- 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 Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New 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
[Touch-packages] [Bug 1992692] Re: tzdata 2022e release
** Description changed: 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. -- 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 Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New 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
[Touch-packages] [Bug 1992692] Re: tzdata 2022e release
** Patch added: "tzdata_2022e-0ubuntu0.16.04+esm1.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1992692/+attachment/5624844/+files/tzdata_2022e-0ubuntu0.16.04+esm1.debdiff -- 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 Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New 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 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
[Touch-packages] [Bug 1992692] Re: tzdata 2022e release
** Patch added: "tzdata_2022e-0ubuntu0.18.04.0.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1992692/+attachment/5624835/+files/tzdata_2022e-0ubuntu0.18.04.0.debdiff -- 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 Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New 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 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
[Touch-packages] [Bug 1992692] Re: tzdata 2022e release
Is there a timeline to backport to Xenial? A customer using Xenial/ESM is specifically interested in the patch to fix the Jordan tz (which is using DLS all-year round going forward). ** Tags added: sts -- 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 Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New 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 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
[Touch-packages] [Bug 1992692] Re: tzdata 2022e release
** Patch added: "tzdata_2022e-0ubuntu0.20.04.0.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1992692/+attachment/5624585/+files/tzdata_2022e-0ubuntu0.20.04.0.debdiff -- 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 Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New 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 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
[Touch-packages] [Bug 1992692] Re: tzdata 2022e release
** Patch added: "tzdata_2022e-0ubuntu0.22.04.0.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1992692/+attachment/5624584/+files/tzdata_2022e-0ubuntu0.22.04.0.debdiff -- 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 Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New 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 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
[Touch-packages] [Bug 1992692] Re: tzdata 2022e release
** Patch removed: "tzdata_2022e-0ubuntu0.22.04.0.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1992692/+attachment/5624578/+files/tzdata_2022e-0ubuntu0.22.04.0.debdiff -- 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 Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New 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 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
[Touch-packages] [Bug 1992692] Re: tzdata 2022e release
** Also affects: tzdata (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Focal) Importance: Undecided Status: New ** Patch added: "tzdata_2022e-0ubuntu0.22.04.0.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1992692/+attachment/5624578/+files/tzdata_2022e-0ubuntu0.22.04.0.debdiff -- 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 Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New 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 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
[Touch-packages] [Bug 1992692] Re: tzdata 2022e release
This bug was fixed in the package tzdata - 2022e-0ubuntu1 --- tzdata (2022e-0ubuntu1) kinetic; urgency=medium * New upstream releases (LP: #1992692): - 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. (LP: #1969671) - Jordan and Syria switch from +02/+03 with DST to year-round +03. * Update the ICU timezone data to 2022d, as 2022e isn't available yet * debian/tzdata.config: convert Europe/Uzhgorod and Europe/Zaporozhye into Europe/Kyiv. * debian/tzdata.templates: Remove Uzhgorod and Zaporozhye -- Benjamin Drung Wed, 12 Oct 2022 21:26:34 +0200 ** Changed in: tzdata (Ubuntu) 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/1992692 Title: tzdata 2022e release Status in tzdata package in Ubuntu: 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 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
[Touch-packages] [Bug 1992692] Re: tzdata 2022e release
** Changed in: tzdata (Ubuntu) Status: New => Fix Committed -- 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 Committed 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 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
[Touch-packages] [Bug 1992692] Re: tzdata 2022e release
** Description changed: 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. + 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 -- 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: New 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 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
[Touch-packages] [Bug 1992692] Re: tzdata 2022e release
** Changed in: tzdata (Ubuntu) Importance: Undecided => Critical -- 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: New 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. 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
[Touch-packages] [Bug 1992692] Re: tzdata 2022e release
** Summary changed: - tzdata 2022c release + tzdata 2022e release -- 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: New 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. 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