[Bug 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
Benjamin Drung
2017999 at bugs.launchpad.net
Tue May 23 13:06:11 UTC 2023
Regarding the failing autopkgtest:
* python-tz on lunar:
- cinder/2:22.0.0-0ubuntu1.1, ironic/1:21.4.0-0ubuntu1, and senlin/1:15.0.0-0ubuntu1 fail on armhf due to an installation issue of mysql (probably bug #1980466)
- python-caldav/0.11.0-1 on armhf: not investigated yet
* tzdata on focal:
- postgresql-12/12.14-0ubuntu0.20.04.1 on amd64: not investigated yet
* tzdata on lunar:
- chrony/4.3-1ubuntu4 on armhf: Flaky test case (see bug #2002910)
- python-tz/2022.7.1-3: fixed by python-tz/2022.7.1-3ubuntu0.1
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to python-tz in Ubuntu.
https://bugs.launchpad.net/bugs/2017999
Title:
tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
Status in python-tz package in Ubuntu:
Fix Released
Status in tzdata package in Ubuntu:
Fix Released
Status in python-tz source package in Focal:
Invalid
Status in tzdata source package in Focal:
Fix Committed
Status in python-tz source package in Jammy:
Invalid
Status in tzdata source package in Jammy:
Fix Committed
Status in python-tz source package in Kinetic:
Invalid
Status in tzdata source package in Kinetic:
Fix Committed
Status in python-tz source package in Lunar:
Fix Committed
Status in tzdata source package in Lunar:
Fix Committed
Bug description:
[ Impact ]
Recent updates have been using `PACKRATDATA=backzone` in order to add
all out-of-scope lower-quality pre-1970 data back that existed in
earlier tzadata releases (see bug #2003797). However it also leads to
time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol,
and Pacific/Enderbury to change:
compared to 2023c-0ubuntu0.22.04.0
- America/Ensenada->only dst changes until 2022 are shown
- Atlantic/Jan_Mayen->now valid data is shown
- Europe/Tiraspol->only dst changes until 2010 are shown
[ Test Plan ]
Add an autopkgtest test case for post-1970 symlink consistency: Check
that the timezones for today and in half a year (= to cover DST
changes) do not change compared to building them without
`PACKRATDATA=backzone`.
The mentioned timezones that differed can also be tested manually.
Running following commands should have the same output (the output
mentioned here is from tzdata 2023c-0ubuntu0.22.04.0):
```
$ TZ=America/Ensenada date -d "2023-04-28 13:49 Z"
Fri Apr 28 06:49:00 PDT 2023
$ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z"
Fri Apr 28 15:49:00 CEST 2023
$ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z"
Fri Apr 28 16:49:00 EEST 2023
```
[ Where problems could occur ]
Timezone data could be wrong. Systems with incorrect timezone set may
observe unexpected time shift when updating the package.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+subscriptions
More information about the foundations-bugs
mailing list