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! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2079966 Title: tzdata 2024b release Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Noble: Fix Committed Status in tzdata source package in Oracular: Fix Committed Bug description: [ Impact ] The 2024b release contains the following changes: * Improve historical data for Mexico, Mongolia, and Portugal. * System V names are now obsolescent. * The main data form now uses %z. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2024b * python-icu: test_2024b (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). There are backward-incompatible changes included: Names present only for compatibility with UNIX System V (last released in the 1990s) have been moved to 'backward'. These names, which for post-1970 timestamps mostly just duplicate data of geographical names, were confusing downstream uses. Names moved to 'backward' are now Links to geographical names if there is an exact match since 1970, and remain Zones otherwise. Those needing the previous TZDB behavior, which does not match any real-world clocks, can find the old entries in 'backzone'. (Problem reported by Justin Grant.) We need to exclude this change for the SRU since it can/will break user setup (e. g. the user from bug #2055718) and it will break a handful of tests (including dateparser, pandas, posrtesql-16). See https://bugs.debian.org/1084190 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2079966/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
