All autopkgtests for the newly accepted tzdata (2022g-0ubuntu0.20.04.1) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

libical3/3.0.8-1 (armhf)


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!

-- 
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/1998321

Title:
  tzdata 2022g release

Status in tzdata package in Ubuntu:
  New
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed

Bug description:
  The 2022g release contains the following changes:

  * The northern edge of Chihuahua changes to US timekeeping.
  * Much of Greenland stops changing clocks after March 2023.
  * Fix some pre-1996 timestamps in northern Canada.
  * C89 is now deprecated; please use C99 or later.
  * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS
  * In C code, use more C23 features if available.
  * C23 timegm now supported by default
  * Fixes for unlikely integer overflows

  Changes to future timestamps:

  In the Mexican state of Chihuahua, the border strip near the US will
  change to agree with nearby US locations on 2022-11-30. The strip's
  western part, represented by Ciudad Juárez, switches from -06 all year
  to -07/-06 with US DST rules, like El Paso, TX. The eastern part,
  represented by Ojinaga, will observe US DST next year, like Presidio,
  TX.  (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez
  splits from America/Ojinaga.

  Much of Greenland, represented by America/Nuuk, stops observing winter
  time after March 2023, so its daylight saving time becomes standard
  time.  (Thanks to Jonas Nyrup and Jürgen Appel.)

  ICU change: https://unicode-org.atlassian.net/browse/ICU-22217
  CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
  compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

  [ Test Case for all releases ]
  1) dpkg -s tzdata | grep ^Version
  2) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1
    -> should have output, last dates should be in 2499

  
  [Test case for releases >= 20.04 LTS]

  from datetime import datetime, timedelta
  from icu import ICUtzinfo, TimeZone
  tz = ICUtzinfo(TimeZone.createTimeZone("America/Ciudad_Juarez"))
  assert(tz.utcoffset(datetime(2022, 12, 1)) == timedelta(hours=-7))

  [Test Case for releases <= 20.04 LTS]

  Additionally, an upstream update of tzdata removed the 'old' SystemV 
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and 
earlier releases. Subsequently, these should be checked for using the following:
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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

Reply via email to