Thanks Brian, these look good, will take these into Trusty and Precise
ESM.
(For the record, I noticed that the 2020d dropped the US/Pacific-New
timezone, which was a symlink to the US/Pacific timezone. Testing
demonstrated that a system with a configured Pacific-New timezone
functioned correctly post package upgrade. See debian bug 815200 for
details on why it was dropped.)

Also, Ubuntu Security Team ack on publishing the xenial, bionic, focal,
and groovy versions to the respective -security pockets for those
releases, despite building in -proposed; there are no binaries or
dependencies that should cause an issue.

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

Title:
  new upstream release 2020d

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Precise:
  In Progress
Status in tzdata source package in Trusty:
  In Progress
Status in tzdata source package in Xenial:
  In Progress
Status in tzdata source package in Bionic:
  In Progress
Status in tzdata source package in Focal:
  In Progress
Status in tzdata source package in Groovy:
  Fix Committed

Bug description:
  New upstream version, affecting the following future timestamps:
    - Fiji starts DST later than usual, on 2020-12-20.
    - Palestine ends DST earlier than predicted, on 2020-10-24.
    - Revised predictions for Morocco's changes starting in 2023.
    - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08.
    - Macquarie Island has stayed in sync with Tasmania since 2011.
    - Casey, Antarctica is at +08 in winter and +11 in summer since 2018.

  Additionally, upstream removed the "old" SystemV timezones, but the
  SRU will ensure that they are kept. Subsequently, these should be
  checked for using the following:

  zdump -v SystemV/MST7
  zdump -v America/Phoenix

  The information returned by SystemV/MST7 should be included in
  America/Phoenix's output.

  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 needed to be greped for in
  /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".]
  This is compared to the same output after the updated package got
  installed. If those are different the verification is considered done.

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