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 2026b
Date: Fri, 24 Apr 2026 18:43:00 +0200	[thread overview]
Message-ID: <20260424164300.3505717-5-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20260424164300.3505717-1-adolf.belka@ipfire.org>

- Update from version 2026a to 2026b
- No change in rootfile
- Changelog
    2026b
  Briefly:
    British Columbia moved to permanent -07 on 2026-03-09.
    Some more overflow bugs have been fixed in zic.
  Changes to future timestamps
    British Columbia’s 2026-03-08 spring forward was its last
     foreseeable clock change, as it moved to permanent -07 thereafter.
     (Thanks to Arthur David Olson.)  Although the change to permanent
     -07 legally took place on 2026-03-09, temporarily model the change
     to occur on 2026-11-01 at 02:00 instead.  This works around a
     limitation in CLDR v48.2 (2026-03-17).  This temporary hack is
     planned to be removed after CLDR is fixed.
  Changes to code
    zic no longer mishandles a last transition to a new time type.
    zic no longer overflows a buffer when generating a TZ string like
     "PST-167:59:58PDT-167:59:59,M11.5.6/-167:59:59,M12.5.6/-167:59:59",
     which can occur with adversarial input.  (Thanks to Naveed Khan.)
    zic no longer generates a longer TZif file than necessary when
     an earlier time zone abbreviation is a suffix of a later one.
     As a nice side effect, zic no longer overflows a buffer when given
     a long series of abbreviations, each a suffix of the next.
     (Buffer overflow reported by Arthur Chan.)
    zic no longer overflows an int when processing input like ‘Zone
     Ouch 2147483648:00:00 - LMT’.  The int overflow can lead to buffer
     overflow in adversarial cases.  (Thanks to Naveed Khan.)
    zic now checks for signals more often.

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 50410a8ff..e57625765 100644
--- a/lfs/tzdata
+++ b/lfs/tzdata
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 2026a
+VER        = 2026b
 # 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 = 01fd07f9bfef107c8fb1ca677b0c25b3162220377610173de6d3591a6e714d25ab763cd2b3121dabeed3f6c95f27a4f402ac4ab59f3959b6f6418824c28fdfc5
-tzcode$(TZCODE_VER).tar.gz_BLAKE2 = 6e427e937a91ed814dc3c25bfb2b64703b2fdaa2129f8a39ecc302090eccd1939403d9eb39b41d7a9252249f970deb106ac5e13030e2c79b90a5f2fcc9acb419
+tzdata$(TZDATA_VER).tar.gz_BLAKE2 = 3134d88addaa6a53749a4c87aa5c1b9d4632478152c67a26e5d1cfcf97b4eaafac3b16a41e61840360d4bde5aa05701aeb1caaafcc8a006c7f4708cfa2ac686d
+tzcode$(TZCODE_VER).tar.gz_BLAKE2 = 89ac1ee3b79c596a4903b9c25a794b24fa8e6076e61fbd30c09c690bd002f3759c76afd303abb9d716efa08da216b64362ec06be0e2c60ee89fd6a5e7b397f17
 
 install : $(TARGET)
 
-- 
2.54.0



      parent reply	other threads:[~2026-04-24 16:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-24 16:42 [PATCH] core202: Ship openssh Adolf Belka
2026-04-24 16:42 ` [PATCH] core202: Ship openssl Adolf Belka
2026-04-24 16:42 ` [PATCH] openssh: Update to version 10.3p1 Adolf Belka
2026-04-24 16:42 ` [PATCH] openssl: Update to version 3.6.2 Adolf Belka
2026-04-24 16:43 ` Adolf Belka [this message]

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=20260424164300.3505717-5-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