public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] tzdata: Update to version 2026a
Date: Tue,  7 Apr 2026 17:11:05 +0200	[thread overview]
Message-ID: <20260407151108.3472751-32-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20260407151108.3472751-1-adolf.belka@ipfire.org>

- Update from version 2025c to 2026a
- No change to rootfile
- Changelog
    2026a
   Briefly:
      Moldova has used EU transition times since 2022.
      The "right" TZif files are no longer installed by default.
      -DTZ_RUNTIME_LEAPS=0 disables runtime support for leap seconds.
      TZif files are no longer limited to 50 bytes of abbreviations.
      zic is no longer limited to 50 leap seconds.
      Several integer overflow bugs have been fixed.
   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.  (Thanks to Heitor David Pinto.)
   Changes to data
     Remove Europe/Chisinau from zonenow.tab, as it now agrees with
      Europe/Athens for future timestamps.
   Changes to build procedure
     The Makefile no longer by default installs an alternate set
      of TZif files for system clocks that count leap seconds.
      Install with 'make REDO=posix_right' to get the old default,
      which is rarely used in major downstream distributions.
      If your system clock counts leap seconds (contrary to POSIX),
      it is better to install with 'make REDO=right_only'.
      This change does not affect the leapseconds file, which is still
      installed as before.
     The Makefile's POSIXRULES option, which was declared obsolete in
      release 2019b, has been removed.  The Makefile's build procedure
      thus no longer optionally installs the obsolete posixrules file.
   Changes to code
     Compiling with the new option -DTZ_RUNTIME_LEAPS=0 disables
      runtime support for leap seconds.  Although this conforms to
      POSIX, shrinks tzcode's attack surface, and is more efficient,
      it fails to support Internet RFC 9636's leap seconds.
     zic now can generate, and localtime.c can now use, TZif files that
      hold up to 256 bytes of abbreviations, counting trailing NULs.
      The previous limit was 50 bytes, and some tzdata TZif files were
      already consuming 40 bytes.  zic -v warns if it generates a file
      that exceeds the old 50-byte limit.
     zic -L can now generate TZif files with more than 50 leap seconds.
      This helps test TZif readers not limited to 50 leap seconds, as
      tzcode's localtime.c is; it has little immediate need for
      practical timekeeping as there have been only 27 leap seconds and
      possibly there will be no more, due to planned changes to UTC.
      zic -v warns if its output exceeds the old 50-second limit.
     localtime.c no longer accesses the posixrules file generated by
      zic -p.  Hence for obsolete and nonconforming settings like
      TZ="AST4ADT" it now typically falls back on US DST rules, rather
      than attempting to override this fallback with the contents of the
      posixrules file.  This removes library support that was declared
      obsolete in release 2019b, and fixes some undefined behavior.
      (Undefined behavior reported by GitHub user Naveed8951.)
     The posix2time, posix2time_z, time2posix, and time2posix_z
      functions now set errno=EOVERFLOW and return ((time_t) -1) if the
      result is not representable.  Formerly they had undefined behavior
      that could in practice result in crashing, looping indefinitely,
      or returning an incorrect result.  As before, these functions are
      defined only when localtime.c is compiled with the -DSTD_INSPIRED
      option.
     Some other undefined behavior, triggered by TZif files containing
      outlandish but conforming UT offsets or leap second corrections,
      has also been fixed.  (Some of these bugs reported by Naveed8951.)
     localtime.c no longer rejects TZif files that exactly fit in its
      internal structures, fixing off-by-one typos introduced in 2014g.
     zic no longer generates a no-op transition when
      simultaneous Rule and Zone changes cancel each other out.
      This occurs in tzdata only in Asia/Tbilisi on 1997-03-30.
      (Thanks to Renchunhui for a test case showing the bug.)
     zic no longer assumes you can fflush a read-only stream.
      (Problem reported by Christos Zoulas.)
     zic no longer generates UT offsets equal to -2**31 and localtime.c
      no longer accepts them, as they can cause trouble in both
      localtime.c and its callers.  RFC 9636 prohibits such offsets.
     zic -p now warns that the -p option is obsolete and likely
      ineffective.

Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
 lfs/tzdata | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/lfs/tzdata b/lfs/tzdata
index ca813384f..50410a8ff 100644
--- a/lfs/tzdata
+++ b/lfs/tzdata
@@ -1,7 +1,7 @@
 ###############################################################################
 #                                                                             #
 # IPFire.org - A linux based firewall                                         #
-# Copyright (C) 2007-2025  IPFire Team  <info@ipfire.org>                     #
+# Copyright (C) 2007-2026  IPFire Team  <info@ipfire.org>                     #
 #                                                                             #
 # This program is free software: you can redistribute it and/or modify        #
 # it under the terms of the GNU General Public License as published by        #
@@ -24,7 +24,8 @@
 
 include Config
 
-VER        = 2025c
+VER        = 2026a
+# https://data.iana.org/time-zones/releases/.tar.gx & .asc
 
 TZDATA_VER = $(VER)
 TZCODE_VER = $(VER)
@@ -46,8 +47,8 @@ objects = tzdata$(TZDATA_VER).tar.gz tzcode$(TZCODE_VER).tar.gz
 tzdata$(TZDATA_VER).tar.gz = $(DL_FROM)/tzdata$(TZDATA_VER).tar.gz
 tzcode$(TZCODE_VER).tar.gz = $(DL_FROM)/tzcode$(TZCODE_VER).tar.gz
 
-tzdata$(TZDATA_VER).tar.gz_BLAKE2 = f7d8fa0286f72e90058693dcdc39b8e9ddca198b157807b8d7d33969c07a2ee5a0391c6ebe8f3d86990de765216f563cf7ca75d8ea6f5c3b2950a16b973827de
-tzcode$(TZCODE_VER).tar.gz_BLAKE2 = b649847fcc59db2e43bc3f942e9ee4abb5968ac45114f6dcf362ec0ec23bd60117f976b539412cf062d8ba097a9d9a85f642ba46c5fbd96e2fb1a5e7b6f2ed53
+tzdata$(TZDATA_VER).tar.gz_BLAKE2 = 01fd07f9bfef107c8fb1ca677b0c25b3162220377610173de6d3591a6e714d25ab763cd2b3121dabeed3f6c95f27a4f402ac4ab59f3959b6f6418824c28fdfc5
+tzcode$(TZCODE_VER).tar.gz_BLAKE2 = 6e427e937a91ed814dc3c25bfb2b64703b2fdaa2129f8a39ecc302090eccd1939403d9eb39b41d7a9252249f970deb106ac5e13030e2c79b90a5f2fcc9acb419
 
 install : $(TARGET)
 
-- 
2.53.0



  parent reply	other threads:[~2026-04-07 15:11 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07 15:10 [PATCH] boost: Update to version 1_90_0 Adolf Belka
2026-04-07 15:10 ` [PATCH] core202: Ship boost Adolf Belka
2026-04-07 15:10 ` [PATCH] core202: Ship libpng Adolf Belka
2026-04-07 15:10 ` [PATCH] core202: Ship libsodium Adolf Belka
2026-04-07 15:10 ` [PATCH] core202: Ship liburcu Adolf Belka
2026-04-07 15:10 ` [PATCH] core202: Ship lmdb Adolf Belka
2026-04-07 15:10 ` [PATCH] core202: Ship lvm2 Adolf Belka
2026-04-07 15:10 ` [PATCH] core202: Ship man-pages Adolf Belka
2026-04-07 15:10 ` [PATCH] core202: Ship mdadm Adolf Belka
2026-04-07 15:10 ` [PATCH] core202: Ship ncat Adolf Belka
2026-04-07 15:10 ` [PATCH] core202: Ship pango Adolf Belka
2026-04-07 15:10 ` [PATCH] core202: Ship sqlite Adolf Belka
2026-04-07 15:10 ` [PATCH] core202: Ship tzdata Adolf Belka
2026-04-07 15:10 ` [PATCH] core202: Ship vim Adolf Belka
2026-04-07 15:10 ` [PATCH] core202: Ship xfsprogs Adolf Belka
2026-04-07 15:10 ` [PATCH] core202: Ship xz Adolf Belka
2026-04-07 15:10 ` [PATCH] libpng: Update to version 1.6.56 Adolf Belka
2026-04-07 15:10 ` [PATCH] libsodium: Update to version 1.0.21 Adolf Belka
2026-04-07 15:10 ` [PATCH] liburcu: Update to version 0.15.6 Adolf Belka
2026-04-07 15:10 ` [PATCH] lmdb: Update to version 0.9.35 Adolf Belka
2026-04-07 15:10 ` [PATCH] lvm2: Update to version 2.03.39 Adolf Belka
2026-04-07 15:10 ` [PATCH] man-pages: Update to version 6.17 Adolf Belka
2026-04-07 15:10 ` [PATCH] mdadm: Update to version 4.6 Adolf Belka
2026-04-07 15:10 ` [PATCH] ncat: Update to version 7.99 Adolf Belka
2026-04-07 15:10 ` [PATCH] nfs: Update to version 2.9.1 Adolf Belka
2026-04-07 15:10 ` [PATCH] nmap: Update to version 7.99 Adolf Belka
2026-04-07 15:11 ` [PATCH] pango: Update to version 1.57.1 Adolf Belka
2026-04-07 15:11 ` [PATCH] postfix: Update to version 3.11.1 Adolf Belka
2026-04-07 15:11 ` [PATCH] sqlite: Update to version 3510300 Adolf Belka
2026-04-07 15:11 ` [PATCH] strongswan: Update to version 6.0.5 Adolf Belka
2026-04-07 15:11 ` [PATCH] transmission: Update to version 4.1.1 Adolf Belka
2026-04-07 15:11 ` Adolf Belka [this message]
2026-04-07 15:11 ` [PATCH] vim: Update to version 9.2.0305 Adolf Belka
2026-04-07 15:11 ` [PATCH] xfsprogs: Update to version 6.19.0 Adolf Belka
2026-04-07 15:11 ` [PATCH] xz: Update to version 5.8.3 Adolf Belka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260407151108.3472751-32-adolf.belka@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox