- tz-announce - lists.iana.org

2026e release of tz code and data available
by Paul Eggert Sept. 30, 2026

Sept. 30, 2026

The 2026e release of the tz code and data is available. This release is prompted by Manitoba’s decision to stay on permanent UTC-05, which has a practical effect starting 2026-11-01 at 02:00. Like the similar changes for Alberta, British Columbia, and the Northwest Territories in the previous three tzdata releases, there will likely be problems downstream as CLDR’s latest release cannot handle it as specified. This release contains the following changes: 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. Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2026e.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2026e.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2026e.tar.lz The following convenience links are also available, although they may point to the previous release until the relevant caches are refreshed: https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz Links are also available via plain HTTP, and via FTP from ftp://ftp.iana.org/tz/releases with the same basenames as above. Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit 039ef27cc5f062a2055cb67435d6d71adbefd27d dated 2026-09-29 17:14:38 -0700 and tagged '2026e' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 623af2d5c611ce5d9f6d07ceeb09721db03ed90e8e74e027f96fc402eb948fc8a7e9aecac2611e41fb501bdc2592a78020375ad677d887beaacb2fd5da9b9815 tzcode2026e.tar.gz 5be2f875f73b75e5783c474bf7a6c768e433cc90283f8fc6a75e3d05bd92aec97936e8a55ccca5e880b5dacc18ba65932bab0e783e1ed5d2af4a3a4df95512be tzdata2026e.tar.gz 757be14e5e01eaeaa995ead6948456772d6b451ca0ce254de40a2167bf7c480ab03de61e19e62c2cfe8bb5ade7f5c938fd6ab70d4cc41ae6d867333076963996 tzdb-2026e.tar.lz Here are GPG digital signatures for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmq8VQsACgkQ7ZfpDmKq fjSKDg/+L/XjXhCZLKRzilGujnZtImSeEKbXvBPWCrB/FkjYx1SG9LTP3dgc1dbt qA3IO3hRWiI3rWXPs5kMzl9kQIZt8SOpHl15Sy+xOoAn2gbJk1EQkwf3gvPuoTce tGBvHdWLI7pV/81YUn339S3vsbLZPC896dHKEz2YCmmOqF2ExVykNMQKiwy6RhEv KiMfbkgAufYATwOXY2+F7s9dpmO5CihEYRhgPA9GDlaoLXL03yywg1Zq7zbH2l5N BKoCmVswEcQCF4qMY39MSj0hHAIr+C4BYsEWWg24mfJ2ECBGErDlEB14PQLmBiuO HTBgCOdrN8NaQWted8+Gru0K32liMTI3KzTNC0BvEmIK7/ChEO5cxwpmQzrgVgyI FIpdCfTJB2Q4VSdm2JWOpwr6fY6yEJbVt2VgbEEi3o8T6H9tW8/7EQDPJRgbVt0G Gieejx1LbJl90AaLFJ7ARICioyAKRgUDZYayaYcUsOZkSXbbmPONzPyaM84CxKO9 S1xWVW506dhDZ6ydlCq0Zy8+7VDmo4wtI4lXeqan+pVL8stgG3x9yZvGlvBkbfcf eUNWd9uFttEaHuP164pA3I3+hNpebAolIJfsNHBHB5DFZJ+AZ16s8BUdLZiQgcge mdtdT03Cn/HrgaEaiYnPTNtOFKfY43KxrXMGEqe8RPHhjey1LDw= =k+Db -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmq8VQsACgkQ7ZfpDmKq fjQSFw/9Ft+BbeEzD6Sfdxuab5WsA48lSxHPwroL01fJI7+qRTqbCXdnjXKbWglT iIvuTSD93Dtsl81cx9y+wDFe3XTYdlCUmTX+kP4wTNwQ6ypkWZmB2YWVACdmXeec g8S6ZkZXnhOE9qAJ/5DVleOHqBb8ozQavqtk7mve4e1vEXLTW9ul2Szn4dKmHoaU EYDo2eSsiEop6z5fhnA2qUYH2dCfKIahLv1yyXG4NmMUFyDVYH0YOPdREP9cxpWt cFoUAktuO2JaQwh2DrU5a+jpPJqasH8Puy2wmZnQNzHtFw/vCiXTBdT+erYjOnFB bOfgwFVMU/a89Zp44ctdVhkXDIRw8prZKpl2Fgc3e/KUPbRJwteuI9AVKQUKQhPN mVR9O8ABVwT8C2QI1sTo8R5zfmYgNaHNxDEEJm/guxmylBJ2jqsC0p7YtiFUfVWU 5N1Wg/nvsm80Jvi9s5748P+NKlJaBYJuVffSsqKmzIE+6G8uMXAfQeM8QKGa314l c3KQ6eWeVJLKmJp7yAnX/EneihQ8JhG8r98Z03+2MiT2uetQYZRhLKOPFWZRt9VJ v6qm3bQE7Phx/o9Mi5wueAd3yDIEPvMlgJmeOGno5QtbPJQoHmo68TLbwfC745Od qxqS8c5v5HLrY7dqafHpojrbL7/Q8dKi4TxP1exyO0FwKJxlJRg= =fybA -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmq8VQwACgkQ7ZfpDmKq fjRuBRAAiLyW7PTQiSKF2S503Yo1thkAwdENV8CG65Q5T2J1aedYxceeVZiyQFqU QyVHB4fKw+2nJQCf7fqmljiMdqT9WtBZipyGY+nmTqFeJnghYv5p/uywtCRQX6rs rSmb/mQDgh8V7ndDW5K/OiO3i8ux81xkry/zrlTGj5W37UhqDQVo5/cQjHodwqm2 /ZHtfS3tbHQ2O9gHMPeDXVrd1/gU/kA8LH2HU8JXLpkWJNcoiTi6x+8l9yl2FLFx htih6V9P09LQSGV/wdhrDrZB6DhXw71ixTGP3uYdOAHPHH91x3wwChO9LkIDRdeK CwoGfSkuhdMvFO8Ss4GMuBr1xtinZ17wkjQMWaVb41mrqFWwiPTOjXw6iZ4DQzhx CBziTsZqkErw9fSC287kpfPojzs4CSDlI+AePLqOsp3CflYLZ6A+YvqEhzz+eU+0 EHyRHSKUjChoE6RhjbbsKVNu9i/DjGrKltLl5Q33UsxDNKtx1oQUDW+rZZtKC7Zu APF0haFQVt3uaCe6se6KV48A2+BtC/CzY6PjfPTL7JSJFjScxd96TFQ/7w7J+uNu 95JhToWMmYykvX9pCXqrXhmdOBHpZpKoZjInQollcDWedpKhKZGX4CDn7MYfLf7+ UMUaFMJ+S2ahV/W16sIVFQ1jhxpizhjKcRGK+bdX7iE7gb8x/Ao= =03Tp -----END PGP SIGNATURE-----

1 0

2026d release of tz code and data available
by Paul Eggert Sept. 12, 2026

Sept. 12, 2026

To: Time zone announcements <tz-announce(a)iana.org> Subject: 2026d release of tz code and data available The 2026d release of the tz code and data is available. This release is prompted by the decision of the Northwest Territories to stay on permanent UTC-06, which has a practical effect starting 2026-11-01 at 02:00. Like the similar changes for Alberta and British Columbia in the previous two tzdata releases, there will likely be problems downstream as CLDR’s latest release cannot handle it as specified.[ This release contains the following changes: 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. Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2026d.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2026d.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2026d.tar.lz The following convenience links are also available, although they may point to the previous release until the relevant caches are refreshed: https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz Links are also available via plain HTTP, and via FTP from ftp://ftp.iana.org/tz/releases with the same basenames as above. Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit d633fe7ed3de8e00ce7cac991376a064a1373bb1 dated 2026-09-11 15:21:07 -0700 and tagged '2026d' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 42d4b37549a35893187851187cae93c811928f808c24ac0003bf0b782837d0934f2f7da7e93a0417273c7e0a66f79e9d512290ae4811cb73a7d02b62b3f0fed1 tzcode2026d.tar.gz 1a27de5af50bbc28a2f64c506ab3678b09d9e5ab6c118f39eb38bb823aa8f57069bf5e465848e71df8274c6b8bcd0fc736a88107e5792d816a1db5d867cbc219 tzdata2026d.tar.gz b2f4622ef0c2a33ee4a9282c8346dc2732e044617b3b7a1288bc065910653ed8109f01b1423b4b497373f9bc2b9fefb0a75a02c6b79e266ea2fe9767ec32ee89 tzdb-2026d.tar.lz Here are GPG digital signatures for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmqkf5gACgkQ7ZfpDmKq fjQXWBAAnIE3DbfQMdoICE5lQiElrwzKhUDkQBbT7bb5GCg6vh4pZjYI49CpcYe3 adPyGBedYRw/ZucfaEL76FM0xpJ2uooQu4s9CIpyvmAygNHgI3PRiG5iLC9Xw8aK /pT9zsYiJgTKkTfz/myfiZbsRerNjT48SNKveBRKhN3gmVjhu2egwGubzvGeiQKd hLE7nQEsmJbGCNSZt6GAW16UM95Opx4K6otc4DBx48cqcqqfpunWp7ltVe1Ka9VP TKo6LzeMS9+SS7TdRzjcjBDHcq/eG+ShS4pghSRYC1JkJ7AjaBJjqb/XGqJwCXPW +9WdvmbY0t6WOGcYjQs9/b8GNUjLx+s0HCv6I+a+rpXj6m1UCwwdQaZ2FOfuzXqN i9CvaPcn3jCq1CpxhEYwYBj5y5MalDcwOZUvDlQEqdA2WQhl8src09Armsiyj2hM pBqg1e8PzXzEusdwxee7pfCpLXv4GYb4d326wUYzuVR0QxPKxWX6/QWAsIQp62rn SuXmBkpV+GEeQzo5d08cLch/al03Xqv5ooAQaRi+CY1jmAMf+i0s1yt05YcgfwZ3 tTVFTIvSXbG6/LpfRod5XljBXqrHL2TZZbcW/bl4Fuupb9OY0z+Orcpih5Fc84Ac 6MVKLFRnz9fm5Vnz6ohXnPqzO9PTFCX5x1rui+dDYIOXJDCXyuA= =x5qK -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmqkf5kACgkQ7ZfpDmKq fjQwXw/+MFPvjwVhxciWFlkcXA56HsWXDCx+qhtYPKDGwDeU7mCTR/kkHIDplepO gyJsZyQfQME+CFqr094rhg2PRxW3xQ5cyM0bl+bVNfc0PYIOjUGLpzkT1go6i2Re cUexnt8DCaztFYYQ9VQbpikg14Zs/noFgqOe61xD5ZlWMK7U0ojKVj/e+R4pDqLW nVMSAsJlLqGczrlhFBXoTRn9fytl5THWLki7DxRiKNcnr12kKqOE8PHTkB12O5hK D1RQEEb0lYMkHkqK0n9y4QVQWwHGyMIbafFUF33A4W7lZFA4JiD4k5e587LtoSNC EcA3Jc65HdRFecfEQQQQM9CjMa6wVqQqW+KtSf2EkAsk37XAbeelw7KlVN4uaXXb 60uqUIcc4seALKR3M3vqUgoV4Fx7L48PUkrXaJfyJu1TxqqaGg84rEd9Vmp5q3Y+ fNzP2iug1sHF8oqqml9wLLDWT8ZyOU/9UTVqKfSvqO46Ny/6M5wkO1gV1wLjwVh/ tdVZvHpQpv2FGjfO38NkM1j3W699gsKwvdD0SB4nP6Lm0bRmdLvcKbGszSKJBmys YvL1epMigtPkLNy77ZKHJQ+X081XHouhcLxJ6NcyxHQH4aMdDIKcJLi/lTdMFI1m TgBrzCxjD3UU9ncYCt0IMHNm5oAyQFggil26UAU0XY/U7cy6TZQ= =Jrqs -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmqkf5oACgkQ7ZfpDmKq fjTUxw//SMs8fyX0yaPYZljYLjEBMpnejY2CiWZCYvZWMCdt195l4sppaHZuaUXW JnkkS2EK4EGCqBsGHLpLqPr9XujkpD8RbMJK9li1YUNRFmHiVdxQUlax2Ezu1rra UExMBIlzGmGzf5CWZahYYWpgFkEaaKrJn/oYH0LvzltaFnS8BV/M0w02P/mxlmUr qdbnRkKN6sPC3OZF9ooCs5iH0THdU79F+n8KE5OQvHE73geiODwHd9aTRtFzKLdk M+ITQrksZEKA4H1JpEsne5uSbmj8kugxmg8YfAeYLg0ETPLBh/6YZIUanoX+SQr7 ujwO3nS1zgQah42q5GXMwokF67W2XUb4u6mDunGD/1OcQHbissVezQSf0hzxxRYB mlJ4L9lMlhM+p3ylzZ+frfiybiB6hHq8si5MoArZo5C5CmzrgCXzxSulFRscsjB+ PmaD8vBpyi6+4XWsVca7g8T0Cc11cHN3iwC5aiNZTYLVyHbWpdn6tqsk4esxDOYm 7brSeKW90qG3YpE22FfBveIqBclg5futihXK4FPFFs76oFhAMCiTd4uFrNEO8ifn G/i1avlbX4LBJRMeU+TKMIrWULdMepLr+wY4wBFDwmeci1wguM9o8RscET4LNJCs f4nGnsWU4iRTF3uX4A50TIJc5cdTH3tWYpA57LAS/3623Y3Rvu4= =3SEZ -----END PGP SIGNATURE-----

1 0

2026c release of tz code and data available
by Paul Eggert July 8, 2026

July 8, 2026

The 2026c release of the tz code and data is available. This release’s main urgency is Alberta’s decision to stop changing its clocks and stay on permanent UTC-06, which has a practical effect starting 2026-11-01 at 02:00. Like the similar British Columbia changes in the previous release, there will likely be problems downstream as CLDR’s latest release cannot handle it as specified. So we’re releasing now so that downstream has some time to test and adjust. Also, Morocco is moving to permanent UTC on 2026-09-20. This will likely cause fewer problems among downstream CLDR users. Although quite possibly we’ll soon need another TZDB release to accommodate similar changes planned for Northwest Territories, these changes have not been formalized yet. This release contains the following changes: Briefly: Alberta moved to permanent -06 on 2026-06-18. Morocco moves to permanent +00 on 2026-09-20. More integer overflow bugs have been fixed in zic. Changes to future timestamps Alberta’s 2026-03-08 spring forward was its last foreseeable clock change, as it moved to permanent -06 thereafter. (Thanks to Roozbeh Pournader and others.) Model this with its traditional abbreviation CST. Although the change to permanent -06 legally took place on 2026-06-18, temporarily model the change to occur on 2026-11-01 at 02:00 instead, for the same reason we introduced a similarly temporary hack for British Columbia in 2026b. Although another TZDB release will likely be needed soon because Northwest Territories will likely follow Alberta, the legal formalities have not yet taken place. Morocco plans to move back to permanent UTC, without daylight saving time transitions, on 2026-09-20 at 02:00. This also affects Western Sahara. Changes to code zic no longer overflows integers when processing outlandish input like ‘Zone Ouch 0 - LMT 9223372036854775807’, ‘Zone Ouch 0 2562047788015215 LMT’, ‘Zone Ouch -2562047788015215:30:08 - LMT’, and ‘Zone Ouch -2562047788015215:30:08 - %%z’. This avoids undefined behavior in C. (Problems reported by Naveed Khan.) On platforms that have EFTYPE, tzalloc now fails with errno set to EFTYPE, not EINVAL, if it detects that the TZif file has an invalid format or is not a regular file. Formerly it did this only on NetBSD, and only when the file was not a regular file. Unprivileged programs no longer require TZif files to be regular files or reject relative names containing ".." components. This reverts to the more-permissive 2025b behavior, as the stricter behavior did not catch on in FreeBSD. zic now reports any failure to remove a temporary file when cleaning up after a previous failure. (Problem reported by Tom Lane.) Changes to commentary Northwest Territories is expected to move to permanent -06 prior to 2026-11-01 02:00, when clocks would otherwise fall back. (Thanks to Tim Parenti and James Bellaire.) Model this with its traditional abbreviation CST. Unfortunately the change is not yet official, so it is currently present only as comments that can be uncommented as needed. Changes to build procedure The undocumented ‘typecheck’ Makefile check rule has been removed. It stopped working in 2025a and evidently nobody noticed. The rule was superseded by ‘check_time_t_alternatives’ in 2013d. Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2026c.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2026c.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2026c.tar.lz The following convenience links are also available, although they may point to the previous release until the relevant caches are refreshed: https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz Links are also available via plain HTTP, and via FTP from ftp://ftp.iana.org/tz/releases with the same basenames as above. Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit 71f28b9ab3b67c0f9466803f6151812d4fc8e357 dated 2026-07-08 10:23:58 -0700 and tagged '2026c' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: ad1aadf26b9aaca487a4f780d7a8ebf1d7383472ce587b06cb63852d4eb030dbd190b537e393e75d59530318581e9d3f492ff5f97bbac78f548d0755c4f7257f tzcode2026c.tar.gz e0b4b7044b66fbc27bc21d13d18063abcdf78ab58d5ba5fd64bd1a88d86e9d495f45add4d8e65bb6c40249f9c94ca29b72c8ebba8d0e4c468f2965ac77932ef0 tzdata2026c.tar.gz 3e5aec7d93522efc875fc8af553f78029677aaa9be8db396c862d687bdedb930379ba6246b33a15c5fb3a76d24e937dac4f4f66d6f9edf69a668bb21e9eeada7 tzdb-2026c.tar.lz Here are GPG digital signatures for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmpOiy0ACgkQ7ZfpDmKq fjRS/hAApD5lVCI/pMXFa6G1WT/Lx3Fydw0Frzo/uCeRtopN+HwLt7e5mwsWQBPe ju7nUs6Zg434ZlY7Rt/xKDPqFZnWmRdNqselkNsUpWi7ajm3VWm6TwJU7Gltkjbo 34DVY7Mn2Pmvma9bsPj1LJCqi+lsILVTobGZhGxh6NcgZ+CUFnVJKTWenDFuSzGA QltBeA74BH0zxIhCnqRjwaUtF1IS9WaX52I58k7llPn05AkGH8po+mkaz6jmqF+N BoL8lgTbNqkDzOaiVY0u2fjx6SoXW3tHPywpTGJeyfgD4KbYQOustw8zMXEANR6I W4M1p1j1aNo8Ss2ZXsNDDP9ZSAD3jRmNV18V4vB/cADff6K/Y/Phq8mHTiKjjS4W 4Fy54avRkk3HEgboytA6R7vwD1naB6L1FE4SM3TbIXO22BeHs4qhBjSRB3Wfk+1u AuGQsCNORi8GXYRSLPUm4ekss9WTU46JXqwa7yHPQH6sKRiHyFci4V1qk0Hhlh2Z 2DCURjXhI/9L+blozsZRZg3bxDN32iFEZAdE+iMmW0VPP39VrlL1gH/GisORzKL0 XCtIducsD7ZvV/cvCADUBwy3zgatXh0VaP2ozWHnnt/9hMVT6it6/2GMY0vY/D61 TUw2Rfa2P3y7IpRfGcT24kFjKv8rxx4A8mM9HndW/fYkUN2O3W4= =kK0H -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmpOiy0ACgkQ7ZfpDmKq fjR6yA/9H1+9KOGi6LIatyM5HSQb6UrOQ5X+Zs1SrBZk95yXBcgYRU6Ycfy3gGM8 +TWBKmMDiN3F1kRBeNgu4h/BAnXkpND50qyyLXKl5ztYdbRaZXZCMizPB7px7+CG YQuOErpS//MEEmtzKNRQBdgOAHv+eAMFIn6keLl8RbIeS1sQ2gewto2BeIDyYSx/ IuDNikI4/6ogyJYaxEKQgmpV/WcPLr5m+GCvW2zzpa7n5RHwR+UyksTGwD1vbQsi +DglIW3IjrdTM5/zuXsjmCxZX2MwxL7vZ62IDiEIlZefpz+7PdROU6fFwqZLryJB bHMTJpD+tjpxIv1j/xKSXA1f6KIOALVpA5eIaPc/S4ZGc4ZAHqghwzsE62fTv/3R 5M20csuAeP5nhEeLpa1UH7+4qLg9HAosXVYfbALeJunLYSUCiBmN2/XmA4W4Q3OD btS8fvt68Lax6srHkcHWFv39doXZNWkPTPFbsWJzqWVW0vhIh1YWJWCtobZ93wGM huKVTG49JGvB8qZQAnYaZdMrIYmNI/x9YYwV9rsvcpTANTRKAHEMoz4jX7fxGjrS xjqmr2RpoDpnd1xvyXIirnn4WkQeO2OF2xhABsAvMstfZf+PAhXl7flucLH2oTNy /8ZIzbItjoFWrbXqtEwE7goMq5XcP4BGOmr+nj2EukJF7CqWkj0= =r0JP -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmpOiy4ACgkQ7ZfpDmKq fjS51g//XdOjk0dzan2ashSNf6NiJ90VuBhCJAeCPBqr3BCVOD94K1riazP1ZbnN q2ex9llB63ZXuZ52W0Q5NigP1eQ+SOzYFN1WD8bQc4uUDfhF8vCO2bAF7bFyzWPd PD+geLWT23lkDtMGFDNePHYgiaOnBvqvadRryUbiPuXTJnEb0VCFU6catuAp+bG8 HADbnFAYQosiR+O2WVvhDmVdDtbJqaPFZFILSK4J+uxD6Kf8sS0/twEm5+hmJiPE Hy7yI65yKGKDcCCp0OFu/+412ZAOgExjVdC58/IGHYit8pAzI35mMm2xfzicShCk Sj1cm8mKLDC8w6J9huqNMK+p8NW4RrjMoeJaa11vgy3ARYkqVnfNZI+YPxQO5LKB yrgw8NF5ZafJYSYR+ZmjiZWTGe/1tMoC6GRmzwfIYmaLFlAIw4fTAe4ySqRIVgKo J5u28wneVxjCbueIE1qgWWvCIvz8xVB6ytx90SPigp6FumKTJiZm2/vF/Hem/5Hk gwKFSxGRBwBIVh5uaWWJEft2nSvpG5lONo1rZ2ygPTfbczjZMDZpoxEmWIeZjQ+r LrzNaDpzxFecfLvlUMrIOr4iwH14cDwkdGtCIJ5N/7uBwLfg+7sYts4pmAVdBZxd sCbAuEN/GtkNPV4cSYnDyF0FbM4zPGbztlOxxiOQG1RtJ51rbjI= =VYnI -----END PGP SIGNATURE-----

1 0

2026b release of tz code and data available
by Paul Eggert April 23, 2026

April 23, 2026

The 2026b release of the tz code and data is available. As Tim mentioned yesterday[1], this release’s main impetus is British Columbia’s decision to stop changing its clocks and stay on permanent UTC-07, which affects BC’s UTC offsets starting 2026-11-01 at 02:00. Since this change will likely cause problems downstream as CLDR’s latest release cannot handle it, we’re pushing out this release now so that downstream has some time to test and reprogram. Quite possibly we’ll need another release soon to accommodate proposed changes in Alberta and Northwest Territories. [1]: https://lists.iana.org/hyperkitty/list/tz@iana.org/thread/LZIJFAY2K4OXXCAGF… There is an embarrassing typo in the 2026b release: its NEWS file's third line has the wrong release number. I applied the following patch to the development version on GitHub and this patch should appear in the 2026c release. diff --git a/NEWS b/NEWS index a0042701..ea52e67e 100644 --- a/NEWS +++ b/NEWS @@ -3 +3 @@ News for the tz database -Release 2026a - 2026-04-22 23:06:43 -0700 +Release 2026b - 2026-04-22 23:06:43 -0700 The 2026b release contains the following changes: 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. Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2026b.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2026b.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2026b.tar.lz The following convenience links are also available, although they may point to the previous release until the relevant caches are refreshed: https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz Links are also available via plain HTTP, and via FTP from ftp://ftp.iana.org/tz/releases with the same basenames as above. Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit 48c25a1ba86cb602990c0573aba7795417931bb4 dated 2026-04-22 23:06:43 -0700 and tagged '2026b' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 55b44d52a83c9db151be32c3d78376ea7f9d4311ef15ed6fe34b855b08fc546531e51309d178d9c175a6d5d7d0b058440e45a55d200ca8925e3798dac9bc739f tzcode2026b.tar.gz a44882258c0a7fbe587e8b73d6bb3cd5be7d4788976ea742adbbf176eb3b33e5bd7d1714b2fffe2972b1a42e7335eac39ed0bd63e819bb421550f8cae1df4f2f tzdata2026b.tar.gz 5ec7f74f14cd2c70a0730e3690e82bd0ba889ac26c96397c16aa08005473c2c86feb47958b52e0301810c8eb908e6d8faf998ffae75b2337a912cc9e52c0f9e9 tzdb-2026b.tar.lz Here are GPG digital signatures for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmnpt34ACgkQ7ZfpDmKq fjSZew//brt18HiMD/tgxJ1CdjvvzDIZ4P0xWsVuxG4MjkC4821zYCfhDYLZ9Zdb /8wCi63uecmK2JsGjxzz+raX4ppHhZpg31a70KlyU9MarISVB2ldPqYDn+Xc98lR XIKj1ahtzyJoNu/67ZbCT7Ih/Wp8hwdlEFivjq00lnt+M2XCeINq9Cy3guisx3/8 dCziZEqoJFXDsdWmCvKZ93U/o7Xq8x7d9nfRjeBlX8VZMXuSnY3WkhLBRl+2Zgml ECeohhLMBuR6dFNOW6qwlsZGXfDb/Nq1NPsxIKqJ5Lv1K8Sj0h4icsGDMRrLvlZM qfNpsjWZQcH9JErR5hfB/Y6INRsKomRamul9LdlEAauMwO287eR8r5LrADMiAvPR jBVqmceAmgS+34BpRmMUfLwQJmEELbK8xzcdW8e41jrQQ8SuyqXQeYBjgjm3v7gc sA1HyWwDRn6276DQATonELOzREctHLIp2jfRGLAwngAl2CzqkhLZgBEHvdZbqW/s RbZLOk0u/y3Trd+dyFcLq/gxNSZQYQqpDmRiYNkb0vl02lu3lbZ1o3dmdF/AZ70U evj6z5iXztdKCQb9ZkecjNXncPDQNPoO1bJqm1QNYvUToMDNnJdu12qva+skNUyt HE54zxjcKv78bhm2ufXcqt4Ju/onyACTkSDQeCEzIzdBu9abVgw= =7394 -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmnpt34ACgkQ7ZfpDmKq fjTFTxAAisuje9O4OTkSUUQ4nHuZOHQW/1FNGXmIb/bGnAGAwOrGqiLuyQ0kJYxk Gdp4cTXEu5+NyQXeBPFtjBNbZO2cMC80rvl9/h3qUlbYG+ydhY0bjDglV3BEP/U/ OrP4pQsNjHeSl+p+3VSq7fAtOGcCRkBQrbEy5yXN5HzYJyCH4GAE1HZNNYKbCzAm hIxspmu6zjeN4xeLsXrB7DfiP7BJydrxk1LShU4zwmwJdmkH8dCGnDW4Kipz+tWF 2W8P4braXTAWCswLhOC8xYZLJKxf1nWS3dyo3i1IfnRciGD0O9dyLsJmlHxS4/34 Ometm9XahPHPiWvjBoqubKEfp6B+AlmmP9D1jM0BY7seuz2oxFUE7YW5+4cO4VhJ soWTDCKjyzo+wgflw3brv7j5AFP7tA7To6fbQ0W0oAmSRFQ10MA3JB0GSgn45SST 49C9jQ7U0XcroeIuoWs/1MbAz+qgCLk9QdijxNWsvk5S5h88FKLckVkEUUNgUSL/ F3z4h2Af6KpWq/n3wL97gwdis8cwxWScL3ZpfikiMJbEGuaIHabiw7C+r/dQssW0 7SbG01yZWgn3HtJBfELs1cmqWCUN4F+Y28um0Y4VYHTpSnNuVHBJ1wtfqCSatWYC wQa+n7KtBEGpY7BbSDZ/oGuqfDzpgR41F1tX7ZRa5y24zWHRQLQ= =eO2u -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmnpt38ACgkQ7ZfpDmKq fjTopg//ViAbiWmRZnu7F5owFRPySQWCSM1RJfBWOTL/UJjSArP2JbkOudcgeXZo Wj6fk1soY8w3o6CJACq12HhUAjQq6/mCupTyDSgOETMn2x/ZknuE407MOMc0t51t iYnfICJNYs1u1uRC/b7PEALYT7lt3Ab6QGe5iO2kVrFqJoB1AxRDIQlfPAHiRILY Abbt9avcL+k76idhSC782BmAFqtogPeHBVYQzBOgw/LfWGQ8ckkk66f4X8E6QMzA CkDSt/bAWIM/iVKw6ag4VBvIbzY2sR1EieN2GlHj5Dx6xMBlQdDpETgTIfNYG7si Ndai7vbMh+Gff5JfYiKq94WJ2uAP4jI3phN2NXpcYwc0OmEEMlYc/lcIlje3Bb3o Y+yop6RoVQpN6zbzLnuCMiDmy1SB2yhWpYQm/bqR1Qsb8vBfWBD3fvdscWXabDl8 m3ii38melVIdjSR18Qf3j9MOXefHo3xu0t00/ppPCwnuKKbhSItvTI9vg8BxqWL8 7iZYhNBkoJTIpgmTaHAggNUKNoa3mNYTuwJr7o/i4Bhki2ggzR5dKiKE9PAXSLaG 1tvCoWVVA3gGklkxFYnUncghC/YbEBDYWlaXbfgOC/+fhix7HnRCNcwckxlww86m gZCa2DcTBWiVQ6PP/6LzgHgNn7mhriVs0cGGVOlTL/h/zjm5CDw= =1+mL -----END PGP SIGNATURE-----

1 0

2026a release of tz code and data available
by Paul Eggert March 2, 2026

March 2, 2026

The 2026a release of the tz code and data is available. This release corrects the time for Moldova's upcoming clock transition on March 29, as well as on other dates. It also has significant changes to code and to the build procedure. This release contains the following changes: 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. Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2026a.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2026a.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2026a.tar.lz The following convenience links are also available, although they may point to the previous release until the relevant caches are refreshed: https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz Links are also available via plain HTTP, and via FTP from ftp://ftp.iana.org/tz/releases with the same basenames as above. Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit dd6be6d1558163517ec55c652efac70842c3b4cc dated 2026-03-01 22:59:49 -0800 and tagged '2026a' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA3-512 checksums for the release files, generated by the GNU coreutils 9.8+ command 'cksum -a sha3 -l 512'. SHA3-512 (tzcode2026a.tar.gz) = 7106762916c6d21aa71fc5b43924582b603e231c90f19fb40ecd81db96208f8a4d6ff9664508c7298c521ab8fed97d4100665f84b2ba17caed04af129e40c5c2 SHA3-512 (tzdata2026a.tar.gz) = 898b090b74d927495a412f382636e4eb2f697e3e357e5a1d35e01cf95f6cdc3bd52533a269ae247b521c6ec1112cbc2df0bb5466accf376e2e7b78a3adde26bd SHA3-512 (tzdb-2026a.tar.lz) = 5aefc96aa15113da1c30fbba7564636e106e3c0e33f475d48f32c5d3417e945fada548176e56c474a85bf02681e101c7b4dd727eb0053d1d39a81c9a13afe37b Here are the SHA-512 checksums for the release files: 69a2ad3334ab1491ba349fcd5d3066a26b38ccb59031fec70ca19379cb0514fe2757af7bee31e796913c0cfc322134e2ba16f93ba07fa45cd4a415b9122b2f27 tzcode2026a.tar.gz 407e8e93aaa054a22a4a7d6d8cf480a20630073bf1a00956df16b10318f239a12015de38fad3072249193e314d6fddbff4e74afa40a88f7bf5c9eecc7659ea15 tzdata2026a.tar.gz 1824fc2e198a449ebaa41e6c679a494c486b848f13fe8f18f948fde0533e99f5f01e7e7298e257c565838d24ec743e824f402887abdf525d1ce578a714c71414 tzdb-2026a.tar.lz Here are GPG digital signatures for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmmlNgMACgkQ7ZfpDmKq fjS64g//TxOxFmBXtJRx4LM8QIL315hvWwVpVAmAk+oFzqjluosfb3xbszBw3fWw PzcOyQ8PDXV42dq29jO8JjVJkCrvLiBjXWTTV6yDRqp3TEBh5uM4cUormnfcTLkT bmgVLLmqiNZgZpEHrsQQKaf8Ia/23F2topG0USSzqguLgLBVLcdut8Djfqb5qpqV xurq88ciC+ZvLENJsBXyfJzN2neuCOelbXgPDz+LJZrv3mJqFrm7EzxHngE8xZ+j Ny0V6WFaZJisWEif4oGeTPtxQS+LT/2bDBKtNpcFQhvquS6dU0nHHVAvNAIZaGNf HeQ/LgxFDQjnIisoqKA61qNmZZ1F5rDuYtL/j53nhjJpLkaDAoEU+xfKtYybJzir mH7Dj8WwUcLwH7lT/U4KDZmiUiT49Vk/u/7+pI1Vx7OogJ4Vs9WTtCt8avNGkwFF qez91hNIb6iZzVbnSKz+TWlfnBgltFQU02ozTZNW6K3TawLuwgyMoAGX0kaK8Lxy 8KKEo53phmmFnZ9vQKEJkJdaaIuisK1qJH1K6cj2GX44bhpDfT/kq4AQQbR7HDWR ZSTB5oG4TvqfGd3bKrDzpGOOLJ2AoiBaGi+rcA8n4WWvdGxodIJ6RU1cDI+RHPfv 8caWfWcEtAPCciArx2pa10gupda67DF1pwxAYLEbr+dmg2S8jQI= =/yto -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmmlNgMACgkQ7ZfpDmKq fjR04A//YmSFvKQi/w8hfB5fAf4VSV+5HBIeuTRJPn9BuRAUvZVYl78ApYGzSqPh sG3H/IPprHICVxMJcPBvEI7+tXVPozCOnwUx7jz2nAvl7awxj5n2z1zs+jjZ+/pU kiQ4x4uZDJTw5wsymy9nPasoQba5kmSItjB7fDXe2wwjPOh3osOzSfC0KDnPvTxl jPxBTd+CXDmz5fiI7RPSi1uJWJFXEtE+NpaltQpA8J1M7QSv2O+7x3eLfNoa1Eh9 GQ5JjtvMixdQGxFzMeID/Y2Rjj3vKFpB0+blf1zu5aBchemmvW/DFpOBhdm+lRf0 Me1TVlmlBI3oj4lrNhGIz3f7zf+IrPVfAAQ/hMMcyYc/FwYuuV9SSF0Aj2pWR0Mi wvASEXb23bWu2t1aeu7by7XSnL033o1P5DqWDueVSilTdeVSOS0EtyyFMC6THmj4 PcQh7/O60zbPhsUXan85rOC1CNv9lZJlEzZShy3B3tAccGr4IKrPRT/jIhVwVbu9 rS25dLR9S/bcrYTpn4aaWMPQ9tuYJ/83i1euAgs7NjKao0lziPTOPaBvqW6fdg1v /4dHluvwMufDLa23WVy2iPueTPD8NDH228xwrtGm/Spyu3XCX7YZJdCJVcNF0E9m W4z5R07LGBZYKscd9T8otPJyzTLcunLmnaf/Mbsrj4FmB+dNof8= =SR0V -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmmlNgQACgkQ7ZfpDmKq fjRfhg//WKsUlkhd9treq8Q3YMju7fezVZhvinFib7mmC3kn3HM5Xo2AKakjtwYn d0ZDuA886qFp3Llkn3pwnEh8vugE0A86qRwk3D3RoL/QfpbKkrVyAWONEWCHMKF1 MswUEO01Lcxd+CmjFWsH+dEhJ8HHLlPgyYgWCy6X3zvTyCLK5navq93QTmIKBguy tXAtWClft7wEv4Sg6xI0MtcAMamt5aBP9oC284XJbjfHz169QcK5VaCJPG82kuDs ABorgc6KVJN88SzPWsajpEQQE17hsH99y+Jh4UR4Lx4s06+52zOl814t0Aru28B2 K8u0PF5mO3druoHN8ielp9gdqIMk5JbOobhezGmnNPQT2ZIazTBa22/zVknkqoLq 6NQnpPekc2sjuVljRYCRkDwWXaUYfl8gR7e59Ew45IfFBpRCfkpEFK4A97KGfGVM gSCdW/N+9lCG2p1MrrRETykyGCX181rtnw8RXO+ADxmz8ddQ5WRrmGIkBYi7iocY 2iULltrLOAzCnUGsN0x/7xk8fLf7MRX+cExUJG992foiPQ/6N/06gp6SNeJyuKgG hI5TO9RIsR8JzjfUpI0Nbr9ZwkQuLFfkvvXSZeYwVU4rFNEHaQqz4dVvcfTAwi1T 9AK8S/7FjRoh/aqbUe9rVsUAOUcoOAkgCd2bUkcYLQ8FXJqJPYA= =t0qu -----END PGP SIGNATURE-----

1 0

2025c release of tz code and data available
by Paul Eggert Dec. 11, 2025

Dec. 11, 2025

The 2025c release of the tz code and data is available. This release mostly changes code and commentary. The only changed data are leap second table expiration and pre-1976 time in Baja California. This release contains the following changes: Briefly: Several code changes for compatibility with FreeBSD. Changes to past timestamps Baja California agreed with California’s DST rules in 1953 and in 1961 through 1975, instead of observing standard time all year. (Thanks to Alois Treindl.) Changes to build procedure Files in distributed tarballs now have correct commit times. Formerly, the committer’s time zone was incorrectly ignored. Distribution products (*.asc, *.gz, and *.lz) now have reproducible timestamps. Formerly, only the contents of the compressed tarballs had reproducible timestamps. By default, distributed formatted man pages (*.txt) now use UTF-8 and are left-adjusted more consistently. A new Makefile macro MANFLAGS can override these defaults. (Thanks to G. Branden Robinson for inspiring these changes.) Changes to code An unset TZ is no longer invalid when /etc/localtime is missing, and is abbreviated "UTC" not "-00". This reverts to 2024b behavior. (Problem and patch reported by Dag-Erling Smørgrav.) New function offtime_r, short for fixed-offset localtime_rz. It is defined if STD_INSPIRED is defined. (Patch from Dag-Erling Smørgrav.) tzset etc. are now more cautious about questionable TZ settings. Privileged programs now reject TZ settings that start with '/', unless they are TZDEFAULT (default "/etc/localtime") or start with TZDIR then '/' (default "/usr/share/zoneinfo/"). Unprivileged programs now require files to be regular files and reject relative names containing ".." directory components; formerly, only privileged programs did those two things. These changes were inspired by similar behavior in FreeBSD. On NetBSD, unprivileged programs now use O_REGULAR to check whether a TZ setting starting with '/' names a regular file, avoiding a minor security race still present elsewhere. TZ strings taken from tzalloc arguments are now treated with no less caution than TZ strings taken from the environment, as the old undocumented behavior would have been hard to explain. tzset etc. no longer use the ‘access’ system call to check access; instead they now use the system calls issetugid, getauxval, getresuid/getresgid, and geteuid/getegid/getuid/getgid (whichever first works) to test whether a program is privileged. Compile with -DHAVE_SYS_AUXV_H=[01] to enable or disable <sys/auxv.h> which (if it defines AT_SECURE) enables getauxval, and compile with -DHAVE_ISSETUGID=[01], -DHAVE_GETRESUID=[01], and -DHAVE_GETEUID=[01] to enable or disable the other calls’ use. The new CFLAGS option -DTZ_CHANGE_INTERVAL=N makes tzset etc. check for TZif file changes if the in-memory data are N seconds old or more, and are derived from the TZ environment variable. This is intended for platforms that want tzset etc. to reflect changes to whatever file TZ selects (including changes to /etc/localtime if TZ is unset). If N is negative (the default) these checks are omitted; this is the traditional behavior. The new CFLAGS options -DHAVE_STRUCT_STAT_ST_CTIM=0 and -DHAVE_STRUCT_TIMESPEC=0 port to non-POSIX.1-2008 platforms that lack st_ctim and struct timespec, respectively. tzset etc. now treat ' ' like '_' in time zone abbreviations, just as they treat other invalid bytes. This continues the transition begun in release 96k, which removed spaces in tzdata because the spaces break time string parsers. The new CFLAGS option -DTHREAD_PREFER_SINGLE causes tzcode in single-threaded processes to avoid locks, as FreeBSD does. This can save time in single-threaded apps. The threadedness testing costs CPU time and energy in multi-threaded apps. New options -DHAVE___ISTHREADED and -DHAVE_SYS_SINGLE_THREADED_H can help configure how to test for single-threadedness. The new CFLAGS option -DTHREAD_RWLOCK uses read-write locks, as macOS does, instead of mutexes. This saves real time when TZ is rarely changing and many threads call tzcode simultaneously. It costs more CPU time and energy. The new CFLAGS option -TTHREAD_TM_MULTI causes localtime to return a pointer to thread-specific memory, as FreeBSD does, instead of to the same memory in all threads. This supports unportable programs that incorrectly use localtime instead of localtime_r. This option affects gmtime and offtime similarly to localtime. Because the corresponding storage is freed on thread exit, this option is incompatible with POSIX.1-2024 and earlier. It also costs CPU time and memory. tzfree now preserves errno, consistently with POSIX.1-2024 ‘free’. tzcode now uses mempcpy if available, guessing its availability. Compile with -DHAVE_MEMPCPY=1 or 0 to override the guess. tzcode now uses strnlen to improve asymptotic performance a bit. Compile with -DHAVE_STRNLEN=0 if your platform lacks it. tzcode now hand-declares unistd.h-provided symbols like getopt if HAVE_UNISTD_H=0, not if HAVE_POSIX_DECLS=0. tzset etc. now have an experimental OPENAT_TZDIR option; see Makefile and localtime.c for details. On platforms like GNU/Hurd that do not define PATH_MAX, exceedingly long TZ strings no longer fail merely because they exceed an arbitrary file name length limit imposed by tzcode. zic has new options inspired by FreeBSD. ‘-D’ skips creation of output ancestor directories, ‘-m MODE’ sets output files’ mode, and ‘-u OWNER[:GROUP]’ sets output files’ owner and group. zic now uses the fdopen function, which was standardized by POSIX.1-1988 and is now safe to use in portable code. This replaces its use of the older umask function, which complicated maintenance. Changes to commentary The leapseconds file contains commentary about the IERS and NIST last-modified and expiration timestamps for leap second data. (Thanks to Judah Levine.) Commentary now also uses characters from the set –‘’“”•≤ as this can be useful and should work with current applications. This also affects data in iso3166.tab and zone1970.tab, which now contain strings like “Côte d’Ivoire” instead of “Côte d'Ivoire”. Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2025c.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2025c.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2025c.tar.lz The following convenience links are also available, although they may point to the previous release until the relevant caches are refreshed: https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz Links are also available via plain HTTP, and via FTP from ftp://ftp.iana.org/tz/releases with the same basenames as above. Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit 7e1145bfdb9630c127841dc8ce808a937a300938 dated 2025-03-22 13:40:46 -0700 and tagged '2025c' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: d14bc0680b9cb33d6526a2c0e483f2abafc2593cfe5fbfe7dcab940aafdc1baaec065dbaa1bb58b03586a8631ffdf43ebb22ff5a70503298b6ea2cf061d82c16 tzcode2025c.tar.gz 1e33f7212fd0ae2ad3c16e68f0c1fc7a6ad26a126b8406c379a5768d79604c6a816054bd0fe3a63228d70cd6a1fc2b1bae2a9f8014e102d3727eb9d21affa1f1 tzdata2025c.tar.gz 6fa233d6a884acd24b52c44b2eecf683f9403f44b39dcbe85b1ec92fc11f4daf6ee5143f05332faf9258b8bd8f7ca7d4882e19b1e3d892b4761be43fd4f39d51 tzdb-2025c.tar.lz Here are GPG digital signatures for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmk5+AQACgkQ7ZfpDmKq fjS7FQ/+OcQWOkAheWXB17w3dzqEaBTzzOFPoVWJkYDYYqRBFYcZHt6SL8NsJ6Vr 4PRv8UXvGZZhyamQY6CA3Te6/SRBTn4vKAPPYrwRxRENBHJtwf00H4khIqzL4iuu Lni7d3MyEurnQ99YKdCdsDM7V2GqGov8SFOIQWohAazL29n/396Me68Excr7WYh2 FY1qmbqQhBuh9WrQ9+YznWkKd5FcPj0a8+XBReABUR3yV58qZ4rvDhDpx+476U09 5PlOHgC3FdEII+I8ihKI+Y0FW20dDfyTc7Eechef2z3izlzaxSFbAXXQX1gs1Vj+ yhjp+MiJC9UiFP0VmafGdpuhNWafrRSF8uyhHEAPC2WRRSlz3hUBFchOWRBpgAkT yIhN7dUWPPT80Pu2vWn3Y647I8397b6mS5o8tLpgcU9S82phwY3zVtsXG4WjVVC/ RcNCyG0J2ybP+IA8r/jPdINLNm+lsdJKoU6Y19R+BJyAV1uycltUEx4yzxs8Mg/8 lxvg+JcKe94UhUHIQXo3j9lXg7KcFXCVjGBBBpfBn4FfcRmdA+IkgONF3MxWz86J 8jBJdSVi2/CjlteWVQ2pBKEEesjXjT0tX8dbVA2x4KAcWYT5jMMQxDEP+Q2uuKfj NhE4D99CiZwdYgi4JP4+86cTDArj9l17tWR9bmVXgyviFU4o3Go= =R12Y -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmk5+AUACgkQ7ZfpDmKq fjTtEg//VloILc1FvXSuFccnpY8G7rmCkL48q5628VbogfqLc3MSQ8FqlfBw3OkI LqiDAF22/nFcMhtQ9j61cFJ5GrAUF28MIKDl1ol5YEswQgiLxDxFbK2c5uWdYJed 4I5bqU8rs6RTA/5ZZ/MMDe7JIGEYClZhHzT9Hs9vLrg2aOW7vSzXjjuAy7FqUwpX k1m6KQtL6UPl4tkbDY9wLSifDtg6GqfZT9bYtPxxLKc89Mm0tFJP7aXuooELb0/k 1YsCFZDU7OK8ttgAlPbtAebfrFJbk1jKuBQqoqyH59QtA4OegHFjRVPFcHYevJsl FMhA10XEXS1C3T2KC9De9Xypt1aJIVIhtEHz7GjlubZRfgLGb+xAvTsJj2h20TIm mTAaJ9tBdr7TiVRlLdUgWdsLRwrVSOLbFCjL5Fa2+XpTNoowPmDp7YHmFsk+itDH 40fRFvBc842huCIsFbQ1EInjVpuUQqaMb1CmZlNMhJz6DoXEicOoo9iwqjRxZyVt 7NB4AQaqBwAKgvTw7iV4Iw0naWaKhwN9pP2AbnC5cMd3SRMneJ6Sxt4MtA9dqpFB mKIMF9Tlb+twuyOZXezaD/RqJs19gusdFmVlpJbNzez//pYMJ/9LcjB+xz61c5Zf mIPWE0mkzSRvhqca4L3inlC73aTRDp2OEt9+n+AJPnk27BRe5Xs= =1kyi -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmk5+AYACgkQ7ZfpDmKq fjRXzA/9GHRwVUZRXXmlwgpPZDVU5BtB2xrcJVQk3pFLs0J6cz+nUVRtsm3Gz400 qaksn6T+azBX5Lv6pSPYmDtj+cSbCA7vcaLxHh414gKu6SKkNTm566xGM3RIKome odhacZtLvPYpfONIGt0YRgwl6oO+Q1dXuu4aoi2H4jdYrHEjpTFY1Pg1TfRrpM/p JxarI/VUOvuXZHAsJRBJshEc5GcOnaUAzYKr/yAelbdowjW2DLetRhWU0YZ9zgZk w6xaVNvcU0i9fX2Ri0MMiTpo92xzRdZd1WZ8wfU3hqUMfolVSMJuk8Qs/NyYm8v9 DMtiQb0Ewi10Y0YyGUnQi3r6wpKQ2K1D2JVZj5eGLsbTfBpi+3bilJHtxBc05NaK HQyZhhgXSTwLkR4LUcsyTtWdiS9uUB2D18EtfxODWoeJsIcoU2fRPX3zVIn0EjTq YLSrGvbk69xAiyhDQlcYFEUoL6GQb0WbDOz1b1IwRJ6de7YcNkkCAlWTt4qIat65 6OfZURSGURRWd9BBNqF2m1OgaGfv4fn/HJL4TYYaEXATpTUxVoPujxl73In5Mu3O A8zVP2QouGD25RYmoQLdAYMyap9XJIS1HWRNBPAyRC8z5YZE1ptm+L0KzBD9+vwe rTejW79L/QMsu9Orz6Mnptraz6C83q7C1hi7STqwNPd4rE8grV8= =MFmx -----END PGP SIGNATURE-----

1 1

2025b release of tz code and data available
by Paul Eggert March 22, 2025

March 22, 2025

The 2025b release of the tz code and data is available. This release contains the following changes: Briefly: New zone for Aysén Region in Chile which moves from -04/-03 to -03. Changes to future timestamps Chile's Aysén Region moves from -04/-03 to -03 year-round, joining Magallanes Region. The region will not change its clocks on 2025-04-05 at 24:00, diverging from America/Santiago and creating a new zone America/Coyhaique. (Thanks to Yonathan Dossow.) Model this as a change to standard offset effective 2025-03-20. Changes to past timestamps Iran switched from +04 to +0330 on 1978-11-10 at 24:00, not at year end. (Thanks to Roozbeh Pournader.) Changes to code 'zic -l TIMEZONE -d . -l /some/other/file/system' no longer attempts to create an incorrect symlink, and no longer has a read buffer underflow. (Problem reported by Evgeniy Gorbanev.) Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2025b.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2025b.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2025b.tar.lz The following convenience links are also available, although they may point to the previous release until the relevant caches are refreshed: https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz Links are also available via plain HTTP, and via FTP from ftp://ftp.iana.org/tz/releases with the same basenames as above. Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit 7e1145bfdb9630c127841dc8ce808a937a300938 dated 2025-03-22 13:40:46 -0700 and tagged '2025b' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 19826b12968c10fc4db7e4b07ba782bfb8590eeebaec6f719d74b92a2e642ab817bd72bceff0015ce52a838edfdb00753b3cd87dd84b35abf2606e5bee445f76 tzcode2025b.tar.gz 7d83741f3cae81fac8131994b43c55b6da7328df18b706e5ee40e9b3212bc506e6f8fc90988b18da424ed59eff69bce593f2783b7b5f18eb483a17aeb94258d6 tzdata2025b.tar.gz 4f4afca86645ca5564a9d7d3ddc36e6b07c15c1b87cd4edbbcae72c6be4e6154e4ad1966407a7081237550301f1093af53dd8a486effb95f7cf3e5721db47c8f tzdb-2025b.tar.lz Here are GPG digital signatures for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmffIRcACgkQ7ZfpDmKq fjRqwhAAjdPreNSN3pJoZiSwQNVk6oUneEHRlNVDFw1d+DflHG2QW4Cw7wWSRaYi B+yxIV1C61ZwhkAQ1AlscFbpzvHcOtNLEgK5VTwOpgBJ0FsmsEzVUCkGYFtWDpPw qf6ZgdtSrmaPX/V+ceWrRE0oQUjFnlQEO3cwGITlcYlck9YUiQZ+y1gOzPypN+v1 YHuVzoMk4ESTTI/glEJljOQfNcl+GvgnMZRNdZWafpjJ2y68JLofEgemKgJqTu9J IKE6Age2fn2P1lyXlFg1ZTzm11XDIWa8cz37rabNqaybKICeMppSEiIp+BcrMl4p ntQwJyytmm8g2AyGUdHEa9rN97pTag8zzBNmQX/5clcYWIvlp964ul9ptXrBkexN iv+Xi2U1zFg+Wo+ytMyj1q5fhBPTe1rNsnngbrgbGFx0t5h+OOVIPxMCAQiKgGg3 w6V59jgKThJ4EbFaCKV1tN3eThxeSrmCEb6zQEGlS5QKOyTnpQNCEAlJlJ+JyeDo tMbPfCzR9EJjrrMB50qMNK9bXJK3NjsOVicJkv4aruVPfPZ1RrAD6ZDTUk7Yxo9x WHT68C2XIde67N7UIcV4gWgbuZKKagkqPnt+dtn8C/5EML1ANEhtF2is0PqqTXpI ol9XLYC5mnlEQB/F1Bu7EppPCMu7qCaFWQCbvvXaaYjUhiupFPU= =EgQ1 -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmffIRcACgkQ7ZfpDmKq fjS6yw//Wdqj0sipbfTMHAJh3y5065wUkwJhi4cbMbpG1MfJ7HQOeF/ISXBnQo2L RIzpRPswIUweKziBQx5+f+VgViWJTJRTbb2Vk0i1SfnQ6BfeEmqIXwxa87rSeCEk vBeur6mnv3Nc/f9HVvKBqx9ux6FIPWMoQbuDZyNh/GfAvrCp69YkC4miZlo8D1M5 QKoNqLB2B/JTeFVdchVYu9Jxyc2LGsSM9SDTuDDHKQyMyZN/93vJiSzfUMkzW6AF dJif5zWaj2YfrcMFP87IMKH9rAA6XrKNbf+0Xu7AWKpMW6vu30NyMoLQvuo1Gf0g uFxqFTu7fVt6ZzO2cVFuzS/MPj8pufPng88gOHpU34ASID5DB5hf98r7fxmn3jwc aBiecrqpq4F4GEqrBQHGVugFM95iBElvl5kEupO0C/8wqvV7gWoo8Qiaix7b/DE4 zpc4z8wNHntqjeP3Qrv+zX9wfZThYoX/j8UuIVZEhm1o/vHeNn5zBZz55jCQ4KOc Sffl68lWjdLkcS4edsaM1GyPsFnqaFP6FZ95zrhyl/mpsDNJggIaL3RuajMIMCBt othXosBAuBKlv3gqXBIEDaifp2aqBo0YgUUJhcVtyv+advzcUgeppnMUPh0US66R inVSt7pMQ8ubYcDQzDchoVPEay/69SPaRRd3W9unQGCBepjaXGo= =W7AG -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmffIRkACgkQ7ZfpDmKq fjRvqQ//cupgXsGqL6buntdGU8QnbY79jmNbXkuzSbjiAx+uh+sCoS34Rr9eO4Kg mFdVaPqZ704ZvI7yzh6amjpkwdYalmhjVogJ3AIHSlAV69UgedztED18AjQ53/Hj gRqqppZacgUmVO4GqybEb/f4toWfnVi8HuCY++q1WkMgQsAqOE9DIJlJOTK5BAEo Iy6+vAigXc7LyveyBP/2yOOoPTkWTRTURfXHXgQxgKuGtDJHnp12j2MPhzag5s64 KrInD6ZB1ZcpDw9BpDd+LmB1gZizwShadXbiMOi8ROC6JwR8oafZJq3rwonSkJLH kMg6VUQr3cQmu8Zd5s9yYpZmx4rMBR+9Hsz5bn0cBLSe478LtmoKI6vI37mZ048S PRTwlHnXi1/RuxovhusPiaoAf3VUN8IxhL2V4NV9D2Pn+iu3Fhj35BlM3XOn1RpH 3K3qi/Wr4XRX6jlPLQ42opBnkKorL21+Tz21+yHDOXxbF+9fYmZOaMaZwl3AjX66 QbWEN8FG+2UEOHVSyxjLKru97TV+RXSo/A1IBwTHALeaiLSc+V1zSTMMrAQVSDPm Rn1VXPc9Jff00LEM0CElS4X719d/0a0Knbs9OjIbp2bmZEun8zTGHOPEtJ8PWrc6 ficDmgynqV89laKtZ7VsUoMgHEKv7dCs1HdFBYQ5qvWW/JiKZhU= =qJJK -----END PGP SIGNATURE-----

1 0

2025a release of tz code and data available
by Paul Eggert Jan. 16, 2025

Jan. 16, 2025

The 2025a release of the tz code and data is available. This release contains the following changes: Briefly: Paraguay adopts permanent -03 starting spring 2024. Improve pre-1991 data for the Philippines. Etc/Unknown is now reserved. Changes to future timestamps Paraguay will stop changing its clocks after the spring-forward transition on 2024-10-06, so it is now permanently at -03. (Thanks to Heitor David Pinto and Even Scharning.) This affects timestamps starting 2025-03-22, as well as the obsolescent tm_isdst flags starting 2024-10-15. Changes to past timestamps Correct timestamps for the Philippines before 1900, and from 1937 through 1990. (Thanks to P Chan for the heads-up and citations.) This includes adjusting local mean time before 1899; fixing transitions in September 1899, January 1937, and June 1954; adding transitions in December 1941, November 1945, March and September 1977, and May and July 1990; and removing incorrect transitions in March and September 1978. Changes to data Add zone1970.tab lines for the Concordia and Eyre Bird Observatory research stations. (Thanks to Derick Rethans and Jule Dabars.) Changes to code strftime %s now generates the correct numeric string even when the represented number does not fit into time_t. This is better than generating the numeric equivalent of (time_t) -1, as strftime did in TZDB releases 96a (when %s was introduced) through 2020a and in releases 2022b through 2024b. It is also better than failing and returning 0, as strftime did in releases 2020b through 2022a. strftime now outputs an invalid conversion specifier as-is, instead of eliding the leading '%', which confused debugging. An invalid TZ now generates the time zone abbreviation "-00", not "UTC", to help the user see that an error has occurred. (Thanks to Arthur David Olson for suggesting a "wrong result".) mktime and timeoff no longer incorrectly fail merely because a struct tm component near INT_MIN or INT_MAX overflows when a lower-order component carries into it. TZNAME_MAXIMUM, the maximum number of bytes in a proleptic TZ string's time zone abbreviation, now defaults to 254 not 255. This helps reduce the size of internal state from 25480 to 21384 on common platforms. This change should not be a problem, as nobody uses such long "abbreviations" and the longstanding tzcode maximum was 16 until release 2023a. For those who prefer no arbitrary limits, you can now specify TZNAME_MAXIMUM values up to PTRDIFF_MAX, a limit forced by C anyway; formerly tzcode silently misbehaved unless TZNAME_MAXIMUM was less than INT_MAX. tzset and related functions no longer leak a file descriptor if another thread forks or execs at about the same time and if the platform has O_CLOFORK and O_CLOEXEC respectively. Also, the functions no longer let a TZif file become a controlling terminal. 'zdump -' now reads TZif data from /dev/stdin. (From a question by Arthur David Olson.) Changes to documentation The name Etc/Unknown is now reserved: it will not be used by TZDB. This is for compatibility with CLDR, which uses the string "Etc/Unknown" for an unknown or invalid timezone. (Thanks to Justin Grant, Mark Davis, and Guy Harris.) Cite Internet RFC 9636, which obsoletes RFC 8536 for TZif format. Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2025a.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2025a.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2025a.tar.lz The following convenience links are also available, although they may point to the previous release until the relevant caches are refreshed: https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz Links are also available via plain HTTP, and via FTP from ftp://ftp.iana.org/tz/releases with the same basenames as above. Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit a8e2fcd87bc5f83fec0a76652095e8d7881b0763 dated 2025-01-15 10:47:24 -0800 and tagged '2025a' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 308f6a3d6ebfa18446f8296e5c799e18dccecd79ace3ba004d3f233892c7428faae152b217b22d229c59dd4e0faafee797d8b3583b58fa982b81f7cc7347f502 tzcode2025a.tar.gz 93b8f939d39bdfe451e262666f9099c529c96c49d14c08e3611560ca660e12e16d08a22b145d615e00570fb194881618d6f9a0a617c119ab447be03279d747c3 tzdata2025a.tar.gz 1e8c4e141158d63ca5c39babc9d18c32df14e2e59bc7649a7fed8c3e577f7b175bafa43883cf351139ff198515f5f8c22b1418e2ac7efb7f837faa8f61d2574d tzdb-2025a.tar.lz Here are GPG digital signatures for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmeIA2oACgkQ7ZfpDmKq fjT4TA//dFIBsmsl3OJ7QdI3lnySSQWyNnZQjsue3qtw7dUp0nbbFd7QGegrVDSC zrY+v51AVm9sk9hLdLQuyVFm5xRqXuBp2fC70wFeCCocEMp4HnhOogJVXMqQz+Dy AFZ8U7HmtNUI+ca9MTw6WTpQ5DOy6Of5rer3LbicmzBgVQ/UNcoIFZs4qf+RnMYY GKOHfLDLhs/4fQf3+zfELLbavieOoqcQlp8HntZrCuR2zZZNImVkt0/ljtTnHqd/ b0KUMDbYQ2dGsNbpBQS5GhAUjVPeUB5npqfA0ibS1gv1e99yWwGeMmUY3GqFbQWn dNN5LTceS9/H/+thtgN+70g4b2Haz+So91AiXKMNxgvb9qkjqV+2ZFd04ud4hapz +rRV8y1VDP/QEmXwL4zMnx+xkzGr3xTh+0z67R3RBIbL5eRGQojjKN1BLkYTWRsx VfaI51+GJWKjlX1Mo9OoSGGWgRWPgn591dYcep+cKA9jYSMzO48VOsdABIt3tTbX 7zqONqpDt6JZJJL7UdH2A0Lik8nkGFnSAnuuwW948CGh26odotoXAC15xWbK18VN v6T+zGZoLR8PdVlIYPjNUyS0sqo6tZtHa3Nci99+A5XG30oX+ecz/zlyDuRBLWkI 31bmm5423PHZ4N94Yi2V6xAC2G7mHn9m7eYv71C6Pg6fs5vOTgA= =2Ldn -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmeIA2oACgkQ7ZfpDmKq fjREhxAAjB1QDroFoq07V+56IIrJR3pK/x4Z2jBbg53N49Cam1oMZK5Wxm291d0G lPutNQvjiNubnBG4pgMMQ2xEF6jgYY0eFfLlORGK9IoW8e3lnlAqSR9BsOQvWjeA lKfmBkhFXetSJ8gu2ModVybpVIqDaJJ73sNQSsA01MHwz0RLV5CLOHXitJ8lBO68 vdSArRhalLUEIVytAKyy1a0msFdzrrDj/7q6tMV9NDY1xQg4V9TLxnPNds29H0x8 xO2zrDug6zrbg9z994JYkhq9h9DLe5h4F3StnaDwRK8eLLRq5D7ryK77Z8dtyXZf tDPgiNc1MquSg48481dDiUfsRdN5S2OLVFqjyWUuwVKBSkSRv/nBQqisGEybY86T H84D5WA0zlj8mFJyuKFmvGHzzKZ6X7mUNrTObaY3G+QHgHjIKWqO7oog447YOYOG DSA5rSmYrzZp2RXP/doeFZD+2kbNVPlN8zBh6lANABwvFH6IhDI+/OJzGJqeYotz ZWVoU3um6aToMS4Uv2PdBNbH1W1P1pzzMM5TJ/bQO/ujCwaBSTwoDPJT6tW9BLrO gJUWd1AumocieAWc0Vyzbrpzbo7Vc//1LF+s1eI+zWt8925unFrBArvQ4h/PyXsc O5LhOQVm1986y9xy2YyF+Cy5s+xsKvKENQ0NbLIDa+l5MdEdEXc= =NQgW -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmeIA2sACgkQ7ZfpDmKq fjQkcQ/+MWIjE3J5FETCaYxUvElzWIN25Jx4p3dBp4CL/UqD9qW/3CRiRt7KbS5Q 2C1+Hg5DKGAJJ/9/L72t4ttMheskUkGyI/M/xWuG2EKMRPJd3zEPZItSfJOtbBwo vmmTIe9s/yZTkmeoMQ/PVdhci6rwifwUEopxq3V2pTBIBnj6H+hBlSLL8Y7RgbWQ yDlzf1HvfnQ+4xlhtcDNb49iljlrPEwUJZe+2RSPmxAtAHe6SJK4i9tSQlv0fJew whM0//rlihNKRG04TFJ4lw5UeueCKhLL8E/HLbLewVcJcbd4pHMFNmdxi17VHmZj IG1tj75Ff69dyuZiCkuOe9S5SzKlI40FEU3aN1k7wWz3PzBbGBWt9CMxNY35DpLF Di23QeTOvdDEEccjivRVyNc4mwthnylOcmKcE5RYhT45W+Tpr0BhLnE29/ZwZ3Dy EB8wQJvGZWh6LVK2C7unEmQaYmPD+pl8WoZ9MmZHnR0YmNd/NfcefKX/UenLs5+J HIifuTWnzRfA4DQTbV+l/kNUzOo/asoD98qQ6/2inDEQWCZpg1V1sOFcHVYkb6XX LT7PUnC5eiKS8U47KBzTTwkEAWij/LKD+gnksjfkzU/Pn5MpzXm4qwVo7v9yuEal i4nIbqzuY8iK0SYBw0da8W10dFtB3bgtfUuSTXQLCP8sWVI34bY= =B68m -----END PGP SIGNATURE-----

1 0

2024b release of tz code and data available
by Paul Eggert Sept. 5, 2024

Sept. 5, 2024

The 2024b release of the tz code and data is available. This release is prompted by the accumulated weight of many non-urgent changes to both code and data. It changes one timestamp abbreviation, for the long-obsolete System V setting TZ='MET'; see below. Otherwise, the timestamps affected by this release all predate April 2008, so you can skip this release if your application uses only tzdata and does not use older timestamps. This release contains the following changes: Briefly: Improve historical data for Mexico, Mongolia, and Portugal. System V names are now obsolescent. The main data form now uses %z. The code now conforms to RFC 8536 for early timestamps. Support POSIX.1-2024, which removes asctime_r and ctime_r. Assume POSIX.2-1992 or later for shell scripts. SUPPORT_C89 now defaults to 1. Changes to past timestamps Asia/Choibalsan is now an alias for Asia/Ulaanbaatar rather than being a separate Zone with differing behavior before April 2008. This seems better given our wildly conflicting information about Mongolia's time zone history. (Thanks to Heitor David Pinto.) Historical transitions for Mexico have been updated based on official Mexican decrees. The affected timestamps occur during the years 1921-1927, 1931, 1945, 1949-1970, and 1981-1997. The affected zones are America/Bahia_Banderas, America/Cancun, America/Chihuahua, America/Ciudad_Juarez, America/Hermosillo, America/Mazatlan, America/Merida, America/Mexico_City, America/Monterrey, America/Ojinaga, and America/Tijuana. (Thanks to Heitor David Pinto.) Historical transitions for Portugal, represented by Europe/Lisbon, Atlantic/Azores, and Atlantic/Madeira, have been updated based on a close reading of old Portuguese legislation, replacing previous data mainly originating from Whitman and Shanks & Pottenger. These changes affect a few transitions in 1917-1921, 1924, and 1940 throughout these regions by a few hours or days, and various timestamps between 1977 and 1993 depending on the region. In particular, the Azores and Madeira did not observe DST from 1977 to 1981. Additionally, the adoption of standard zonal time in former Portuguese colonies have been adjusted: Africa/Maputo in 1909, and Asia/Dili by 22 minutes at the start of 1912. (Thanks to Tim Parenti.) Changes to past tm_isdst flags The period from 1966-04-03 through 1966-10-02 in Portugal is now modeled as DST, to more closely reflect how contemporaneous changes in law entered into force. Changes to data Names present only for compatibility with UNIX System V (last released in the 1990s) have been moved to 'backward'. These names, which for post-1970 timestamps mostly just duplicate data of geographical names, were confusing downstream uses. Names moved to 'backward' are now links to geographical names. This affects behavior for TZ='EET' for some pre-1981 timestamps, for TZ='CET' for some pre-1947 timestamps, and for TZ='WET' for some pre-1996 timestamps. Also, TZ='MET' now behaves like TZ='CET' and so uses the abbreviation "CET" rather than "MET". Those needing the previous TZDB behavior, which does not match any real-world clocks, can find the old entries in 'backzone'. (Problem reported by Justin Grant.) The main source files' time zone abbreviations now use %z, supported by zic since release 2015f and used in vanguard form since release 2022b. For example, America/Sao_Paulo now contains the zone continuation line "-3:00 Brazil %z", which is less error prone than the old "-3:00 Brazil -03/-02". This does not change the represented data: the generated TZif files are unchanged. Rearguard form still avoids %z, to support obsolescent parsers. Asia/Almaty has been removed from zonenow.tab as it now agrees with Asia/Tashkent for future timestamps, due to Kazakhstan's 2024-02-29 time zone change. Similarly, America/Scoresbysund has been removed, as it now agrees with America/Nuuk due to its 2024-03-31 time zone change. Changes to code localtime.c now always uses a TZif file's time type 0 to handle timestamps before the file's first transition. Formerly, localtime.c sometimes inferred a different time type, in order to handle problematic data generated by zic 2018e or earlier. As it is now safe to assume more recent versions of zic, there is no longer a pressing need to fail to conform RFC 8536 section 3.2, which requires using time type 0 in this situation. This change does not affect behavior when reading TZif files generated by zic 2018f and later. POSIX.1-2024 removes asctime_r and ctime_r and does not let libraries define them, so remove them except when needed to conform to earlier POSIX. These functions are dangerous as they can overrun user buffers. If you still need them, add -DSUPPORT_POSIX2008 to CFLAGS. The SUPPORT_C89 option now defaults to 1 instead of 0, fixing a POSIX-conformance bug introduced in 2023a. tzselect now supports POSIX.1-2024 proleptic TZ strings. Also, it assumes POSIX.2-1992 or later, as practical porting targets now all support that, and it uses some features from POSIX.1-2024 if available. Changes to build procedure 'make check' no longer requires curl and Internet access. The build procedure now assumes POSIX.2-1992 or later, to simplify maintenance. To build on Solaris 10, the only extant system still defaulting to pre-POSIX, prepend /usr/xpg4/bin to PATH. Changes to documentation The documentation now reflects POSIX.1-2024. Changes to commentary Commentary about historical transitions in Portugal and her former colonies has been expanded with links to many relevant legislation. (Thanks to Tim Parenti.) Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2024b.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2024b.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2024b.tar.lz The following convenience links are also available, although they may point to the previous release until the relevant caches are refreshed: https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz Links are also available via plain HTTP, and via FTP from ftp://ftp.iana.org/tz/releases with the same basenames as above. Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit 6903dde39ed637adaafc352c4b6993739253f058 dated 2024-09-04 12:27:47 -0700 and tagged '2024b' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 0e4e872d6c6d9e2ce8c4e567fcbb7658942b8544157d1e48673d9cb989f3af3379fa58e7a71ab98f4a8f2ac6727de1f8c4cd1981053409ebd8989345dc640026 tzcode2024b.tar.gz 0d86686e215672343debb3471b7e7ccb8a27f063f085c9b532d5e0470377843daa0dfb6aee0db4fb9068dd52810c69aeee914a1a7c7e603fdecda7e855020193 tzdata2024b.tar.gz 72446e5cf445515512437c8deaae3063b093aab9620d6441cafaa9b3b71603c857f7ba53557579595788bbc901cd6142404b4db6b0e9f2b23d57b2b3cbc837a8 tzdb-2024b.tar.lz Here are GPG digital signatures for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmbYtYgACgkQ7ZfpDmKq fjTPkRAAvusnEE+0TDcfXqA/eEr4LksyAWMjLcIU+xakuXqbBGbGZIeEeDjT58f5 IWhKZyEc6JPgL9T/0TSBUW0IwC8JqiYkK3oovQPlcQkufwkCe2GNqAEWVRuT9Y4H trFGM53tNJJA6GySNBCvtaglIkj7vCQJ+gQ/NACEcxlxypy0TRRqAG9ZcUT8HpRI Hh5+TTBJdxG9PqLBI/INbKlEvpFovMjV0UXvlqfO/R2vanZTOlanjW3/g0PgzcfO GvNRTC8R0N49rrieGj4iUUDPaSi7rPW9hLX6OQDc3ASUjTXHw7uL1fkVTCUdF+so f6r9UTrTjOofQOjziR1BfA+SRv79mWOLSxW+yJDYLPkPjEEIUnmIoIoSrDXdqXC3 p7nWOJzFGEw7Q8FBBzOtcFPOiLohNe+zg3reAy4P5Uw8P8DeYm0T/jaZUQGLF2gx Xp60+KkzGuorfzPECqzUW4RNT/+7hVChf+bxRQ14upnpx+rjBxZMX9lFEzismF4p v3cCAPJ038CHDSXkwnBefKRLoWhzbov/MxJ+FgbksuhlaO/0OdQsP4e8tv8RhvHk tTl07n7tU8NPO1J6osEIRXggVKW/fo+ifCtmkHqvE21vtSq1NccYZYphkvZlQdmk oHFyAIxRdgEv2iS4KGlXeY062ZiSKAy0LdhEIFcGr59bLE9wPuA= =tdRE -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmbYtYgACgkQ7ZfpDmKq fjRqPA/+N+f7KwPQJYYFtLWudtXxGIVEYDsBtHcqlj20FsdgsKk/9cdm3zKTWFuF a5uKn6plxwN6hmXjrwV7nBV6M8kxeqRP4Zf+rCdNMWhLGSmHmDCU+1m5SPYs/+Xh P2W3pc310pQocGtMIsYoVYrEtQl/K4p7V6jxAaG8QTpWmt0K6RS+LxxfqgKbmq14 tU8Jznx/LBFbvEmQxNAGKzq58ce7yexIRRGvetHGWvwafb9+Vv2CiOx+oCS2GeEF APO2UdbZCiUaTJYZPtg2vnk2pGDrTAO/jsEe486iKinVAOkJyBckn/yqykh5NLCk q+MtRngIinrV88KqpmW1OXuAKjJJLXrveAKoZKVbvMuzBAMG1YvAo9CzBwHYfKhW bxLo9q9HyRgci9xoMOeVi1xabTm+NkhbqQuu15rQLlgXoMYm/4x9PbP7JSeuB8N0 vyGjyD+tZtDXgPC3AARmpPuabDQQ9BM0RJ5exUOkcAbvYyFE3bVHLPk28iZOzg8r Y/BSUOXIj7Jb+ZOuIkuDRWHvDifTBrpPDDlwY4JWUfRhx2HhrFjD59SJt6kPNsJE KAjVQREtXDtnqu3bZ7AsKzckpFlrlk0vYfeKaL5N3O6iEpggmE0LTWDXRcrzESh5 E1uQBnIrS4CHuso1wZRy0FHJYvSKGbRCN3jHyJBRSGgBTFGOuIY= =AXnJ -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmbYtYkACgkQ7ZfpDmKq fjSLXhAAnP1lRfPZ5pQhV57GAvYgMyrHpQbnBmZUHLESPRlqETzjDiA/n/tpaWBz ypvD91O0O5F2jf7JTGO8OgN3UARuOLE+Ry/gtW01udC4Z083ALsLovJKx7DbaCcc KwxK9Ia1++T/nulJsEH5b+6w78ptUbqnbwIdwzqDnImJn3OFdAJddapI/z6iDDEh 9EzSlykcHec9aYdC9KEFJaPjzABxDlbqhDM3QEkheFHXiZtt6fTg3fH+B3uetvix IfHAyYA6iJxezY/rqr+k5loa+ObTj8Rh11bF0OPJoWVMWLNDDWUa/h/SIm5zfD64 wl2aRw+yYSB1Fp1W9zOxJJyYnJvlBsNBU1KZEjNaCxbjcmeUtwyYv3tl8dq8NABL KhafPI6Cvw8NAI4c7JI2lDbLdLTxRNMar5uDhXPFZ6CGbBGwjyiVR2j73FjgngUk nHC2jw3UudfrkyWArArIwUPz0GKtgkQPTGUnWn1lZZP3QI1rM5Vhk17s88E2Igls AkHZYPI8X6118u+deVsyG9d+8v/vNbPkMMC/wqv4tqJva4Yu8QSWP6ZLFZhO1r6q 2ZHEEGPftF0tZETkWLr4Ndpbny6a2jeNaT9/qBRjSDpD4hIdBgYbfa3jKFlNZAx6 o9xVZy0n5MgXh2FOFFWIepYhQvwngnaw0kf3YqTkk+4xcKsgM3w= =qqXx -----END PGP SIGNATURE-----

1 0

2024a release of tz code and data available
by Paul Eggert Feb. 1, 2024

Feb. 1, 2024

The 2024a release of the tz code and data is available. This release contains the following changes: Briefly: Kazakhstan unifies on UTC+5 beginning 2024-03-01. Palestine springs forward a week later after Ramadan. zic no longer pretends to support indefinite-past DST. localtime no longer mishandles Ciudad Juárez in 2422. Changes to future timestamps Kazakhstan unifies on UTC+5. This affects Asia/Almaty and Asia/Qostanay which together represent the eastern portion of the country that will transition from UTC+6 on 2024-03-01 at 00:00 to join the western portion. (Thanks to Zhanbolat Raimbekov.) Palestine springs forward a week later than previously predicted in 2024 and 2025. (Thanks to Heba Hamad.) Change spring-forward predictions to the second Saturday after Ramadan, not the first; this also affects other predictions starting in 2039. Changes to past timestamps Asia/Ho_Chi_Minh's 1955-07-01 transition occurred at 01:00 not 00:00. (Thanks to Đoàn Trần Công Danh.) From 1947 through 1949, Toronto's transitions occurred at 02:00 not 00:00. (Thanks to Chris Walton.) In 1911 Miquelon adopted standard time on June 15, not May 15. Changes to code The FROM and TO columns of Rule lines can no longer be "minimum" or an abbreviation of "minimum", because TZif files do not support DST rules that extend into the indefinite past - although these rules were supported when TZif files had only 32-bit data, this stopped working when 64-bit TZif files were introduced in 1995. This should not be a problem for realistic data, since DST was first used in the 20th century. As a transition aid, FROM columns like "minimum" are now diagnosed and then treated as if they were the year 1900; this should suffice for TZif files on old systems with only 32-bit time_t, and it is more compatible with bugs in 2023c-and-earlier localtime.c. (Problem reported by Yoshito Umaoka.) localtime and related functions no longer mishandle some timestamps that occur about 400 years after a switch to a time zone with a DST schedule. In 2023d data this problem was visible for some timestamps in November 2422, November 2822, etc. in America/Ciudad_Juarez. (Problem reported by Gilmore Davidson.) strftime %s now uses tm_gmtoff if available. (Problem and draft patch reported by Dag-Erling Smørgrav.) Changes to build procedure The leap-seconds.list file is now copied from the IERS instead of from its downstream counterpart at NIST, as the IERS version is now in the public domain too and tends to be more up-to-date. (Thanks to Martin Burnicki for liaisoning with the IERS.) Changes to documentation The strftime man page documents which struct tm members affect which conversion specs, and that tzset is called. (Problems reported by Robert Elz and Steve Summit.) Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2024a.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2024a.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2024a.tar.lz The following convenience links are also available, although they may point to the previous release until the relevant caches are refreshed: https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz Links are also available via plain HTTP, and via FTP from ftp://ftp.iana.org/tz/releases with the same basenames as above. Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit 380c07cef01c71c1f93e9709d9f8c79b91cff063 dated 2024-02-01 09:28:56 -0800 and tagged '2024a' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 46da8bfa762c7d109db93e5c060789097fc0e1e38bdad5bb8fec886ef47f138bd03b913a743cd5f7e23dc359a72bfd63e7ffc0de199d2b51e6a174361dbdc43c tzcode2024a.tar.gz 1f09f1b2327cc9e1afc7e9045e83ee3377918dafe1bee2f282b6991828d03b3c70a4d3a17f9207dfb1361bb25bc214a8922a756e84fa114e9ba476226db57236 tzdata2024a.tar.gz f1a3b06ea2b28a0bf968b75f3674f3b64d8226338d42e2ed17aea33e34bff0f9a7a22f4116612e6c81b9b7b57deaee6ed01a6881000fa1042a7f4390b55a1856 tzdb-2024a.tar.lz Here are GPG digital signatures for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmW716sACgkQ7ZfpDmKq fjTCyxAAvMohPXC5+oZT9T/X0vhIkK5kJOzDF/eptBVzwxa8WDymp4q7UzGCC2Kg 57dWthckzYqrvcz3QBLagF8bFFVCrQKPiKbMZUYTin+eWrxLUDx1sHOPaxWMPFrY aHjy/HGVMa43P7wp/3iaLLwvuVmcxcWiLy5ebQbXQrFbe09KJDb6mK4ClR+1KdLd aF8BCSU6nI0KQz1bRqmHlm+J7X1ll0E8YymWoK7Ujwht8SYRqpJOqOv2XJ8g0wFO wip6p535KQ3iEIQqc25Swn4v3W26hfa2yZXMh0edgQe1uqqzV3rLi7n8sOrSYjjd uwzyVC6wADGM2PgH4dq6YOeOs9jB+wTm6MEH4/GXP0IpPNPswUnHLK/WJGTHidW4 HJ0hY50S24wMxNYiaiuSbo8Lgefky3GZKZo+umXVKlPjsSrvImaWmFH2gOqvbZIi Ujl/NjDUmH7C4UDGx/ZkLwpOwjcu28hcacLkd6ad3hnFuZhG28yKd9rdQFn6/PTL rX8uAtuJ0GOREWAQWBNKj2dnyOrE45C+EbbuSCobAzvSXMyJ9svb7WuawmhqEjf/ DXY3VJ7pEAViQ/Hqtkxp8R9JfvZ6XCL8EF18eReeJdejjVObNIoUMOyPFX5HXJbs WS8yEl63iDyzzj4Jnvu5dMv8VlWel4CBCCJSkHjtrX9PewqbGq0= =aSZf -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmW716sACgkQ7ZfpDmKq fjTkQQ/6AqS/VNV6+RbbyLbLuOzh4GvYDMq1xTxGnjj7nwr80ob/wwSVmX7Gf5xt gVgagC75EJyskY6dfUPbSHwmOx8Dk2ttQtEprhhzk+1WpUSPZoy/RYMdWN+JzO3s LekrzU86SAh7yP21qSovYRM5rW02Da5RmiLUmknzBpP2cuZsq3qSPYUEMjB3JO39 OzBq0nyLbUR9nqew/f6fcPviyweqTkZdcDsr/+jNUGDI/kezGQ0u3ExlGc0EmGU0 ISAFB7uSDWgoJlwH3ZBtI4lOxiVQRKXafFcdvmLka0hYDGOm6f2zvkhvLEHVN9xK /V680qKy1vIOkyDRp664P9qZ0951+tpb9I47ip7SLqqBoyWhlfb/SJ2eFfb3k+kx fPkCX89QsqkfSPXySJCO13YYEQXpI2VPdWi0JxDI+LD/VEHITiydrYT+afnn0iyZ bM/TKnqaQ4bhAXdLBj3oUSwFQHEgPgeLOrTmWEdN9YmO5Cwbm1gZvOKZ4u2CYW6I ZM+ZwCuNO1hqYRSoeIaN60fUOneXaOcAejlOS/bJr7hNKUtmAjsSS7S7YGeNgQld LXRDRD3vou/qIHlIhmGpTUlOBl5NXVrP42w91nBYEwNyY4lbKLw22GS4FRF1cu9+ wfMfJqY4wwDp/uDMXAfWIXU1AdMg7t1NephMIGg4mivKGYmQmvY= =CvSR -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmW7160ACgkQ7ZfpDmKq fjTlmBAAnPjG9L1PG/4AlnLSdrXhXEVirX6LlmsUjh3DRzXlHjeEHUcD+rEL+wFK cM55uo+yzD7iq1TC1FXxbVKpxFcTxtgNx6Jmz2sHYjymCUmqPFVaj2GtCEwiBaKA CioxHZuQoRaSQnsmGzM/VhC30VMPj1S8SoFNZhbhXkNr0Wxy/f8xxnwcIDRvdzOD 9DvUWqJ5W0jHg/2m4RmbTavsp6tZSdcxoe8R5Ie33tQL7Lwqsze4dkggbzdCFd11 bPhrB9l2mQ6l3KrZ+VQRthL9VJPMrkpgFNK0XiCn+8ctaJS7dFjIspcTtIUbuyiF Z4YMcOUnLdLeL0OwFP1dRNz4kVlLioAO5dfIAHjPdRF0slywcFaw4BWB81Vwwkdy BjkX8nWmFEgYy1DoDYPBf5ju5SNcafPnQ20tO3Cjyzdg57Dc4nN7rd21t6bcPWTw 8FjzOvFoeSjLmzK+4EB5Sx9r0xsP53KSNHYXG272qqkRDtKhi62KNn6ZWR9QMTM7 yIh2OC+yI6Nrp0SAR0CKZQCtM7ghjBQYJeHliW6BzCmAolRaH2Ng5Z+rFDLyxtc2 L+VWkZROyyI5dQrKTpq+pzS6LtidbkM/hyggc0GE2mqGr78f+pEHHXsNkq8xtVNX Z1HLQe0cvORQsi9wH1yNFRlwsflxfN1VHhNhNXvYdtvJLfbwr7M= =Yw45 -----END PGP SIGNATURE-----

1 0