- tz - lists.iana.org

file "zoneinfo2tdf.pl" is missing from latest release 2022c!
by chris＠gensler-it-support.de Aug. 19, 2022

Aug. 19, 2022

Maybe that's intended, but it disappeared without notice. Chris

2 1

Add option to act like global-tz
by Paul Eggert Aug. 18, 2022

Aug. 18, 2022

I wangled a bit of free time and wrote the attached proposed patch, which adds an option that causes 'make install' to generate time zone data (TZif files) that are byte-for-byte identical to what Stephen Colebourne's global-tz currently generates. This is done via a few lines of awk script. The idea is to give an option to distros that prefer a separate Zone per ISO 3166 country, just as we already have build-time options for rearguard/vanguard form, TZif truncation, leap seconds, etc. I haven't installed this in the development database. Comments welcome as usual.

5 22

time_t truncation occurrence in tzcode
by Jan Engelhardt Aug. 18, 2022

Aug. 18, 2022

Due to an update of the Coverity Scan analyzer itself, it has identified a new issue in timezone code. In version 2022c (the excerpt is copypasted from an own project, so line numbers don't mean much), it has flagged: <<< 1757 while (year_lengths[isleap(y)] <= idays) { 1758 int tdelta = idays / DAYSPERLYEAR; 1759 int_fast32_t ydelta = tdelta + !tdelta; 1760 time_t newy = y + ydelta; 1761 register int leapdays; 1762 leapdays = leaps_thru_end_of(newy - 1) - 1763 leaps_thru_end_of(y - 1); 1764 idays -= ydelta * DAYSPERNYEAR; 1765 idays -= leapdays; 1766 y = newy; 1767 } 1768 1769 if (!TYPE_SIGNED(time_t) && y < TM_YEAR_BASE) { CID 1491244 (#1 of 1): Use of 32-bit time_t (Y2K38_SAFETY) 1. store_truncates_time_t: A time_t value is stored in an integer with too few bits to accommodate it. The expression y is cast to int. 1770 int signed_y = y; ^^^^^^^^^^^^ 1771 tmp->tm_year = signed_y - TM_YEAR_BASE; 1772 } else if ((!TYPE_SIGNED(time_t) || INT_MIN + TM_YEAR_BASE <= y) 1773 && y - TM_YEAR_BASE <= INT_MAX) 1774 tmp->tm_year = y - TM_YEAR_BASE; 1775 else { 1776 errno = EOVERFLOW; 1777 return NULL; 1778 } 1779 tmp->tm_yday = idays; >>> On e.g. x86_64-linux-gnu, time_t is 64 bits (signed) wide, and while the specific code path is not executed on that particular platform, the warning about a truncation to a 32-bit signed int seems justified.

3 2

Official Chilean Goverment Decret for timezone changes 2022-2026
by Eduardo Romero Urra Aug. 18, 2022

Aug. 18, 2022

Dear Paul, I've send a copy of presidential decret for Summer time changes for the Republic of Chile, officially published at August 13th 2022: https://www.diariooficial.interior.gob.cl/publicaciones/2022/08/13/43327/01… I've review your update 2022b TZdata and it's ok for this year where the summer time starts the second saturday of September ( Sep 10th at midnight), but the next years ( 2023 to 2026 ) is need to precise that the summer time event affects only for this year according to avoid problem confusions to a Votation Day schedule to the next sunday Sept 4th (the original summer time change was schedule at Saturday Sep 3th midnight). Also consider this also affects to Easter Island Time Zone (Pacific/Easter) and not affects to Chile/Punta_Arenas Time Zone. At resume (page #2 of document): 2022: - Chile/Continental ( America/Santiago ): Summer time starts at Saturday 10th Sep. at 24:00 Hrs, adding 1hour ( GMT -03) - Chile/Easter (Pacific/Easter) : Summer time starts at Saturday 10th Sep. at 22:00 Hrs, adding 1hour ( GMT -05) - Chile/Punta_Arenas (America/Punta_Arenas): No changes, keeps on GMT -03 2023-2025 - Chile/Continental ( America/Santiago ): Summer time ends at first saturday of Abril 24:00 Hrs, backward 1hour ( GMT -04) , and Summer time starts the first saturday of September at 24:00 , adding 1hour ( GMT -03) - Chile/Easter (Pacific/Easter) : Summer time ends at first saturday of Abril at 22:00 Hrs, backward 1hour ( GMT -06), and Summer time starts the first saturday of September at 24:00 , adding 1hour ( GMT -05) - Chile/Punta_Arenas (America/Punta_Arenas): No changes , keeps on GMT -03 2026: - Chile/Continental ( America/Santiago ): Summer time ends at first saturday of Abril 24:00 Hrs, backward 1hour ( GMT -04) - Chile/Easter (Pacific/Easter) : Summer time ends at first saturday of Abril at 22:00 Hrs, backward 1hour ( GMT -06) (the decret has no mentions for future time changes plans) - Chile/Punta_Arenas (America/Punta_Arenas): No changes , keeps on GMT -03 I've check the rules on southamerica file , but i'm not sure if apply correctly for Easter Island changes Rule Chile 2019 max - Apr Sun>=2 3:00u 0 - Rule Chile 2019 2021 - Sep Sun>=2 4:00u 1:00 - Rule Chile 2022 only - Sep Sun>=9 4:00u 1:00 - Rule Chile 2023 max - Sep Sun>=2 4:00u 1:00 - [...] Zone Pacific/Easter -7:17:28 - LMT 1890 -7:17:28 - EMT 1932 Sep # Easter Mean Time -7:00 Chile -07/-06 1982 Mar 14 3:00u # Easter Time -6:00 Chile -06/-05 I'm very appreciated your assistance for this changes. Thanks in Advance. ━━━━━━━━ Eduardo Romero Urra Asesor de Sistemas División de Redes y Seguridad Informática +56224863218 Ministerio del Interior y Seguridad Pública Gobierno de Chile CONFIDENCIALIDAD Y USO EXCLUSIVO: La información contenida en este mensaje y/o en los archivos adjuntos son de carácter confidencial y está destinada al uso exclusivo del emisor y/o de la persona o entidad a quien va dirigida, y por lo mismo pueden ser consultados y revisados por la entidad emisora o propietaria de los sistemas desde donde fueron enviados.- Si usted no es el destinatario, cualquier almacenamiento, divulgación, distribución o copia de esta información está estrictamente prohibida y sancionada por la ley. Si recibió este mensaje por error, por favor infórmenos inmediatamente respondiendo este mismo mensaje y borre éste y todos los archivos adjuntos. Considerando que no existe certidumbre de que el presente mensaje no será modificado como resultado de su transmisión por correo electrónico, el emisor original no será responsable si el contenido del mismo ha sido modificado. Ministerio del Interior y Seguridad Publica<https://www.interior.gob.cl>

3 3

Re: [tz] tzdata 2022b and 2022c location
by Paul Eggert Aug. 17, 2022

Aug. 17, 2022

On 8/16/22 01:07, Alex Goldberg3 wrote: > We usually get tzdata files from https://github.com/unicode-org/icu-data/tree/main/tzdata/icunew , where metaZones.res, timezoneTypes.res, etc are located. However, the latest release there is 2022a. Are 2022b and 2022c not officially released or may be changed location? I suspect that you're talking about ICU's files concerning time zones as opposed to the tzdata files themselves, as the repository you mention stopped mirroring tzdata files after tzdata 2011k. ICU is downstream from tzdata and an ICU forum would be a good place to ask about ICU's status. A request for ICU to update to match tzdata 2022b (and 2022c) is here: https://unicode-org.atlassian.net/browse/ICU-22118 and I expect you can monitor and/or comment there. Currently nobody is assigned to the task.

1 0

[tz-announce] 2022c release of tz code and data available
by Paul Eggert via tz-announce Aug. 16, 2022

Aug. 16, 2022

The 2022c release of the tz code and data is available. This release reflects the following changes, which do not affect timestamps unless your system has the awk bug mentioned below: Briefly: Work around awk bug in FreeBSD, macOS, etc. Improve tzselect on intercontinental Zones. Changes to code Work around a bug in onetrueawk that broke commands like 'make traditional_tarballs' on FreeBSD, macOS, etc. (Problem reported by Deborah Goldsmith.) Add code to tzselect that uses experimental structured comments in zone1970.tab to clarify whether Zones like Africa/Abidjan and Europe/Istanbul cross continent or ocean boundaries. (Inspired by a problem reported by Peter Krefting.) Fix bug with 'zic -d /a/b/c' when /a is unwritable but the directory /a/b already exists. Remove zoneinfo2tdf.pl, as it was unused and triggered false malware alarms on some email servers. Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2022c.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2022c.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2022c.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 ce4d77644d2793027bb27f095dec7b530edcd947 dated 2022-08-15 17:47:18 -0700 and tagged '2022c' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 3373fa16a12007415c3dc3a75c4a0d61d6ae54968eeecedcdf4bcfd7f554020a15c4687dde107b90462b75d848eebe1e200c33322ebe0d3f1ad11bc769cade06 tzcode2022c.tar.gz e2ae92abac6d87ce4ab4ba9012e868e1791b842e083293489debc0c671b9cf135b5b70426dacb6dbebbf6eba24463205225ae45bb7df891a086b25475f85ee0b tzdata2022c.tar.gz e51a9044da116a52906bc0fc22a3dde0e1a6d4e486f9e610a63aa6634ccc1ebd0bc2d47d2faa84bde2b78cc890fe3fb08f6c1ac4e1e0c147d45de5c21d26b26a tzdb-2022c.tar.lz Here are the GPG digital signatures for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmL66eQACgkQ7ZfpDmKq fjSarBAAp6iKJluMo3MOD4YQUwB5aUsVg1zSXPYs1WH88gXaHLxm2G0fv8Ar4FFg gDOBxyazc/4fB7zwec3rMKo5KVV/pRil1go93BetefoU1ffhrLYbrVw89/VsesXP nQ5FXkVLd/u5vuOXf2WoS+hmJANlC2ljhHTN1MX0hoChyLA/paBYvS18mTn45Tm4 PCH6cPKX//gwGSmOavRqlT9wp95NCpCeXX7Yl5aYIgpdGAJAGZJrzGcn1Rp0NoOJ BQfoaC4SuGEeBbqsUdoFrXE6V1rI1pAvPXq8fwTjrh7LDIaGmIHY+HAeJUDwT4d5 rEXNJ9D5mun4VDkVMiyMlITTletu1wnHyspLZk4h9g6H75C2c0pipCI4FGfEn+wh 2l54bVAwJE2An5UKdqukaC2B9MGxEFTbgE5Za93OwOyrb6FFGUrMjj2Ua1nf1h6E 5VefqyKepF1TY/ApWy2OObTioBew2lVuXRsQrD1cDo/rqAyMYLlkrye0nQspvkAA jv5LKH8fmapBee7JaFYYbnCMZwpyr0iP4LOiH34a9vsFrUtERUTUKxhPv1epNyyc F6ECJz7wknYwRszyp/2ai7nc8yCHc+76dmgXM6fPwcghuVv0ihl7uOkNx1Rp2MHr oZ7r0KV7HcAOQgCWJuh4l1QNX3qX7XqmRJP1rNCmMbUnENme6MQ= =7xd7 -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmL66eQACgkQ7ZfpDmKq fjTHhQ//YaTZjsHEvJuVFRcqjuIByGySv7aUnvldFGZ4vuAgIX0g7hlaoCdSlVri qjqhGSM7ShcRs1PtvBGUmFrrfvhg+vW6D6etkf3GO8h/Vztz26GIkY/PLv/wFu4i bf915wfbsMmaoI/MVlLsNMzQ63qS5i+JwouJAKOmUb95wNMrmKlBi4XXcQNvUdTF pp7uGq7jJdcETAgH5UQkeiXBghahdS6SEK8raFplW2hK8SqyAAjG9hRBjMqyoSUS cPK0UwrjLZvd9KOB73RFryglkNpTthqvsr4vZ7K4WzZuIYxHLzG2LEG6Rhuuq8Z/ 2u3g4KMLJ29NQJRIjAYWU9F2IruzgQJjxRjMtbxysR7Jiru+xzg5nha1eRdp/G4z F9aqc2NR79I9kpUQAIxhi3C6v/mreMNm0HfBskA3Ws1R7Mi7MSpnIhi/gwUUnQV2 AMBOo2qAz24d3kt65Opc2bHWZemtfzXTkMQhIiIgCkHrb5H9EKUYac+aJeJpRZKU jdZ/5rLzKJyUraBb1a0h6UXCuxk0yVelVIcDEjaJTfpgMF5qmwrFaCBZUZ0zbQvT 9VhltgpkWGGUMJxn+OTyGsZRO8oUXg/3SbaMQr0tAnR59tcorvhF5wU5aNH/PYoa dDwW+qmDW3ky10DiF2fzjZWwRBiiLJF61stHXaNy9RvHC/V3yFY= =nylY -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmL66eYACgkQ7ZfpDmKq fjS8Dg//fnZzYIPMv90un2mPyAnVZbVSS6O8CG2YSdHPkXwVZE8DbyrIVNaJTLNG zaGgQ0/+enf3HZlM8NTBJO6Zf4Sv1ZFrnifqF0JmUZ5P/OxlhKLdt3OgQ0oGAX48 SacJoXf3JX8At10Ar+NVtAneJpG1wVsD4nPFrNS/rWRwfMMKdnP2HxlEVHCbNikk r1/F+065qbXYOhYD3UpqJI9dKaA3OFjEANQJJHw3+h7m0YZFcMATSw5anrnvGotx +lgQffLQvKIKc5E7CsppEk0SnFmKncUceepajJzqnyNTT9kecSAlu6qrnJCgHtu+ qhQfMfklixqocCwj6yJyZDKuv9e8vKjb7U2HYhNRhBWS3eE4ozE6fDDacehRyUrz HLgotpRuYWImP3MA+AhOqSQThY2y3tSOHAKxMDixaq4dkpXGgg+5KR/VRLD8//99 m19yu3QqpzjKGPiQpfdU5tpk/2JegFpCbYwsMkw0XfCVvmRwjKGexS3hIHLF4WkQ XMjkf8Bj+AS0Ld+9IBE97BrG6qDN+NPI9EhC7/YvyxqcDcSWbG65JbiYkyDUkBgt rUFPTlUUTD2hcdfbQQZ4f23F/iJpbJXOyhqxxHl9RnkJkEkgDcO+apps74V4IN/6 YSP3pvW32hZ0Z8iXKD4VVbYBqIw6rLb8HpaA5zQEHs/S2A/kcfs= =BW2X -----END PGP SIGNATURE----- PS. If your tzdata parser does not yet support negative DST offsets or times past 24:00, or if it insists on a 'pacificnew' file that is no longer present, this release's data entries can be turned into a rearguard-format tarball that should work even with these older parsers. This is intended to be a temporary transition aid for these parsers. To generate a rearguard-format tarball, obtain the full distribution as described above, and run the command 'make DATAFORM=rearguard tailored_tarballs' on a development host. Or you can run 'make rearguard.zi' to generate a single file that can be fed directly to a parser that works like 'zic'.

1 0

[PROPOSED 1/2] Prefer " to ' in HTML attributes
by Paul Eggert Aug. 15, 2022

Aug. 15, 2022

--- tz-art.html | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/tz-art.html b/tz-art.html index 73be9f9c..f1bd4c57 100644 --- a/tz-art.html +++ b/tz-art.html @@ -483,19 +483,19 @@ Supernaw.</td></tr> <ul> <li> The webcomic xkcd has the strip -"<a href='https://xkcd.com/673/'>The Sun</a>" (2009-12-09) and the panels -"<a href='https://xkcd.com/1017/'>Backward in Time</a>" (2012-02-14), -"<a href='https://xkcd.com/1061/'>EST</a>" (2012-05-28), -"<a href='https://xkcd.com/1179/'>ISO 8601</a>" (2013-02-27), -"<a href='https://xkcd.com/1335/'>Now</a>" (2014-02-26), -"<a href='https://xkcd.com/1655/'>Doomsday Clock</a>" (2016-03-14), -"<a href='https://xkcd.com/1799/'>Bad Map Projection: Time Zones</a>" +"<a href="https://xkcd.com/673/">The Sun</a>" (2009-12-09) and the panels +"<a href="https://xkcd.com/1017/">Backward in Time</a>" (2012-02-14), +"<a href="https://xkcd.com/1061/">EST</a>" (2012-05-28), +"<a href="https://xkcd.com/1179/">ISO 8601</a>" (2013-02-27), +"<a href="https://xkcd.com/1335/">Now</a>" (2014-02-26), +"<a href="https://xkcd.com/1655/">Doomsday Clock</a>" (2016-03-14), +"<a href="https://xkcd.com/1799/">Bad Map Projection: Time Zones</a>" (2017-02-15), -"<a href='https://xkcd.com/1883/'>Supervillain Plan</a>" (2017-08-30), -"<a href='https://xkcd.com/2050/'>6/6 Time</a>" (2018-09-24), -and "<a href='https://xkcd.com/2266/'>Leap Smearing</a>" (2020-02-10). +"<a href="https://xkcd.com/1883/">Supervillain Plan</a>" (2017-08-30), +"<a href="https://xkcd.com/2050/">6/6 Time</a>" (2018-09-24), +and "<a href="https://xkcd.com/2266/">Leap Smearing</a>" (2020-02-10). The related book What If? has an entry -"<a href='https://what-if.xkcd.com/26/'>Leap Seconds</a>" (2012-12-31). +"<a href="https://what-if.xkcd.com/26/">Leap Seconds</a>" (2012-12-31). </li> <li> Pig kills time in <a @@ -504,11 +504,11 @@ Before Swine (2016-11-06)</a>. </li> <li> Stonehenge is abandoned in <a -href='https://www.gocomics.com/nonsequitur/2017/03/12'>Non Sequitur +href="https://www.gocomics.com/nonsequitur/2017/03/12">Non Sequitur (2017-03-12)</a>. <li> The boss freaks out in <a -href='https://dilbert.com/strip/1998-03-14'>Dilbert (1998-03-14)</a>. +href="https://dilbert.com/strip/1998-03-14">Dilbert (1998-03-14)</a>. </li> <li> Peppermint Patty: "What if the world comes to an end tonight, Marcie?" @@ -516,7 +516,7 @@ Peppermint Patty: "What if the world comes to an end tonight, Marcie?" Marcie: "I promise there'll be a tomorrow, sir ... in fact, it's already tomorrow in Australia!" -(Charles M. Schulz, <a href='https://www.gocomics.com/peanuts/1980/06/13'>Peanuts, 1980-06-13</a>) +(Charles M. Schulz, <a href="https://www.gocomics.com/peanuts/1980/06/13">Peanuts, 1980-06-13</a>) </li> </ul> <h2>Jokes</h2> -- 2.34.1

1 1

Re: [tz] Trivial questions about Tz
by dpatte Aug. 15, 2022

Aug. 15, 2022

Thanks Paul It is theoretically possible that such a triple midnight could happen, but I assume it could happen only if some goverment/administration had poorly chosen their walltime transition times. ----- Original Message ----- From: Paul Eggert [mailto:eggert@cs.ucla.edu] To: "dpatte" <dpatte(a)relativedata.com> Cc: tz(a)iana.org Sent: Mon, 15 Aug 2022 15:46:55 -0700 Subject: Re: [tz] Trivial questions about Tz On 8/15/22 14:23, dpatte via tz wrote: > Are there any known cases in the tz database where two close offset and save changes in one region cause wall times in that region to have not just one but two repeats of the original wall times, such as 3 midnights with the same date? I dimly recall we used to have examples of that but eventually removed them from TZDB since they were surely mistakes. Quite possibly my memory is incorrect. > I am also curious what the largest single change to a save-time is in the database, and the largest single change to a GMT offset-time (though I assume the answer to this second one is Western Samoa). The following shell command: zdump -i $(awk '/^Zone/{print $2}' main.zi) | awk 'o!="" && $3!="" && o!=$3 {print o, $3} {o = $3}' | sort -u prints output that should help answer your question. Each line of output is a distinct pair of (before, after) %z-style abbreviations that is observed somewhere in tzdb. I get 579 lines of output with current tzdb.

1 0

Trivial questions about Tz
by dpatte Aug. 15, 2022

Aug. 15, 2022

I was just curious... Generally, when a region comes off Daylight/Summer time, the wall time is set back, causing a wall clock to repeat a portion of wall times (albeit with a different time abbreviation). Likewise, if a region elects a new GMT offset that is further west than before, the wall time is also set back, also causing a repeat of wall times (again with a different time abbreviation). Are there any known cases in the tz database where two close offset and save changes in one region cause wall times in that region to have not just one but two repeats of the original wall times, such as 3 midnights with the same date? I am also curious what the largest single change to a save-time is in the database, and the largest single change to a GMT offset-time (though I assume the answer to this second one is Western Samoa).

3 2

make traditional_tarballs fails on macOS for 2022b
by Deborah Goldsmith Aug. 15, 2022

Aug. 15, 2022

This is a regression from 2022a. This is on macOS 13.0 but I suspect it will fail the same way on macOS 12. Also note that macOS does not have nroff installed, but that doesn’t look like a fatal error. Debbie debbie 6:11PM tz ✓ % make traditional_tarballs { (type git) >/dev/null 2>&1 && \ V=`git describe --match '[0-9][0-9][0-9][0-9][a-z]*' \ --abbrev=7 --dirty` || \ if test 'unknown' = unknown && V=`cat version`; then \ case $V in *-dirty);; *) V=$V-dirty;; esac; \ else \ V='unknown'; \ fi; } && \ printf '%s\n' "$V" >version.out mv version.out version awk -v EXPIRES_LINE=0 \ -f leapseconds.awk leap-seconds.list >leapseconds.out mv leapseconds.out leapseconds LC_ALL=C sh workman.sh `expr tzselect.8.txt : '$.*$\.txt$'` >tzselect.8.txt.out workman.sh: line 16: nroff: command not found mv tzselect.8.txt.out tzselect.8.txt LC_ALL=C sh workman.sh `expr zic.8.txt : '$.*$\.txt$'` >zic.8.txt.out workman.sh: line 16: nroff: command not found mv zic.8.txt.out zic.8.txt awk \ -v DATAFORM=`expr main.zi : '$.*$.zi'` \ -v PACKRATDATA='' \ -v PACKRATLIST='' \ -f ziguard.awk \ africa antarctica asia australasia europe northamerica southamerica etcetera factory backward >main.zi.out awk: syntax error at source line 110 source file ziguard.awk context is stdoff_column = 2 * /^Zone/ >>> + <<< 1 awk: illegal statement at source line 110 source file ziguard.awk awk: illegal statement at source line 110 source file ziguard.awk make: *** [main.zi] Error 2

4 26