Bug#1111991: trixie-pu: package tzdata/2025b-4+deb13u1
Package: release.debian.org
Severity: normal
Tags: trixie
X-Debbugs-Cc: tzdata@packages.debian.org
Control: affects -1 + src:tzdata
User: release.debian.org@packages.debian.org
Usertags: pu
[ Reason ]
tzdata contains a leap second file which is updated twice a year, and
which has an expiration date on 28 December 2025. It has been updated
upstream on July 7th, but there has been no upstream release since then.
While it can be fixed in the 13.2 point release, or while there might be
a new upstream release in the mean time, I would prefer to sync the
change with the one in oldstable (see #1111989), in order to prevent a
"regression" on upgrade.
[ Impact ]
There is no leap second added at the end of 2025, so the impact is
relatively low, but NTP servers using this file usually emit warnings
28 days before the expiration date.
[ Tests ]
There are no tests for this change.
[ Risks ]
The risk is quite low, the changes are minimal and routinely done twice
a year.
[ 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 change simply consists in updating leap-seconds.list from upstream,
who took it from NIST following an IERS Bulletin. This file is then
shipped in /usr/share/zoneinfo/leap-seconds.list and is shipped in a
different format in /usr/share/zoneinfo/leapseconds.
[ Other info ]
Given the limited changes, I have already uploaded the package to the
archive. Thanks for considering.
diff -Nru tzdata-2025b/debian/changelog tzdata-2025b/debian/changelog
--- tzdata-2025b/debian/changelog 2025-06-28 10:23:31.000000000 +0000
+++ tzdata-2025b/debian/changelog 2025-08-24 20:12:10.000000000 +0000
@@ -1,3 +1,9 @@
+tzdata (2025b-4+deb13u1) trixie; urgency=medium
+
+ * Backport leap second update from upstream
+
+ -- Aurelien Jarno <aurel32@debian.org> Sun, 24 Aug 2025 22:12:10 +0200
+
tzdata (2025b-4) unstable; urgency=medium
[ Aurelien Jarno ]
diff -Nru tzdata-2025b/debian/patches/No-leap-second-on-2025-12-31.patch tzdata-2025b/debian/patches/No-leap-second-on-2025-12-31.patch
--- tzdata-2025b/debian/patches/No-leap-second-on-2025-12-31.patch 1970-01-01 00:00:00.000000000 +0000
+++ tzdata-2025b/debian/patches/No-leap-second-on-2025-12-31.patch 2025-08-24 20:12:10.000000000 +0000
@@ -0,0 +1,46 @@
+From be764d7bd3d6fd00fefdaf9027d9886b1e5cb741 Mon Sep 17 00:00:00 2001
+From: Tim Parenti <tim@timtimeonline.com>
+Date: Mon, 7 Jul 2025 12:28:29 -0400
+Subject: [PATCH] No leap second on 2025-12-31
+
+Per IERS Bulletin C 70 (2025-07-07).
+https://hpiers.obspm.fr/iers/bul/bulc/bulletinc.70
+
+* leap-seconds.list: Update file from IERS, retrieved from
+https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list
+---
+ leap-seconds.list | 8 ++++----
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+diff --git a/leap-seconds.list b/leap-seconds.list
+index 6f861c88..649a22c6 100644
+--- a/leap-seconds.list
++++ b/leap-seconds.list
+@@ -60,15 +60,15 @@
+ #
+ # The following line shows the last update of this file in NTP timestamp:
+ #
+-#$ 3945196800
++#$ 3960835200
+ #
+ # 2) Expiration date of the file given on a semi-annual basis: last June or last December
+ #
+-# File expires on 28 December 2025
++# File expires on 28 June 2026
+ #
+ # Expire date in NTP timestamp:
+ #
+-#@ 3975868800
++#@ 3991593600
+ #
+ #
+ # LIST OF LEAP SECONDS
+@@ -117,4 +117,4 @@
+ # please see the readme file in the 'source' directory :
+ # https://hpiers.obspm.fr/iers/bul/bulc/ntp/sources/README
+ #
+-#h 848434d5 570f7ea8 d79ba227 a00fc821 f608e2d4
++#h 49db2447 571e5e1b 2f002a53 9c8da8e4 39b8e49e
+--
+2.47.2
+
diff -Nru tzdata-2025b/debian/patches/series tzdata-2025b/debian/patches/series
--- tzdata-2025b/debian/patches/series 2025-06-28 10:23:31.000000000 +0000
+++ tzdata-2025b/debian/patches/series 2025-08-24 20:12:10.000000000 +0000
@@ -1 +1,2 @@
Correct-timezone-symlinks-when-using-BACKWARD-backward-PA.patch
+No-leap-second-on-2025-12-31.patch
Reply to: