From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4hvt9s1vL7z2xVj for ; Wed, 30 Sep 2026 11:29:37 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (secp384r1 raw public key) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "YR2" (not verified)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4hvt9n5yKjz2xN3 for ; Wed, 30 Sep 2026 11:29:33 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4hvt9m00ZZzCc; Wed, 30 Sep 2026 11:29:31 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1790767772; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=MZtZQcjFmMA7MhyxpjOADADGqHIPwkeAnqnUVgSFhmE=; b=bZ4LhFfEMxMWunvu+v2meaBgypaEeymlTb4u6XMGBVaXSlUEWgoN7dAVIZqqavP4v5B/wn GPgAuV3oxwHFnjDw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1790767772; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=MZtZQcjFmMA7MhyxpjOADADGqHIPwkeAnqnUVgSFhmE=; b=X+cjObzXyyB3NGsc8RBYzbrqZ0eH0jmILq6sCLaynM7byw2ekIN5lU//vWXv89M9BSVqub wPCy0uI2O9oTxz51eCdRzzdWvPrKF/NrW5j5psmQc9XCeRmSR6ayEjOcU3Hn1TbVbi6yks S2pyLQNcKisbySa3vTj6ESngB70Gol0Yyjg+YDwIv+HfmOj1t+FUw2UnRcqJe/GNgZB/kH BngDNoRG7elgcDGpb8yc7ryh4i4zJ+S7zNfZj6IrBEo31vWzoNuBrM5X2WTXy6MTcuwM1H 7shGPIroPEIb+mom/L/gtAXDcTihpv5h8kVu/bdSRUjYEU+dK7NzpzFSnT9Y2w== From: Adolf Belka To: development@lists.ipfire.org Cc: Adolf Belka Subject: [PATCH] tzdata: Update to version 2026e Date: Wed, 30 Sep 2026 13:29:29 +0200 Message-ID: <20260930112929.3446372-1-adolf.belka@ipfire.org> Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - 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 --- 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