tzdata 2022e release

[Benjamin Drung]

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.

[Launchpad Janitor (janitor)]

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 <email address hidden> Wed, 12 Oct 2022 21:26:34 +0200

[Ponnuvel Palaniyappan (pponnuvel)]

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).

[Benjamin Drung (bdrung)]

Uploaded SRU to bionic, focal, and jammy.

[Steve Beattie (sbeattie)]

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 "<stdin>", line 1, in <module>
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/

[Steve Beattie (sbeattie)]

tzdata updates were published to both trusty/esm and xenial/esm. Thanks!

[Timo Aaltonen (tjaalton)]

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.

[Timo Aaltonen (tjaalton)]

Hello Benjamin, or anyone else affected,

Accepted tzdata into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2022e-0ubuntu0.20.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-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. 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.

[Timo Aaltonen (tjaalton)]

Hello Benjamin, or anyone else affected,

Accepted tzdata into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2022e-0ubuntu0.18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted tzdata (2022e-0ubuntu0.22.04.0) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

chrony/4.2-2ubuntu2 (armhf)
gnustep-base/1.28.0-4build1 (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#tzdata

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Simon Chopin (schopin)]

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.

[Simon Chopin (schopin)]

Both regressions were retried and succeeded.

[Launchpad Janitor (janitor)]

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 <email address hidden> Mon, 17 Oct 2022 15:51:00 +0200

[Brian Murray (brian-murray)]

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.

[Launchpad Janitor (janitor)]

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 <email address hidden> Mon, 17 Oct 2022 15:59:56 +0200

[Launchpad Janitor (janitor)]

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 <email address hidden> Mon, 17 Oct 2022 15:48:16 +0200