package tzdata 2024a-3ubuntu1.1 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 10

[Justin Bache]

[ Impact ]

Updating the tzdata package will fail on systems that have a legacy timezone selected (that is not updated to a recent one during dpkg-reconfigure). Example:

```
$ schroot-wrapper -p tzdata -c jammy -u root
(jammy)root@host:~# ln -sf /usr/share/zoneinfo/EST5EDT /etc/localtime
(jammy)root@host:~# DEBIAN_FRONTEND=noninteractive dpkg-reconfigure tzdata
(jammy)root@host:~# echo $?
10
```

[ Test Plan ]

Test cases were added for Ubuntu 24.10 (oracular), Ubuntu 24.04 (noble), and Ubuntu 22.04 (jammy) to the autopkgtest to cover the testing:

* debconf: test_legacy_timezones

So the test plan is to check that the autopkgtest succeeds. For older releases, run the example given above. It should exit with 0 and keep the configured timezone.

[ Where problems can occur ]

The fix touches the code that is used for configuring the timezone. That can cause package update to fail. There are autopkgtest to avoid regressions.

[ Original report ]

ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: tzdata 2024a-3ubuntu1.1
ProcVersionSignature: Ubuntu 6.5.0-1018.21-raspi 6.5.13
Uname: Linux 6.5.0-1018-raspi aarch64
ApportVersion: 2.28.1-0ubuntu3
Architecture: arm64
CasperMD5CheckResult: unknown
CloudArchitecture: aarch64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: config-disk (/dev/mmcblk0p1)
Date: Mon Jun 24 09:04:36 2024
DuplicateSignature:
 package:tzdata:2024a-3ubuntu1.1
 Setting up tzdata (2024a-3ubuntu1.1) ...
 dpkg: error processing package tzdata (--configure):
  installed tzdata package post-installation script subprocess returned error exit status 10
ErrorMessage: installed tzdata package post-installation script subprocess returned error exit status 10
PackageArchitecture: all
Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.22.6ubuntu6
 apt 2.7.14build2
SourcePackage: tzdata
Title: package tzdata 2024a-3ubuntu1.1 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 10
UpgradeStatus: Upgraded to noble on 2024-06-24 (0 days ago)

[Benjamin Drung (bdrung)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. What happens when you retry?

```
sudo apt install -f
```

[Nagabhiru Sudhakar (nagabhiru888)]

I am also facing same issue with tzdata 2024a-3ubuntu1.1 and it is a bug with package.

Please check and fix the bug.

[Nagabhiru Sudhakar (nagabhiru888)]

It is critically one and need fix asap.

[Benjamin Drung (bdrung)]

There is no error message in the logs that would explain the failure. Are you willing to help debugging the failure to find (and then resolve) the root cause?

Can you edit /var/lib/dpkg/info/tzdata.postinst and add `set -x` in line two and then run

```
sudo apt install -f
```

[Nagabhiru Sudhakar (nagabhiru888)]

Please refer below error output as per request.

# apt install -f
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up tzdata (2024a-0ubuntu0.22.04.1) ...
+ LC_ALL=C
+ LANG=C
+ unset TZ
+ umask 022
+ . /usr/share/debconf/confmodule
+ [ ! ]
+ PERL_DL_NONLAZY=1
+ export PERL_DL_NONLAZY
+ [ ]
+ exec /usr/share/debconf/frontend /var/lib/dpkg/info/tzdata.postinst configure 2024a-0ubuntu0.22.04.1
dpkg: error processing package tzdata (--configure):
 installed tzdata package post-installation script subprocess returned error exit status 10
Errors were encountered while processing:
 tzdata
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

[Benjamin Drung (bdrung)]

So the debconf call fails. Can you run debconf with debug mode?

```
sudo DEBCONF_DEBUG=developer debconf /var/lib/dpkg/info/tzdata.postinst configure 2024a-0ubuntu0.22.04.1
```

[Nagabhiru Sudhakar (nagabhiru888)]

The latest version "2024a-0ubuntu0.22.04.1" getting installed rightly if my instance time zone is in UTC.
Othereise it is failing and it shouldn't impact the timezone which set as per our requirment.
Looks it required some fix.

# date
Mon Jul 1 12:31:50 CEST 2024
# ls -ld /etc/localtime
lrwxrwxrwx 1 root root 23 Jun 30 15:53 /etc/localtime -> /usr/share/zoneinfo/CET
# DEBCONF_DEBUG=developer debconf /var/lib/dpkg/info/tzdata.postinst configure 2024a-0ubuntu0.22.04.1
debconf (developer): starting /var/lib/dpkg/info/tzdata.postinst configure 2024a-0ubuntu0.22.04.1
debconf (developer): <-- VERSION 2.0
debconf (developer): --> 0 2.0
debconf (developer): <-- GET tzdata/Areas
debconf (developer): --> 0 Etc
debconf (developer): <-- GET tzdata/Zones/Etc
debconf (developer): --> 0 UTC
debconf (developer): <-- STOP

Current default time zone: 'Etc/UTC'
Local time is now: Mon Jul 1 10:32:02 UTC 2024.
Universal Time is now: Mon Jul 1 10:32:02 UTC 2024.
Run 'dpkg-reconfigure tzdata' if you wish to change it.

# ls -ld /etc/localtime
lrwxrwxrwx 1 root root 27 Jul 1 10:32 /etc/localtime -> /usr/share/zoneinfo/Etc/UTC
#

[Launchpad Janitor (janitor)]

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

[Patrick Schratz (pat-s)]

I can confirm the issue as well, and can also confirm that changing TZ from ETC to UTC fixes the issue for now.

[Ashwin Kini (akini93)]

This affects us too with same error.

seen on Bionic instance with version: 2024a-0ubuntu0.18.04.1+esm1 old version: 2023c-0ubuntu0.18.04.

earlier:
/etc/localtime -> /usr/share/zoneinfo/CET.

workaround:

sudo ln -sf /usr/share/zoneinfo/US/Central /etc/localtime.

and then installation went through fine.

Please advise if CET is no more supported and along with that if there are more TZ's that are deprecated (if so) or if this is a bug that will be fixed in next release (release # and ETA pls)

Thanks

[Benjamin Drung (bdrung)]

I can reproduce the failure in a bionic, jammy, and oracular chroot:

```
$ schroot-wrapper -p tzdata -c jammy -u root
(jammy)root@host:~# ln -sf /usr/share/zoneinfo/EST5EDT /etc/localtime
(jammy)root@host:~# DEBIAN_FRONTEND=noninteractive dpkg-reconfigure tzdata
(jammy)root@host:~# echo $?
10
```

This is a bug that should be fixed. dpkg-reconfigure should not fail on those legacy timezones.

Upstream dropped those legacy timezones in the 2024b release. So I recommend switching to the country/city timezones (like US/Central) or to the Etc/GMT* zones in case you want to ignore DST.

The current plan is to keep these legacy timezones in place for the stable release (to not enforce those changes to our customers on the stable releases).

[Ashwin Kini (akini93)]

Thanks Benjamin,

We will try to move to Country/city timezones, however we have many systems on bionic/trusty (yes trusty!), and it is affecting all of them. eg: 2024a-0ubuntu0.18.04.1+esm1 shipped via canonical ESM also is buggy.

Would you or someone would possibly know if this will be fixed/patched and released on 2024a release for affected ubuntu releases sooner - any ETA on the fix etc? (not sure if you are the right person to answer this)

Thanks again.

[Benjamin Drung (bdrung)]

This bug is fixed in tzdata 2024b-4ubuntu1 which updates those legacy timezones.

The fix for this bug will be bundled with the 2024b SRU, because this bug is triggered on package updates.

[Benjamin Drung (bdrung)]

tzdata 2024b-1ubuntu2.1 uploaded to oracular. The remaining series will be done tomorrow.

[Benjamin Drung (bdrung)]

Uploaded fixes for noble, jammy, focal. They are waiting in the unapproved queue for review.

[Łukasz Zemczak (sil2100)]

Hello Justin, or anyone else affected,

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

[Łukasz Zemczak (sil2100)]

Hello Justin, or anyone else affected,

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

[Łukasz Zemczak (sil2100)]

Hello Justin, or anyone else affected,

Accepted tzdata into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2024b-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.

[Łukasz Zemczak (sil2100)]

Hello Justin, or anyone else affected,

Accepted tzdata into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2024b-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 (2024b-0ubuntu0.20.04) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

postgresql-12/12.22-0ubuntu0.20.04.1 (s390x)
python-dateutil/unknown (ppc64el)

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/focal/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 (2024b-0ubuntu0.24.04) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

chrony/4.5-1ubuntu4.2 (ppc64el)
dask.distributed/unknown (ppc64el)
golang-github-lib-pq/1.10.9-2 (ppc64el)
php8.3/8.3.6-0ubuntu0.24.04.2 (ppc64el)
postgresql-16/16.6-0ubuntu0.24.04.1 (ppc64el)
tzdata/2024b-0ubuntu0.24.04 (ppc64el)

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/noble/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 (2024b-1ubuntu2.1) for oracular have finished running.
The following regressions have been reported in tests triggered by the package:

chrony/4.5-3ubuntu3 (armhf)
chrony/unknown (ppc64el)
golang-github-lib-pq/1.10.9-2 (ppc64el)
pandas/unknown (ppc64el)
partd/unknown (ppc64el)
php8.3/unknown (amd64)
python3.12/3.12.7-1ubuntu1 (amd64, ppc64el, s390x)
python3.13/3.13.0-1 (arm64, ppc64el, s390x)
systemd/256.5-2ubuntu3.1 (amd64)
systemd/unknown (ppc64el)
tzdata/2024b-1ubuntu2.1 (ppc64el)

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/oracular/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:

oracular: tzdata/2024b-1ubuntu2.1

* amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-oracular/oracular/amd64/t/tzdata/20241205_173859_adda8@/log.gz
* arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-oracular/oracular/arm64/t/tzdata/20241205_174701_2f4b5@/log.gz
* armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-oracular/oracular/armhf/t/tzdata/20241205_174739_d2a53@/log.gz
* ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-oracular/oracular/ppc64el/t/tzdata/20241213_232359_82d3c@/log.gz
* s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-oracular/oracular/s390x/t/tzdata/20241205_173856_af105@/log.gz

noble: tzdata/2024b-0ubuntu0.24.04

* amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/t/tzdata/20241205_181237_ab8a4@/log.gz
* arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/t/tzdata/20241205_180342_5794b@/log.gz
* armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/armhf/t/tzdata/20241205_180826_1089d@/log.gz
* ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/ppc64el/t/tzdata/20241211_113053_ff166@/log.gz
* s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/s390x/t/tzdata/20241205_180234_8d56b@/log.gz

jammy: tzdata/2024b-0ubuntu0.22.04

* amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/t/tzdata/20241213_081348_0329b@/log.gz
* arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/t/tzdata/20241213_082219_16cbb@/log.gz
* armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/armhf/t/tzdata/20241213_081958_f78c0@/log.gz
* ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/t/tzdata/20241213_091230_07e80@/log.gz
* s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/t/tzdata/20241213_081540_0e0e9@/log.gz

focal: tzdata/2024b-0ubuntu0.20.04

* amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/t/tzdata/20241205_172929_d71ba@/log.gz
* arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/t/tzdata/20241205_173428_d43d6@/log.gz
* armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/t/tzdata/20241205_173344_d43d6@/log.gz
* ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/t/tzdata/20241213_231233_33547@/log.gz
* s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/t/tzdata/20241205_173102_2a5f0@/log.gz

[Benjamin Drung (bdrung)]

And also run the manual test successfully:

```
$ schroot-wrapper -p tzdata -c jammy -u root -e
(jammy)root@nfnf:~# ln -sf /usr/share/zoneinfo/EST5EDT /etc/localtime
(jammy)root@nfnf:~# DEBIAN_FRONTEND=noninteractive dpkg-reconfigure tzdata

Current default time zone: 'EST5EDT'
Local time is now: Mon Dec 16 06:38:30 EST 2024.
Universal Time is now: Mon Dec 16 11:38:30 UTC 2024.

(jammy)root@nfnf:~# echo $?
0
(jammy)root@nfnf:~# dpkg -s tzdata | grep ^Version
Version: 2024b-0ubuntu0.22.04
```

[Benjamin Drung (bdrung)]

And also run the manual test successfully on focal:

```
schroot-wrapper -p tzdata -c focal -u root -e
(focal)root@nfnf:~# ln -sf /usr/share/zoneinfo/EST5EDT /etc/localtime
(focal)root@nfnf:~# DEBIAN_FRONTEND=noninteractive dpkg-reconfigure tzdata

Current default time zone: 'EST5EDT'
Local time is now: Mon Dec 16 06:41:56 EST 2024.
Universal Time is now: Mon Dec 16 11:41:56 UTC 2024.

(focal)root@nfnf:~# echo $?
0
(focal)root@nfnf:~# dpkg -s tzdata | grep ^Version
Version: 2024b-0ubuntu0.20.04
```

[Andreas Hasenack (ahasenack)]

There was an autopkgtest failure for oracular on ppc64el:

autopkgtest for python3.12/unknown: ppc64el: Regression ♻

Given the "unknown" version, and of course checking logs, I see it was an infrastructure problem. I retried it.

[Ashwin Kini (akini93)]

Hi,

Thanks for the fix. I am particularly looking for Ubuntu 18.04 bionic. We have Ubuntu ESM/PRO support.

The Version we have is: 2024a-0ubuntu0.18.04.1+esm1

Is there any plan to backport the fix to bionic ESM as well? Can you please let us know

Thanks
Ashwin

[Benjamin Drung (bdrung)]

I will consider backporting this fix to the ESM versions as well, but I am not sure if that is feasible (ESM updates should small and not too invasive).

[Marc Deslauriers (mdeslaur)]

Please also release this package into the security pocket as we want to keep them in sync. Thanks!

[Launchpad Janitor (janitor)]

This bug was fixed in the package tzdata - 2024b-1ubuntu2.1

---------------
tzdata (2024b-1ubuntu2.1) oracular; urgency=medium

  * Make remaining legacy timezones selectable in debconf (LP: #2070285)

tzdata (2024b-1ubuntu2) oracular; urgency=medium

  [ Aurelien Jarno ]
  * Build timezones with zic -b 'fat' (Closes: #1084111)
  * tzdata-legacy: bump Replaces: tzdata version to handle the
    Asia/Choibalsan move

  [ Benjamin Drung ]
  * Move UNIX System V zones back from backzone to backwards file
    to keep them unchanged for the stable release updates.

tzdata (2024b-1ubuntu1) oracular; urgency=medium

  * Merge with Debian unstable. 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
  * Update the ICU timezone data to 2024b
  * Add autopkgtest test case for ICU timezone data 2024b

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

  * New upstream release (LP: #2079966):
    - Improve historical data for Mexico, Mongolia, and Portugal.
    - System V names are now obsolescent.
    - The main data form now uses %z.
    - Asia/Choibalsan is now an alias for Asia/Ulaanbaatar
  * Add autopkgtest test case for 2024b release
  * Update Asia/Choibalsan to Asia/Ulaanbaatar on upgrade and move
    Asia/Choibalsan to tzdata-legacy
  * Bump Standards-Version to 4.7.0
  * generate_debconf_templates: Work around AttributeError on icu import

 -- Benjamin Drung <email address hidden> Tue, 03 Dec 2024 22:34:58 +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 - 2024b-0ubuntu0.24.04

---------------
tzdata (2024b-0ubuntu0.24.04) noble; urgency=medium

  * New upstream release (LP: #2079966):
    - Improve historical data for Mexico, Mongolia, and Portugal.
    - System V names are now obsolescent (reverted, see below).
    - The main data form now uses %z.
    - Asia/Choibalsan is now an alias for Asia/Ulaanbaatar
  * Add autopkgtest test case for 2024b release
  * Update the ICU timezone data to 2024b
  * Add autopkgtest test case for ICU timezone data 2024b
  * Build timezones with zic -b 'fat' (Closes: #1084111)
  * Move UNIX System V zones back from backzone to backwards file
    to keep them unchanged for the stable release updates.
  * Make remaining legacy timezones selectable in debconf (LP: #2070285)

 -- Benjamin Drung <email address hidden> Tue, 03 Dec 2024 22:59:32 +0100

[Launchpad Janitor (janitor)]

This bug was fixed in the package tzdata - 2024b-0ubuntu0.22.04

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

  * New upstream release (LP: #2079966):
    - Improve historical data for Mexico, Mongolia, and Portugal.
    - System V names are now obsolescent (reverted, see below).
    - The main data form now uses %z.
    - Asia/Choibalsan is now an alias for Asia/Ulaanbaatar
  * Add autopkgtest test case for 2024b release
  * Update the ICU timezone data to 2024b
  * Add autopkgtest test case for ICU timezone data 2024b
  * Build timezones with zic -b 'fat' (Closes: #1084111)
  * Move UNIX System V zones back from backzone to backwards file
    to keep them unchanged for the stable release updates.
  * Test debconf configuration with autopkgtest
  * Make remaining legacy timezones selectable in debconf (LP: #2070285)

 -- Benjamin Drung <email address hidden> Wed, 04 Dec 2024 00:58:03 +0100

[Launchpad Janitor (janitor)]

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

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

  * New upstream release (LP: #2079966):
    - Improve historical data for Mexico, Mongolia, and Portugal.
    - System V names are now obsolescent (reverted, see below).
    - The main data form now uses %z.
    - Asia/Choibalsan is now an alias for Asia/Ulaanbaatar
  * Add autopkgtest test case for 2024b release
  * Update the ICU timezone data to 2024b
  * Add autopkgtest test case for ICU timezone data 2024b
  * Move UNIX System V zones back from backzone to backwards file
    to keep them unchanged for the stable release updates.
  * Test debconf configuration with autopkgtest
  * Make remaining legacy timezones selectable in debconf (LP: #2070285)

 -- Benjamin Drung <email address hidden> Wed, 04 Dec 2024 02:07:48 +0100