[Bug 2052739] Re: tzdata 2024a release
Benjamin Drung
2052739 at bugs.launchpad.net
Thu Feb 22 19:35:47 UTC 2024
Some time ago, I converted all the manual tests from the SRU
documentation into autopkgtests. For example
https://git.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/tzdata/commit/?id=a70967f356720a37571dd0a301c3c99bea11abc7
implements the python3-icu test mentioned on the SRU documentation.
The python3-icu uses bin:tzdata-icu (or bin:tzdata on older releases).
The python3-icu test is about verifying that python3-icu does not break
after tzdata was updated.
I am also driving the updates for ESM by preparing them for bionic,
xenial, and trusty: https://code.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/tzdata/+git/tzdata
--
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/2052739
Title:
tzdata 2024a release
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Focal:
Confirmed
Status in tzdata source package in Jammy:
Confirmed
Status in tzdata source package in Mantic:
Confirmed
Bug description:
[ Impact ]
The 2024a release contains the following changes:
* Kazakhstan unifies on UTC+5 beginning 2024-03-01.
* Palestine springs forward a week later after Ramadan.
* zic no longer pretends to support indefinite-past DST.
* localtime no longer mishandles Ciudad Juárez in 2422.
[ Test Plan ]
Test cases were added to the autopkgtest to cover the testing:
* python: test_2024a
* python-icu: test_2024a (only for focal and newer)
So the test plan is to check that the autopkgtest succeeds.
[ Other Info ]
The autopkgtest for chrony is flaky on jammy and newer (see bug
#2002910).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739/+subscriptions
More information about the foundations-bugs
mailing list