tzdata 2024a release

[Benjamin Drung]

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

[Launchpad Janitor (janitor)]

This bug was fixed in the package tzdata - 2024a-1ubuntu1

---------------
tzdata (2024a-1ubuntu1) noble; urgency=medium

  * Merge with Debian unstable (LP: #2052739). Remaining changes:
    - Ship ICU timezone data which are utilized by PHP in tzdata-icu
    - Add autopkgtest test case for ICU timezone data
    - Do not rename NEWS into changelog.gz, this fixes a build failure on
      moment-timezone.js
    - Point Vcs-Browser/Git to Launchpad
    - generate_debconf_templates: Work around AttributeError on icu import
  * Update the ICU timezone data to 2024a
  * Add autopkgtest test case for ICU timezone data 2024a

tzdata (2024a-1) unstable; urgency=medium

  * New upstream version 2024a
     - Kazakhstan unifies on UTC+5 beginning 2024-03-01.
     - Palestine springs forward a week later after Ramadan.
  * Add autopkgtest test case for 2024a release

 -- Benjamin Drung <email address hidden> Thu, 08 Feb 2024 23:00:15 +0100

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Benjamin Drung (bdrung)]

A few hours ago I uploaded the tzdata updates for the stable releases. They are waiting in the unapproved queue.

[Andreas Hasenack (ahasenack)]

The SRU documentation[1] on tzdata describes other, or additional, tests, to be performed in this package. Is that:
a) assumed, and will be done?
b) autopkgtests cover it?
c) was forgotten, and should be added to the test plan?

1. https://wiki.ubuntu.com/StableReleaseUpdates#tzdata

[Andreas Hasenack (ahasenack)]

I'm not familiar with this package, so maybe not the best person to review this SRU, but here is another question. The SRU docs on tzdata also mention python3-icu, but I don't see an update for that package here or in the unapproved queue. Is that necessary? Or is it just about verifying that python3-icu does not break after bin:tzdata-icu was updated?

[Andreas Hasenack (ahasenack)]

Finally, the SRU doc also says this: "Uploads should also be made to any releases supported via ESM."

Are you going to drive that as well?

[Benjamin Drung (bdrung)]

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

[Andreas Hasenack (ahasenack)]

Hello Benjamin, or anyone else affected,

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

[Andreas Hasenack (ahasenack)]

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/2024a-0ubuntu0.22.04 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.

[Andreas Hasenack (ahasenack)]

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/2024a-0ubuntu0.20.04 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.

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

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

chrony/4.2-2ubuntu2 (s390x)
mtail/3.0.0~rc48-3 (amd64)

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!

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

All autopkgtests for the newly accepted tzdata (2024a-0ubuntu0.23.10) for mantic have finished running.
The following regressions have been reported in tests triggered by the package:

astropy/5.3.2-1 (arm64)

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/mantic/update_excuses.html#tzdata

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

Thank you!

[Benjamin Drung (bdrung)]

Verified successful autopkgtest on https://autopkgtest.ubuntu.com/packages/tzdata:

mantic:

* amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/t/tzdata/20240223_012444_0f113@/log.gz
* arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/arm64/t/tzdata/20240223_001555_7ca29@/log.gz
* armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/armhf/t/tzdata/20240223_023357_ee94e@/log.gz
* ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/ppc64el/t/tzdata/20240223_001617_0822f@/log.gz
* s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/s390x/t/tzdata/20240223_014437_7f723@/log.gz

jammy:

* amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/t/tzdata/20240223_001452_bda5d@/log.gz
* arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/t/tzdata/20240222_232655_62fd6@/log.gz
* armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/armhf/t/tzdata/20240222_235619_bdf0b@/log.gz
* ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/t/tzdata/20240222_232100_67fd5@/log.gz
* s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/t/tzdata/20240223_000331_11f77@/log.gz

focal:

* amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/t/tzdata/20240223_001845_45d0c@/log.gz
* arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/t/tzdata/20240222_235449_caab5@/log.gz
* armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/t/tzdata/20240222_235714_29cd7@/log.gz
* ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/t/tzdata/20240222_231755_6a4ad@/log.gz
* s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/t/tzdata/20240222_233135_dc0df@/log.gz

[Andreas Hasenack (ahasenack)]

@security, could you please sign off on this tzdata SRU, according to the SRU procedure[1] for this package?

1. https://wiki.ubuntu.com/StableReleaseUpdates#tzdata

[Marc Deslauriers (mdeslaur)]

+1 from security. Please remember to also release it to the -security pocket on all releases in addition to just -updates.

Thanks!

[Andreas Hasenack (ahasenack)]

The 7 day aging period will be hit later today. Releasing it now.

[Launchpad Janitor (janitor)]

This bug was fixed in the package tzdata - 2024a-0ubuntu0.23.10

---------------
tzdata (2024a-0ubuntu0.23.10) mantic; urgency=medium

  * New upstream version (LP: #2052739):
    - 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.
  * Add autopkgtest test case for 2024a release
  * Update the ICU timezone data to 2024a
  * Add autopkgtest test case for ICU timezone data 2024a

 -- Benjamin Drung <email address hidden> Wed, 21 Feb 2024 13:37:28 +0100

[Andreas Hasenack (ahasenack)]

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 - 2024a-0ubuntu0.22.04

---------------
tzdata (2024a-0ubuntu0.22.04) jammy; urgency=medium

  * New upstream version (LP: #2052739):
    - 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.
  * Add autopkgtest test case for 2024a release
  * Update the ICU timezone data to 2024a
  * Add autopkgtest test case for ICU timezone data 2024a

 -- Benjamin Drung <email address hidden> Wed, 21 Feb 2024 13:50:24 +0100

[Launchpad Janitor (janitor)]

This bug was fixed in the package tzdata - 2024a-0ubuntu0.20.04

---------------
tzdata (2024a-0ubuntu0.20.04) focal; urgency=medium

  * New upstream version (LP: #2052739):
    - 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.
  * Add autopkgtest test case for 2024a release
  * Update the ICU timezone data to 2024a
  * Add autopkgtest test case for ICU timezone data 2024a

 -- Benjamin Drung <email address hidden> Wed, 21 Feb 2024 14:36:33 +0100

[Vladimir (larrabee112)]

Hello.
After automatic upgrade of tzdata from 2023c-0ubuntu0.22.04.2 to 2024a-0ubuntu0.22.04
the previously set EST time zone was automatically changed to "America/Adak" or "America/Indiana/Indianapolis" on all our servers (50+).
Look like a bug in tzdata configure script.

[Andreas Hasenack (ahasenack)]

Hi Vladimir,

I'm sorry to hear that. What was the previously timezone that you had set? Just EST?

I filed https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718 about your report, if you could please amend it with more details.

[Andreas Hasenack (ahasenack)]

Given https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/comments/5, I don't think it's a regression in the update. Removing the regression-update tag.