[Bug 1965791] Re: Update tzdata to version 2022a

[Brian Murray]

Verified on Impish:

Setting up tzdata (2022a-0ubuntu0.21.10) ...

Current default time zone: 'America/Los_Angeles'
Local time is now:      Tue Mar 22 12:54:20 PDT 2022.
Universal Time is now:  Tue Mar 22 19:54:20 UTC 2022.
Run 'dpkg-reconfigure tzdata' if you wish to change it.

Setting up libmpdec3:amd64 (2.5.1-2build1) ...
Setting up libpython3.9-stdlib:amd64 (3.9.7-2build1) ...
Setting up libpython3-stdlib:amd64 (3.9.4-1build1) ...
Setting up python3.9 (3.9.7-2build1) ...
Setting up python3 (3.9.4-1build1) ...
running python rtupdate hooks for python3.9...
running python post-rtupdate hooks for python3.9...
Setting up python3-icu (2.5-1build4) ...
Processing triggers for libc-bin (2.34-0ubuntu3.2) ...
zdump test
----------
Asia/Gaza  Sat Mar 26 21:59:59 2022 UT = Sat Mar 26 23:59:59 2022 EET isdst=0 gmtoff=7200
Asia/Gaza  Sat Mar 26 22:00:00 2022 UT = Sun Mar 27 01:00:00 2022 EEST isdst=1 gmtoff=10800
python3-icu test
----------------
UTC offest is: 2:00:00

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1965791

Title:
  Update tzdata to version 2022a

Status in tzdata package in Ubuntu:
  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 Impish:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Released

Bug description:
  New upstream version affecting the following timestamp:

  $region/$timezone = Asia/Gaza

  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 'Mar.*2022'

  With the version of the package from -proposed this will show Mar 26
  not Mar 25.

  For releases with ICU timezone data verification is done using the following with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Asia/Gaza')); print(str(tz.utcoffset(datetime(2022, 3, 26))))'

  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:

  [Test Case for releases <= 20.04 LTS]
  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/1965791/+subscriptions