[ Reason ]
A new upstream version of tzdata, 2026f, has been released with a change
for Cuba, which will not fall back to -05 on 2026-11-01.
[ Impact ]
If this version is not accepted, the clock of users in Cuba will start
differing on 2026-11-01.
[ Tests ]
There are no tests for these changes.
[ Risks ]
The risks to import new upstream versions of tzdata are quite low, and
is done routinely. This version just got uploaded to unstable and is not
yet in testing. However this time the changes are relatively small,
compensating the risks of a less tested (in debian) release.
[ 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 2026f upstream version contains the following change to
future timestamps:
- Cuba will not fall back to -05 on 2026-11-01 and instead plans to
maintain -04 through 2027-11-07.
It also contains some historical changes for Brazil and Ukraine, and
updates to the comments regarding the ongoing Canadian changes. It also
changes the comments of the leapseconds file to explain the expiration
date in that file is now obsolete.
In addition the debian packaging includes an update of the upstream
signing key, given it was expired.
[ Other info ]
Given that the next point release is scheduled for Nov 14, this will
need to go through stable-updates.
I have just uploaded the package to the archive.