Bug#1129617: trixie-pu: package tzdata/2026a-0+deb13u1

Package: release.debian.org
Severity: normal
Tags: trixie
X-Debbugs-Cc: [email protected]
Control: affects -1 + src:tzdata
User: [email protected]
Usertags: pu

[ Reason ]
A new upstream version of tzdata, 2026a, has been released with a fix
for the transition time for Moldova, and an bump of the leap second list
expiration date from 28 June 2026 to 28 December 2026.

The 2025c release never went into trixie as it only contained changes to
past timestamps and a leap second update that has already been done
through a patch in debian version 2025b-4+deb13u1.

[ Impact ]
This time the impact of not accepting this update is relatively low.
The transition time for Moldova has been wrong since 2022, and only
leads to the clocks being wrong during one hour. There is still until
end of May to provide and update of the leap second list.

[ Tests ]
Some users will have the wrong time on their system.

[ Risks ]
The risk to import new upstream versions of tzdata are quite low, and is
done routinely. Note however that this version got released upstream 2
days ago, and I has just been uploaded to sid. It will take 2 more days
until it migrates to testing.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
The 2025c and 2026a upstream versions contains the following changes to
past and future timestamps:

Since 2022 Moldova has observed EU transition times, that is, it
has sprung forward at 03:00, not 02:00, and has fallen back at
04:00, not 03:00.

Baja California agreed with California’s DST rules in 1953 and in
1961 through 1975, instead of observing standard time all year.