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 2026e
Date: Wed, 30 Sep 2026 13:29:29 +0200	[thread overview]
Message-ID: <20260930112929.3446372-1-adolf.belka@ipfire.org> (raw)

- Update from version 2026d to 2026e
- No chnage in rootfile
- Changelog
2026e
  Briefly:
    Manitoba moves to permanent -05 on 2026-10-31.
  Changes to future timestamps
	    Manitoba’s 2026-03-08 spring forward was its last foreseeable clock
	     change, as it moved to permanent -05 thereafter.  Model this with
	     its traditional abbreviation EST.  Although the change to
	     permanent -05 legally takes place on 2026-10-31, temporarily model
	     the change to occur on 2026-11-01 at 02:00 for the same reason as
	     other recent temporary hacks.  (Caution: see “NOTE FOR 2026b
	    TEMPORARY HACK FOR CLDR AND CANADA” below.)
	      As the change affects both America/Winnipeg and its backward
	      compatibility link, the obsolescent setting TZ="Canada/Central"
	      will now use the abbreviation EST for affected timestamps,
	      akin to TZ="Canada/Pacific" behavior introduced in 2026b.
	      Another TZDB release may be needed soon if any of the portions of
	      northwestern Ontario historically aligned with America/Winnipeg do
	      not follow.  For now, given the short leadtime with Manitoba’s
	      announcement, assume that they will, to avoid creating new zones
	      that may not be needed if no divergence occurs.
    NOTE FOR 2026b TEMPORARY HACK FOR CLDR AND CANADA:
	    This temporary hack works around a Canadian timekeeping bug in
	     Unicode CLDR 48 and earlier.  Unfortunately it also causes zic
	     2023d through 2026a, in the default slim mode, to generate a
	     TZif file that does not conform to Internet RFC 9636 §3.3.
	     The buggy file in turn causes some TZif readers, including tzcode
	     itself, to ignore America/Vancouver’s 2026-11-01 02:00 transition
	     from PDT (tm_isdst=1) to MST (tm_isdst=0).  Although the buggy
	     file does not cause any known TZif reader to mishandle UT offsets,
	     caution is advised when using zic 2023d through 2026a to compile
	     data from more-recent tz releases.  To work around this problem
	     when using these older zic versions, use ‘zic -b fat’.
  Changes to past timestamps
	    In 1925 Ireland fell back on 09-20 not 10-04 (thanks to Stan Ulbrych).
  Changes to commentary
	    Discussion on timekeeping practices in northwestern Ontario has been
	     expanded in light of Manitoba’s recent announcement.  It is not yet
	     known whether or to what extent these areas may adapt their own
	     timekeeping practices in response.

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

diff --git a/lfs/tzdata b/lfs/tzdata
index 04856bca8..1dda8489b 100644
--- a/lfs/tzdata
+++ b/lfs/tzdata
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 2026d
+VER        = 2026e
 # https://data.iana.org/time-zones/releases/.tar.gx & .asc
 
 TZDATA_VER = $(VER)
@@ -47,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 = a9ed7437306e582e2b6791ca02de44c0bf7ec0e52d303532a972aaa2610820c1c16c3b959e5222398bc5101d2061a00b417d815bd5de730ad1f57b98471b901a
-tzcode$(TZCODE_VER).tar.gz_BLAKE2 = 7a042efe57b2e319ce96a38b7ec28335fed1713eeeed799cbc7d7164cbd596601718a5ec2847daa3ac5f5051f7957779455b637c6b49d45eae7eb7429c393c07
+tzdata$(TZDATA_VER).tar.gz_BLAKE2 = 0669a6189c1d9f4adbf7b2ed6778d1d48b7799db4e86d60d9ff275dcd635341f1d0325141e0b792c4472e38d7f9f60e81cbb0142a35a98a7b169351afbed9daf
+tzcode$(TZCODE_VER).tar.gz_BLAKE2 = 3265ce424251a83179fb5523b770f3c7fc5d6c5b7267fa4cf08e416d79f83117f8a581bde1d2ba57122852bbdaef08742bab478705ab135dfdf2ddc1b5743d9f
 
 install : $(TARGET)
 
-- 
2.55.0



                 reply	other threads:[~2026-09-30 11:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260930112929.3446372-1-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