tzdata: Update to version 2026d

Message ID 20260913171230.3920551-28-adolf.belka@ipfire.org
State New
Headers
Series tzdata: Update to version 2026d |

Commit Message

Adolf Belka 13 Sep 2026, 5:12 p.m. UTC
- Update from version 2026c to 2026d
- No change in rootfile
- Changelog
2026d
  Briefly:
    Canada’s Northwest Territories moved to permanent -06 on 2026-08-21.
     Obsolescent settings like TZ="EST5EDT" now conform better to POSIX.
     Fix security, performance and porting bugs in zic and localtime.
  Changes to future timestamps
    Canada’s Northwest Territories will not fall back on 2026-11-01
     and will stay on -06 year-round, matching Alberta’s recent change.
     Model this with its traditional abbreviation CST.  Although the
     change to permanent -06 legally took place on 2026-08-21,
     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.)
     This affects only America/Inuvik as the rest of the territory is
     covered by America/Edmonton, for which the equivalent change was
     released in 2026c.
    NOTE FOR 2026b TEMPORARY HACK FOR CLDR AND CANADA:
     This zic fix is needed for the temporary hack (mentioned above)
     that works around the Canadian timekeeping bug in Unicode CLDR.
     Without the fix, the temporary hack causes zic versions 2023d
     through 2026a, in their default mode that generates slim output,
     to generate a TZif file that violates 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
    Colombia’s 1992-05-02 spring forward was at 00:00, not 24:00.
    Iran’s 1979-05-26 spring forward was at 00:00, not 24:00.
     (Thanks to N.F. Hase.)
    The backward-compatibility names EST5EDT, CST6CDT, MST7MDT, and
     PST8PDT now conform better to POSIX.  For example, EST5EDT now
     always uses the abbreviation "EST" for standard time (now always 5
     hours behind UT) and "EDT" for daylight saving time, whereas it
     formerly had different UT offsets before standard time was
     introduced and sometimes used abbreviations like "LMT", "EWT" and
     "EPT", all contrary to POSIX.  Also, though not required by POSIX
     these names now use US federal rules rather than rules of places
     like New York, reverting to 2024a behavior.  This change affects
     only timestamps before 1966-10-30 at 01:00 standard time.
  Other data changes
    The temporary hacks used for North American timekeeping changes
     now work around a libstdc++ std::chrono bug in GCC 14.1-14.4,
     15.1-15.2, and 16.1; see GCC bug 124851.  This data change does
     not affect TZif files or timestamps.  The change does not work
     around the related but less serious GCC bugs 116110 and 124513.
     These GCC bugs are all fixed in GCC 16.2.
  Changes to code
    zic now rejects Link targets that would have invalid names, and
     more efficiently processes Expires, Leap and Rule lines with years
     far in the past or future.  (Thanks to Darren Carreras.)
    zic now ports to systems that report lack of link support via
     EINVAL, ENOSYS or EPERM errno values. (Thanks to Tom Lane.)
    When tzset and related functions encounter a TZif file that is too
     large for them, they now consistently fail instead of sometimes
     silently ignoring excess parts of the file.
    localtime-related functions no longer mishandle extreme timestamps
     when given TZif files holding some unlikely timezone histories.
     (Problem reported by David Sarkisyan.)
    localtime-related functions no longer check the values of TZif
     files’ standard/wall and UT/local indicators, which these
     functions have not used since 2026a’s removal of the old
     posixrules feature.
    tzcode has been ported to Haiku.
    localtime.c now works again by default on AIX and DragonFly BSD.
    zic now rejects ‘:’ and ‘\’ in Zone and Link names when running on
     Microsoft Windows.  (Problem reported by David Diaz.)
  Changes to documentation
    URLs for release tarballs in tz-link.html have been updated to
     reflect their new canonical URLs on data.iana.org.

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

Patch

diff --git a/lfs/tzdata b/lfs/tzdata
index 42b916af0..04856bca8 100644
--- a/lfs/tzdata
+++ b/lfs/tzdata
@@ -24,7 +24,7 @@ 
 
 include Config
 
-VER        = 2026c
+VER        = 2026d
 # 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 = 53a759b9081736b5daba8574b2f6a6852fcd0fbb85237d90e5c589f4126a445a9fbbf338383fc14cee09fa4bb38b546a8285adcbdd944d93eb7e1242cae8feda
-tzcode$(TZCODE_VER).tar.gz_BLAKE2 = 09939593ad33e894d7ad62f8a7e1ee09a4490143a4c744551f81e836eb1b63f96926d362e415d1e254d2fe2d52378017c190b027e1d99a00b94014a413e329dd
+tzdata$(TZDATA_VER).tar.gz_BLAKE2 = a9ed7437306e582e2b6791ca02de44c0bf7ec0e52d303532a972aaa2610820c1c16c3b959e5222398bc5101d2061a00b417d815bd5de730ad1f57b98471b901a
+tzcode$(TZCODE_VER).tar.gz_BLAKE2 = 7a042efe57b2e319ce96a38b7ec28335fed1713eeeed799cbc7d7164cbd596601718a5ec2847daa3ac5f5051f7957779455b637c6b49d45eae7eb7429c393c07
 
 install : $(TARGET)