- tz - lists.iana.org

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

Time in Eucla (Western Australia)
by Robert Elz Aug. 13, 2022

Aug. 13, 2022

A friend has relatives driving towards Perth (from eastern AU). They sent him the attached photo (after I asked if they could confirm the time there as they passed through) from the local motel entrance. This is just a confirmation of what we already knew. Photo date is 13 August 2022; since it is a photo of clocks, the time is self evident (note, daylight, not near midnight). kre

1 0

[PROPOSED] Remove zoneinfo2tdf.pl
by Paul Eggert Aug. 12, 2022

Aug. 12, 2022

* Makefile (MISC, VERSION_DEPS): Remove mention of removed file. * NEWS: Mention this. * zoneinfo2tdf.pl: Remove. --- Makefile | 4 ++-- NEWS | 3 +++ zoneinfo2tdf.pl | 53 ------------------------------------------------- 3 files changed, 5 insertions(+), 55 deletions(-) delete mode 100755 zoneinfo2tdf.pl diff --git a/Makefile b/Makefile index 88240ad..ae0f3fd 100644 --- a/Makefile +++ b/Makefile @@ -538,7 +538,7 @@ DATA= $(TDATA_TO_CHECK) backzone iso3166.tab leap-seconds.list \ leapseconds $(ZONETABLES) AWK_SCRIPTS= checklinks.awk checktab.awk leapseconds.awk \ ziguard.awk zishrink.awk -MISC= $(AWK_SCRIPTS) zoneinfo2tdf.pl +MISC= $(AWK_SCRIPTS) TZS_YEAR= 2050 TZS_CUTOFF_FLAG= -c $(TZS_YEAR) TZS= to$(TZS_YEAR).tzs @@ -567,7 +567,7 @@ VERSION_DEPS= \ tzfile.5 tzfile.h tzselect.8 tzselect.ksh \ workman.sh zdump.8 zdump.c zic.8 zic.c \ ziguard.awk zishrink.awk \ - zone.tab zone1970.tab zoneinfo2tdf.pl + zone.tab zone1970.tab # And for the benefit of csh users on systems that assume the user # shell should be used to handle commands in Makefiles. . . diff --git a/NEWS b/NEWS index 9042cd8..4c1c48d 100644 --- a/NEWS +++ b/NEWS @@ -14,6 +14,9 @@ Unreleased, experimental changes Fix bug with 'zic -d /a/b/c' when /a is unwritable but the directory /a/b already exists. + The script zoneinfo2tdf.pl has been removed, as it was unused and + triggered false malware alarms on some email servers. + Release 2022b - 2022-08-10 15:38:32 -0700 diff --git a/zoneinfo2tdf.pl b/zoneinfo2tdf.pl deleted file mode 100755 index 176fce9..0000000 --- a/zoneinfo2tdf.pl +++ /dev/null @@ -1,53 +0,0 @@ -#! /usr/bin/perl -w -# Summarize .zi input in a .zi-like format. - -# Courtesy Ken Pizzini. - -use strict; - -#This file released to the public domain. - -# Note: error checking is poor; trust the output only if the input -# has been checked by zic. - -my $contZone = ''; -while (<>) { - my $origline = $_; - my @fields = (); - while (s/^\s*((?:"[^"]*"|[^\s#])+)//) { - push @fields, $1; - } - next unless @fields; - - my $type = lc($fields[0]); - if ($contZone) { - @fields >= 3 or warn "bad continuation line"; - unshift @fields, '+', $contZone; - $type = 'zone'; - } - - $contZone = ''; - if ($type eq 'zone') { - # Zone NAME STDOFF RULES/SAVE FORMAT [UNTIL] - my $nfields = @fields; - $nfields >= 5 or warn "bad zone line"; - if ($nfields > 6) { - #this splice is optional, depending on one's preference - #(one big date-time field, or componentized date and time): - splice(@fields, 5, $nfields-5, "@fields[5..$nfields-1]"); - } - $contZone = $fields[1] if @fields > 5; - } elsif ($type eq 'rule') { - # Rule NAME FROM TO - IN ON AT SAVE LETTER/S - @fields == 10 or warn "bad rule line"; - } elsif ($type eq 'link') { - # Link TARGET LINK-NAME - @fields == 3 or warn "bad link line"; - } elsif ($type eq 'leap') { - # Leap YEAR MONTH DAY HH:MM:SS CORR R/S - @fields == 7 or warn "bad leap line"; - } else { - warn "Fubar at input line $.: $origline"; - } - print join("\t", @fields), "\n"; -} -- 2.37.1

1 0

[PROPOSED] Fix bug with 'zic -d /a/b/c' if /a is unwriteable
by Paul Eggert Aug. 12, 2022

Aug. 12, 2022

If the directory /a/b already exists, it is not an error if /a is unwritable when you invoke zic -d /a/b/c. Problem found on Solaris 10, where mkdir("/a", ...) can fail with EACCES in this situation, which POSIX allows. * NEWS: Mention the fix. * private.h (ELOOP) [!ELOOP]: Define to EINVAL. * zic.c (mkdirs): Do not fail merely because mkdir fails with errno == EACCES, as the parent directory may already exist but be unwritable. For example --- NEWS | 2 ++ private.h | 3 +++ zic.c | 9 +++++++-- 3 files changed, 12 insertions(+), 2 deletions(-) diff --git a/NEWS b/NEWS index 7291030a..af99e2b7 100644 --- a/NEWS +++ b/NEWS @@ -7,6 +7,8 @@ Unreleased, experimental changes Work around a bug in macOS 'awk' that broke commands like 'make traditional_tarballs'. (Problem reported by Deborah Goldsmith.) + Fix bug with 'zic -d /a/b/c' when /a is unwritable but the + directory /a/b already exists. Release 2022b - 2022-08-10 15:38:32 -0700 diff --git a/private.h b/private.h index 9b9389f3..9c31ec54 100644 --- a/private.h +++ b/private.h @@ -168,6 +168,9 @@ # define EINVAL ERANGE #endif +#ifndef ELOOP +# define ELOOP EINVAL +#endif #ifndef ENAMETOOLONG # define ENAMETOOLONG EINVAL #endif diff --git a/zic.c b/zic.c index a29f6792..ff047937 100644 --- a/zic.c +++ b/zic.c @@ -3670,9 +3670,14 @@ mkdirs(char const *argname, bool ancestors) some other process might have made the directory in the meantime. Likewise for ENOSYS, because Solaris 10 mkdir fails with ENOSYS if the - directory is an automounted mount point. */ + directory is an automounted mount point. + Likewise for EACCES, since mkdir can fail + with EACCES merely because the parent directory + is unwritable. Likewise for most other error + numbers. */ int err = errno; - if (err != EEXIST && err != ENOSYS) { + if (err == ELOOP || err == ENAMETOOLONG + || err == ENOENT || err == ENOTDIR) { error(_("%s: Can't create directory %s: %s"), progname, name, strerror(err)); exit(EXIT_FAILURE); -- 2.34.1

1 0

Chile Timezone change
by Juan Luis Orellana Aug. 11, 2022

Aug. 11, 2022

Dear IANA Team, I'm glad I can be in touch with you, this mail has as objective, to ask for a tzdata update package, our Chilean Goverment changed the timezone change date from 09/03/23:59 to 09/10 23:59 (America/Santiago), due to political reasons. Please if you can answer me or guide me to make that change on the files, I'll apretitate that I'm struggling to correct that across from more than a thousand servers. I'll be in touch. Kind regards. Juan Luis Orellana E. +56954151809

4 4

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

Aug. 11, 2022

The 2022b release of the tz code and data is available. This release reflects the following changes: Briefly: Chile's DST is delayed by a week in September 2022. Iran no longer observes DST after 2022. Rename Europe/Kiev to Europe/Kyiv. New zic -R option Vanguard form now uses %z. Finish moving duplicate-since-1970 zones to 'backzone'. New build option PACKRATLIST New tailored_tarballs target, replacing rearguard_tarballs Changes to future timestamps Chile's 2022 DST start is delayed from September 4 to September 11. (Thanks to Juan Correa.) Iran plans to stop observing DST permanently, after it falls back on 2022-09-21. (Thanks to Ali Mirjamali.) Changes to past timestamps Finish moving to 'backzone' the location-based zones whose timestamps since 1970 are duplicates; adjust links accordingly. This change ordinarily affects only pre-1970 timestamps, and with the new PACKRATLIST option it does not affect any timestamps. In this round the affected zones are Antarctica/Vostok, Asia/Brunei, Asia/Kuala_Lumpur, Atlantic/Reykjavik, Europe/Amsterdam, Europe/Copenhagen, Europe/Luxembourg, Europe/Monaco, Europe/Oslo, Europe/Stockholm, Indian/Christmas, Indian/Cocos, Indian/Kerguelen, Indian/Mahe, Indian/Reunion, Pacific/Chuuk, Pacific/Funafuti, Pacific/Majuro, Pacific/Pohnpei, Pacific/Wake and Pacific/Wallis, and the affected links are Arctic/Longyearbyen, Atlantic/Jan_Mayen, Iceland, Pacific/Ponape, Pacific/Truk, and Pacific/Yap. From fall 1994 through fall 1995, Shanks wrote that Crimea's DST transitions were at 02:00 standard time, not at 00:00. (Thanks to Michael Deckers.) Iran adopted standard time in 1935, not 1946. In 1977 it observed DST from 03-21 23:00 to 10-20 24:00; its 1978 transitions were on 03-24 and 08-05, not 03-20 and 10-20; and its spring 1979 transition was on 05-27, not 03-21. (Thanks to Roozbeh Pournader and Francis Santoni.) Chile's observance of -04 from 1946-08-29 through 1947-03-31 was considered DST, not standard time. Santiago and environs had moved their clocks back to rejoin the rest of mainland Chile; put this change at the end of 1946-08-28. (Thanks to Michael Deckers.) Some old, small clock transitions have been removed, as people at the time did not change their clocks. This affects Asia/Hong_Kong in 1904, Asia/Ho_Chi_Minh in 1906, and Europe/Dublin in 1880. Changes to zone name Rename Europe/Kiev to Europe/Kyiv, as "Kyiv" is more common in English now. Spelling of other names in Ukraine has not yet demonstrably changed in common English practice so for now these names retain old spellings, as in other countries (e.g., Europe/Prague not "Praha", and Europe/Sofia not "Sofiya"). Changes to code zic has a new option '-R @N' to output explicit transitions < N. (Need suggested by Almaz Mingaleev.) 'zic -r @N' no longer outputs bad data when N < first transition. (Problem introduced in 2021d and reported by Peter Krefting.) zic now checks its input for NUL bytes and unterminated lines, and now supports input line lengths up to 2048 (not 512) bytes. gmtime and related code now use the abbreviation "UTC" not "GMT". POSIX is being revised to require this. When tzset and related functions set vestigial static variables like tzname, they now prefer specified timestamps to unspecified ones. (Problem reported by Almaz Mingaleev.) zic no longer complains "can't determine time zone abbreviation to use just after until time" when a transition to a new standard time occurs simultanously with the first DST fallback transition. Changes to build procedure Source data in vanguard form now uses the %z notation, introduced in release 2015f. For example, for America/Sao_Paulo vanguard form contains the zone continuation line "-3:00 Brazil %z", which is simpler and more reliable than the line "-3:00 Brazil -03/-02" used in main and rearguard forms. The plan is for the main form to use %z eventually; in the meantime maintainers of zi parsers are encouraged to test the parsers on vanguard.zi. The Makefile has a new PACKRATLIST option to select a subset of 'backzone'. For example, 'make PACKRATDATA=backzone PACKRATLIST=zone.tab' now generates TZif files identical to those of the global-tz project. The Makefile has a new tailored_tarballs target for generating special-purpose tarballs. It generalizes and replaces the rearguard_tarballs target and related targets and macros, which are now obsolescent. 'make install' now defaults LOCALTIME to Factory not GMT, which means the default abbreviation is now "-00" not "GMT". Remove the posix_packrat target, marked obsolescent in 2016a. Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2022b.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2022b.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2022b.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 b61a7acb4d267872f1c5319f30889a927b441b8f dated 2022-08-10 15:38:32 -0700 and tagged '2022b' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 851622eb8e6dc8f8201bf05e1f7e411ca32b2ed0f4dc9f6b875f4482c05c4a3302259b78c3e8e2dadda52ae19d4d34ffa3463fee10f70fa3a8b08b19f1417f79 tzcode2022b.tar.gz a51418cda50386bc2e82a26201178c282ec225e04867e70a47ef90f42371a4014c70bffebb52ac09ccd893dfa17b0acc782f31527b3579ebdc4a302a9367ddb1 tzdata2022b.tar.gz b5bd93401c9586047e865a49b9f7fd0bdf451973be24a433786633f41a1ecc2f7eacdeb78d9a906c3526bfd3b236edab72682e5bc09add42156f8dcc2497694a tzdb-2022b.tar.lz Here are the GPG digital signatures for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmL0NEoACgkQ7ZfpDmKq fjTVbw/8Cu33QgaVXIWhyQDv9gFBtGJvgVNa7IL1FP9nz1O6unqjTr57i7sameO0 aTu/v7JiCgIg5fsqqsi5yJQnYn8mZDC4MbOlqBtE237p4BwEZbvii0UWuWo/N4ep KNpbd3ezgOCYYXA+VS4azIW1LRAHhB4ZOvoUZuoRkPfoA5bR1VfZ8NRh0SfVK17R hoeRU7nlDofxHapL5zAqikGROLHhS++PVQ+x0gi5lQmDdHLtXZeiKor/y6sqb8R3 cQt8RyM6GzA9t4rsoUnMGBZIwaLYADJAmxVpBgS1EEwVfL7nx5WLur2ui+BK2GoF nN2QUG/N9TRPPFK722PiFAqoULKWamgUmRFl302TtIbygdaaKd7fxPMmgTL22REw 6qbVamP6Gk6jpG7+/FHusHB1Vz4TiTbSwK0g5UpTrps7QpoCXIU8sbScUXZzPYiY 1V2e9Fnrd2QE2+83guQhY4OX156Z32SPixl+qfK8+MMykibU6PGvCxhwHa7BzYBo X38rmsCri8vo+P27/godd6RBfsAkb8/PtB3Hlo0OGmhyggUMruVB+poip/xK8zJA bbjFB9pwi+gzkXVEkHIMuh5wgXswO+Tko7/P4ZH1t5xocc3BlrSxDvQuAVGb3hZw H3oyG5KP7sX4HCvZ42+3QTX05hFcJFgFtoncEVWAj+fPMJUm/yc= =IUf2 -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmL0NEoACgkQ7ZfpDmKq fjSfew/+P1NUMCiqlH5FlO5YyVGjc3Gxmpb6ToKsFloI7pn4KGlgQFy224VFmCVn ImSlurAuKydmZI6r+JPnjYIx0hcFUK/Wi2Y9tJKMlPDuOrexLa2toDvoXMlhBgQk RH+iaIGk8FC2mP/tdif0pzr43a87zRQiPuJ3MdoXYxEARXmc6wNtk07RS5jMlBUS G8dF2h023pTP3fD04Q77q+wUg3k5UuLw3DWrCCci1oeW/Vp+NzOsMb4vcxaWiH0M ecF0+FMpmqehJdKYZsS29D3aX8acZp3zXlAKoWHRCasCeKcltVEIyHHqdQrrR1SP R/r/OCOhIuOR3f9viPAAo56Obb63M+0siQYJmFy2Jr00lFjAzRIeajrCxSU7vxW7 6ljfdtSK8Ruv9FKrYD1Rdqa6jCpZLs6lnLk54WBStvdzJawjhZibBu3hK9LIagr/ Hb2x3H87swfId8lUZK46kjYhRYU7Jijtu+fPms5Fhrauaj2Dq56DrPyI+LyGKqBz Os0T28QUM6i67Rd0JOoMtDMesx2C/jvy9G09wwDq0mUdqg1OnfWeaUpYwCZJYdo0 Hm+zOPaxXIQph3f/MrFbrmwwggwFdjeCikOAH3uFPDp0UoHrGVq493sIGG3ulPYK 2FErRNNaeAyzniUK/35IqCQBB82GPiw6pxVf/O/HhPjLyUk55lU= =5vEv -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmL0NEsACgkQ7ZfpDmKq fjS9Yw/7BgRppySA/2mXbL+EqkGG1tmelEVx1TaHN/E2a/k1yji38Fs5+e0oHikb 95Xy2vApK5qMF0oye6nnsmtV+JquJSzwaQ4YDGLoPOtwCVNQU6WEOSlL7zfQXFsI AQy9x+yoQzevjiA+MK1Xx/s6a0G50uNZNFN1huRd4ENPPEw6qEEgLLo2qaP75uGz SM/RVIMjSTWdTdsefV1l/fIOPEqtX0S7SuldUbZh19NDLUn6vedwnO4i2qn71Guu EvZOr8RNtRpKeKOuyvLd+mKB1o4s3rUU/HlAAOcwJueNFstYH83QtrLKbjomPalI DC3E0x21Zlu3PoMsiaM+3BQknFBhx9JZI/pZz5+mUGlnjuNWTOcvxG9UGtRH+6Gr hVintjNuL2oabTuStxI7iuy+Dy6xbZ82Hs6Zy5xKuLixds/DutIfJHjLpsA3vaj+ PAkvEmPyF9zZY0C7QM3frMjqFc9vXY1114EKkVDknJ1jcOM1hszASgV/I3+j3NkN U2+++Y0fFWrWeGSm6mI5Pc2Z18OYfoIYS7q+k8fb1gzjiEWFav4U1cdm/npRca27 Mhkbbk4obVNyKGkRqpYQ40h99/Nl6uymMYx8N6zVin3tFXY23PeZnlJ6wS1yxOv1 i1g41pviERYjpp6JjBkosv5aVkxA+WKxqoWaE7x6fPXd1D3giAY= =H4rJ -----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

[Change] DST dates for Chile will change in 2022-2023
by Juan Correa Aug. 9, 2022

Aug. 9, 2022

Hello there: As of moments ago, the Internal Affairs Ministry (Ministerio del Interior) informed DST for America/Santiago will start on midnight of September 11th; and will end on April 1st, 2023. Magallanes region (America/Punta Arenas) will keep UTC -3 "indefinitely" If I recall correctly, this might alter at least the switch for 2023 This is because on September 4th we will have a voting whether to approve a new Constitution Source: https://twitter.com/min_interior/status/1556981967551209472

3 4

[PROPOSED 1/3] * theory.html: Source data can do subseconds.
by Paul Eggert Aug. 1, 2022

Aug. 1, 2022

--- theory.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/theory.html b/theory.html index bfadc4f0..2b14c511 100644 --- a/theory.html +++ b/theory.html @@ -723,8 +723,8 @@ href="https://www.dissentmagazine.org/blog/booked-a-global-history-of-time-vanes than what the <code><abbr>tz</abbr></code> code can handle. For example, from 1880 to 1916 clocks in Ireland observed Dublin Mean Time (estimated to be <abbr>UT</abbr> - −00:25:21.1), but the <code><abbr>tz</abbr></code> - code cannot represent the fractional second. + −00:25:21.1); although the <code><abbr>tz</abbr></code> + source data can represent the .1 second, TZif files and the code cannot. In practice these old specifications were rarely if ever implemented to subsecond precision. </li> -- 2.34.1

9 18

IANA timezone database - request to add Omaha, Nebraska
by Bob Wilmes Aug. 1, 2022

Aug. 1, 2022

Hello Paul Eggert, Can you please tell me how I request that Omaha, Nebraska, USA which is in the Americas Central time zone and uses daylight savings time, can be added to the "Olson" timezone database used by Ubuntu? Regards, Bob Wilmes Omaha, Nebraska bobwilmes(a)gmail.com -- Bob Wilmes bobwilmes(a)gmail.com

10 22

Re: [tz] [PROPOSED 3/3] Vanguard form now uses subsecond precision -Brooks
by Steve Allen July 31, 2022

July 31, 2022

On Sat 2022-07-30T13:24:01-0400 Brooks Harris hath writ: > On 2022-07-30 1:01 PM, Paul Eggert via tz wrote: > > Given the other comments in this thread I'm inclined to revert the > > effect of this change, so that vanguard form continues to use integer > > multiples of a second. So I installed the attached further patches, the > > last of which does the reversion. > I think that's best for civil time. But I had a thought. Steve Allen seemed > to like the idea and I'm sympathetic to his needs as astronomer. Maybe > subsecond precision could be added to "right" instead of vanguard? No, tz does not need subsecond precision, not for anyone, not in any era. The French law of 9m 21s is an example. The legislators should have known about the funds which had been expended as part of the two century effort to establish the offset between Greenwich and Paris, and that the disagreements of many 0.1 s in their own lifetimes were from the techniques employed by the astronomers, not from the telegraphs or radios. The sub-second astronomical offsets all date from before the 1970 cutoff. 1970 was when the CCIR was persuaded to assert that one second is close enough for everyone. Historically the best time comparisons had poor precision. Before the 20th century offsets were many 0.1 s or even > 1 s. In the early 20th century offsets were still many 0.01 s or even > 1 s. Attempts to reach a precision of 0.0001 s were not widespread until the International Geophysical Year of 1957/1958. Offsets of many 0.001 s persisted after the adoption of the cesium-based coordinated time because the Soviets used their own coordination scheme and other countries did not convert from UT2 to coordinated cesium time until the late 1960s. tz has rightfully eschewed the notion of trying to track local offsets recorded in Bulletin Horaire and Circular T. The legal time of the US was offset by 0.035 seconds from the BIH at 1958-01-01. The USNO and US NBS did not attempt to bring their time scales into microsecond agreement until 1968. Over a long interval in this century the legal time of Hungary was 50 microseconds different from UTC in most other places because the time lab there declined to perform a reset of their cesium. Thinking of encoding these things is a world of pain that tz does not need. -- Steve Allen <sla(a)ucolick.org> WGS-84 (GPS) UCO/Lick Observatory--ISB 260 Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 Lng -122.06015 Santa Cruz, CA 95064 https://www.ucolick.org/~sla/ Hgt +250 m

3 3

[PROPOSED] Check that ziguard substitutions revert
by Paul Eggert July 29, 2022

July 29, 2022

Add a check that substitutions to vanguard or rearguard form can be reverted. This supports possible future uses when continental files are in vanguard form and you want rearguard (or vice versa). * Makefile (check): Depend on ... (check_ziguard): ... this new target. * ziguard.awk: Fix some in_comment typos, as these column numbers do not depend on whether we’re in a comment. Use sub(X,Y) instead of $I = Y to preserve whitespace. Fix Japan and Morocco substitutions so that they are reversible. --- Makefile | 9 ++++++++- ziguard.awk | 58 ++++++++++++++++++++++++++++++++++++----------------- 2 files changed, 48 insertions(+), 19 deletions(-) diff --git a/Makefile b/Makefile index e3e5c0dd..52d7fdbe 100644 --- a/Makefile +++ b/Makefile @@ -754,7 +754,7 @@ tzselect: tzselect.ksh version check: check_character_set check_white_space check_links \ check_name_lengths check_slashed_abbrs check_sorted \ - check_tables check_web check_zishrink check_tzs + check_tables check_web check_ziguard check_zishrink check_tzs check_character_set: $(ENCHILADA) test ! '$(UTF8_LOCALE)' || \ @@ -839,6 +839,13 @@ check_theory.html check_tz-art.html check_tz-how-to.html check_tz-link.html: test ! -s $@.out || { cat $@.out; exit 1; } mv $@.out $@ +check_ziguard: rearguard.zi vanguard.zi ziguard.awk + $(AWK) -v DATAFORM=rearguard -f ziguard.awk vanguard.zi | \ + diff -u rearguard.zi - + $(AWK) -v DATAFORM=vanguard -f ziguard.awk rearguard.zi | \ + diff -u vanguard.zi - + touch $@ + # Check that zishrink.awk does not alter the data, and that ziguard.awk # preserves main-format data. check_zishrink: check_zishrink_posix check_zishrink_right diff --git a/ziguard.awk b/ziguard.awk index 171b952d..c39e0d65 100644 --- a/ziguard.awk +++ b/ziguard.awk @@ -134,8 +134,7 @@ DATAFORM != "main" { || in_comment + 3 == NF)))) if (Rule_Namibia || Zone_using_Namibia_rule) { if ((Rule_Namibia \ - ? ($(in_comment + 9) ~ /^-/ \ - || ($(in_comment + 9) == 0 && $(in_comment + 10) == "CAT")) \ + ? ($9 ~ /^-/ || ($9 == 0 && $10 == "CAT")) \ : $(in_comment + 1) == "2:00" && $(in_comment + 2) == "Namibia") \ == (DATAFORM != "rearguard")) { uncomment = in_comment @@ -219,43 +218,66 @@ DATAFORM != "main" { stdoff_column = 2 * /^Zone/ + 1 stdoff_column_val = $stdoff_column if (stdoff_column_val == stdoff_subst[0]) { - $stdoff_column = stdoff_subst[1] + sub(stdoff_subst[0], stdoff_subst[1]) if (until_subst[0] && $NF == until_subst[0]) { - $NF = until_subst[1] + sub(until_subst[0], until_subst[1]) } } else if (stdoff_column_val != stdoff_subst[1]) { stdoff_subst[0] = 0 } } - if (DATAFORM == "rearguard") { - - # In rearguard form, change the Japan rule line with "Sat>=8 25:00" - # to "Sun>=9 1:00", to cater to zic before 2007 and to older Java. - if (/^Rule/ && $2 == "Japan") { + # In rearguard form, change the Japan rule line with "Sat>=8 25:00" + # to "Sun>=9 1:00", to cater to zic before 2007 and to older Java. + if (/^Rule/ && $2 == "Japan") { + if (DATAFORM == "rearguard") { if ($7 == "Sat>=8" && $8 == "25:00") { sub(/Sat>=8/, "Sun>=9") sub(/25:00/, " 1:00") } + } else { + if ($7 == "Sun>=9" && $8 == "1:00") { + sub(/Sun>=9/, "Sat>=8") + sub(/ 1:00/, "25:00") + } } + } - # In rearguard form, change the Morocco lines with negative SAVE values - # to use positive SAVE values. - if ($2 == "Morocco") { - if (/^Rule/) { - if ($4 == 2018 && $6 == "Oct") { + # In rearguard form, change the Morocco lines with negative SAVE values + # to use positive SAVE values. + if ($2 == "Morocco") { + if (/^Rule/) { + if ($4 ~ /^201[78]$/ && $6 == "Oct") { + if (DATAFORM == "rearguard") { sub(/\t2018\t/, "\t2017\t") + } else { + sub(/\t2017\t/, "\t2018\t") } - if (2019 <= $3) { - if ($9 == "0") { + } + + if (2019 <= $3) { + if ($8 == "2:00") { + if (DATAFORM == "rearguard") { sub(/\t0\t/, "\t1:00\t") } else { + sub(/\t1:00\t/, "\t0\t") + } + } else { + if (DATAFORM == "rearguard") { sub(/\t-1:00\t/, "\t0\t") + } else { + sub(/\t0\t/, "\t-1:00\t") } } } - if ($1 == "1:00" && $3 == "+01/+00") { - sub(/1:00\tMorocco\t\+01\/\+00$/, "0:00\tMorocco\t+00/+01") + } + if ($1 ~ /^[+0-9-]/ && NF == 3) { + if (DATAFORM == "rearguard") { + sub(/1:00\tMorocco/, "0:00\tMorocco") + sub(/\t\+01\/\+00$/, "\t+00/+01") + } else { + sub(/0:00\tMorocco/, "1:00\tMorocco") + sub(/\t\+00\/+01$/, "\t+01/+00") } } } -- 2.34.1

1 0

[PROPOSED 1/2] New ‘make’ target tailored_tarballs
by Paul Eggert July 28, 2022

July 28, 2022

* Makefile (tailored_tarballs, tailored_tarballs_version) (tzdata$(VERSION)-tailored.tar.gz): New rules. (CREATE_EMPTY): New macro. (tzdata$(VERSION)-rearguard.tar.gz, tzdata$(VERSION)-vanguard.tar.gz): Use it. --- Makefile | 66 ++++++++++++++++++++++++++++++++++++++++++++------------ NEWS | 6 ++++++ 2 files changed, 58 insertions(+), 14 deletions(-) diff --git a/Makefile b/Makefile index 79910d8..65dc0d8 100644 --- a/Makefile +++ b/Makefile @@ -1039,9 +1039,9 @@ REARGUARD_ASC = \ ALL_ASC = $(TRADITIONAL_ASC) $(REARGUARD_ASC) \ tzdb-$(VERSION).tar.lz.asc -tarballs rearguard_tarballs traditional_tarballs \ +tarballs rearguard_tarballs tailored_tarballs traditional_tarballs \ signatures rearguard_signatures traditional_signatures: \ - version set-timestamps.out rearguard.zi + version set-timestamps.out rearguard.zi vanguard.zi VERSION=`cat version` && \ $(MAKE) AWK='$(AWK)' VERSION="$$VERSION" $@_version @@ -1054,6 +1054,8 @@ rearguard_tarballs_version: \ tzdata$(VERSION)-rearguard.tar.gz traditional_tarballs_version: \ tzcode$(VERSION).tar.gz tzdata$(VERSION).tar.gz +tailored_tarballs_version: \ + tzdata$(VERSION)-tailored.tar.gz signatures_version: $(ALL_ASC) rearguard_signatures_version: $(REARGUARD_ASC) traditional_signatures_version: $(TRADITIONAL_ASC) @@ -1071,30 +1073,65 @@ tzdata$(VERSION).tar.gz: set-timestamps.out gzip $(GZIPFLAGS) >$@.out mv $@.out $@ +# Create empty files with a reproducible timestamp. +CREATE_EMPTY = TZ=UTC0 touch -mt 202010122253.00 + +# The obsolescent *rearguard* targets and related macros are present +# for backwards compatibility with tz releases 2018e through 2022a. +# They should go away eventually. To build rearguard tarballs you +# can instead use 'make DATAFORM=rearguard tailored_tarballs'. tzdata$(VERSION)-rearguard.tar.gz: rearguard.zi set-timestamps.out - rm -fr tzdata$(VERSION)-rearguard.dir - mkdir tzdata$(VERSION)-rearguard.dir - ln $(COMMON) $(DATA) $(MISC) tzdata$(VERSION)-rearguard.dir - cd tzdata$(VERSION)-rearguard.dir && \ - rm -f $(TDATA) $(PACKRATDATA) version + rm -fr $@.dir + mkdir $@.dir + ln $(COMMON) $(DATA) $(MISC) $@.dir + cd $@.dir && rm -f $(TDATA) $(PACKRATDATA) version for f in $(TDATA) $(PACKRATDATA); do \ - rearf=tzdata$(VERSION)-rearguard.dir/$$f; \ + rearf=$@.dir/$$f; \ $(AWK) -v DATAFORM=rearguard -f ziguard.awk $$f >$$rearf && \ $(SET_TIMESTAMP_DEP) $$rearf ziguard.awk $$f || exit; \ done - sed '1s/$$/-rearguard/' \ - <version >tzdata$(VERSION)-rearguard.dir/version + sed '1s/$$/-rearguard/' <version >$@.dir/version : The dummy pacificnew pacifies TZUpdater 2.3.1 and earlier. - TZ=UTC0 touch -mt 202010122253.00 \ - tzdata$(VERSION)-rearguard.dir/pacificnew - touch -cmr version tzdata$(VERSION)-rearguard.dir/version + $(CREATE_EMPTY) $@.dir/pacificnew + touch -cmr version $@.dir/version LC_ALL=C && export LC_ALL && \ - (cd tzdata$(VERSION)-rearguard.dir && \ + (cd $@.dir && \ tar $(TARFLAGS) -cf - \ $(COMMON) $(DATA) $(MISC) pacificnew | \ gzip $(GZIPFLAGS)) >$@.out mv $@.out $@ +# Create a tailored tarball suitable for TZUpdater and compatible tools. +# For example, 'make DATAFORM=vanguard tailored_tarballs' makes a tarball +# useful for testing whether TZUpdater supports vanguard form. +tzdata$(VERSION)-tailored.tar.gz: set-timestamps.out + rm -fr $@.dir + mkdir $@.dir + : The dummy pacificnew pacifies TZUpdater 2.3.1 and earlier. + cd $@.dir && \ + $(CREATE_EMPTY) $(PRIMARY_YDATA) $(NDATA) backward pacificnew + (grep '^#' tzdata.zi && echo && cat $(DATAFORM).zi) \ + >$@.dir/etcetera + touch -cmr tzdata.zi $@.dir/etcetera + sed -n \ + -e '/^# *version *$.*$/h' \ + -e '/^# *ddeps */H' \ + -e '$$!d' \ + -e 'g' \ + -e 's/^# *version *//' \ + -e 's/\n# *ddeps */-/' \ + -e 's/ /-/g' \ + -e 'p' \ + <tzdata.zi >$@.dir/version + touch -cmr version $@.dir/version + LC_ALL=C && export LC_ALL && \ + (cd $@.dir && \ + tar $(TARFLAGS) -cf - \ + $(TDATA_TO_CHECK) version \ + `test $(DATAFORM) = vanguard || echo pacificnew` | \ + gzip $(GZIPFLAGS)) >$@.out + mv $@.out $@ + tzdb-$(VERSION).tar.lz: set-timestamps.out set-tzs-timestamp.out rm -fr tzdb-$(VERSION) mkdir tzdb-$(VERSION) @@ -1153,6 +1190,7 @@ zic.o: private.h tzfile.h version.h .PHONY: tarballs tarballs_version .PHONY: traditional_signatures traditional_signatures_version .PHONY: traditional_tarballs traditional_tarballs_version +.PHONY: tailored_tarballs tailored_tarballs_version .PHONY: typecheck .PHONY: zonenames zones .PHONY: $(ZDS) diff --git a/NEWS b/NEWS index 33261ee..eac1f0a 100644 --- a/NEWS +++ b/NEWS @@ -7,6 +7,7 @@ Unreleased, experimental changes Rename Europe/Kiev to Europe/Kyiv. New zic -R option Vanguard form now uses %z. + New tailored_tarballs target, replacing rearguard_tarballs Changes to future timestamps @@ -70,6 +71,11 @@ Unreleased, experimental changes to use %z eventually; in the meantime maintainers of zi parsers are encouraged to test the parsers on vanguard.zi. + The Makefile has a new tailored_tarballs target for generating + special-purpose tarballs. It generalizes and replaces the + rearguard_tarballs target and related targets and macros, which + are now obsolescent. + 'make install' now defaults LOCALTIME to Factory not GMT, which means the default abbreviation is now "-00" not "GMT". -- 2.37.1

2 2

Re: [tz] IANA timezone database - request to add Omaha, Nebraska
by Paul Eggert July 26, 2022

July 26, 2022

On 7/26/22 13:15, John Hawkinson wrote: >> If it means to enumerate only Zones and omit Links, which is what I think >> you mean, then readlink will work only if Links are implemented via symbolic >> links. Although Debian and Red Hat based systems do that, the default TZDB >> installation does not (it uses hard links), and Alpine, macOS, NetBSD, >> OpenBSD, OpenSUSE etc. use the default either because it is the default or >> because it is a bit more efficient. > You sure? > > My MacOS 12.5 laptop uses a symlink for /etc/localtime Oh, I was referring to links like these on Ubuntu 22.04: $ ls -l /usr/share/zoneinfo/Europe/Belfast lrwxrwxrwx 1 root root 6 Mar 21 11:29 /usr/share/zoneinfo/Europe/Belfast -> London I was not talking about /etc/localtime, which is a different kettle of fish. PS. Based on my misreading of a quick Google search I said in that quote above that macOS uses hard links for aliases like Europe/Belfast. However, Guy just reported[1] that current Ventura beta uses copies, just like FreeBSD does. Apologies for the error. [1] https://mm.icann.org/pipermail/tz/2022-July/031706.html

3 3

Meta engineers oppose leap seconds
by Paul Eggert July 26, 2022

July 26, 2022

Monty Solomon writes that Meta engineers Oleg Obleukhov and Ahmad Byagowi have come out against leap seconds in “It’s time to leave the leap second in the past”[1], which gives a shoutout to the leap-seconds.list file that Tim just updated in TZDB’s development version. Meta uses a 17-hour quadratic smear starting at midnight UTC, whereas Google and Amazon use a 24-hour linear smear from noon to noon UTC.[2] Obleukhov and Byagowi list several reasons leap seconds are a pain, say that the leap second is doing more harm than good (take that, scientists and astronomers!) and conclude that they “are supporting a larger community push to stop the future introduction of leap seconds”. Although I don’t see any new technical material there, their note prompted me to reread [2] and notice that Google provides an unsmear library[3] that’s worth mentioning, so I installed the attached proposed patch into the development version. [1] https://engineering.fb.com/2022/07/25/production-engineering/its-time-to-le… [2] https://developers.google.com/time/smear [3] https://github.com/google/unsmear

1 0

Leap second announcement July 2022
by Howard Hinnant July 26, 2022

July 26, 2022

https://datacenter.iers.org/data/latestVersion/16_BULLETIN_C16.txt There will be no leap second at the end of Dec. 2022. The leap second file expiration date should be updated prior to releasing 2022b. Howard

2 2

[PROPOSED] Use %z in vanguard form
by Paul Eggert July 22, 2022

July 22, 2022

* europe (Atlantic/Azores, Atlantic/Madeira): Add comments containing a vanguard equivalent. * ziguard.awk (get_minutes, offset_abbr): New functions. Support the special case for the Azores and Madeira. Convert to and from %z form. --- NEWS | 9 ++++++ europe | 12 ++++++-- ziguard.awk | 83 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 102 insertions(+), 2 deletions(-) diff --git a/NEWS b/NEWS index 4904819..33261ee 100644 --- a/NEWS +++ b/NEWS @@ -6,6 +6,7 @@ Unreleased, experimental changes Iran no longer observes DST after 2022. Rename Europe/Kiev to Europe/Kyiv. New zic -R option + Vanguard form now uses %z. Changes to future timestamps @@ -61,6 +62,14 @@ Unreleased, experimental changes Changes to build procedure + Source data in vanguard form now uses the %z notation, introduced + in release 2015f. For example, for America/Sao_Paulo vanguard + form contains the zone continuation line "-3:00 Brazil %z", which + is simpler and more reliable than the line "-3:00 Brazil -03/-02" + used in main and rearguard forms. The plan is for the main form + to use %z eventually; in the meantime maintainers of zi parsers + are encouraged to test the parsers on vanguard.zi. + 'make install' now defaults LOCALTIME to Factory not GMT, which means the default abbreviation is now "-00" not "GMT". diff --git a/europe b/europe index 0c008b4..776504d 100644 --- a/europe +++ b/europe @@ -2399,9 +2399,13 @@ Zone Europe/Lisbon -0:36:45 - LMT 1884 0:00 W-Eur WE%sT 1992 Sep 27 1:00s 1:00 EU CE%sT 1996 Mar 31 1:00u 0:00 EU WE%sT -# This Zone can be simplified once we assume zic %z. Zone Atlantic/Azores -1:42:40 - LMT 1884 # Ponta Delgada -1:54:32 - HMT 1912 Jan 1 2:00u # Horta MT +# Vanguard section, for zic and other parsers that support %z. +# -2:00 Port %z 1966 Apr 3 2:00 +# -1:00 Port %z 1983 Sep 25 1:00s +# -1:00 W-Eur %z 1992 Sep 27 1:00s +# Rearguard section, for parsers lacking %z; see ziguard.awk. -2:00 Port -02/-01 1942 Apr 25 22:00s -2:00 Port +00 1942 Aug 15 22:00s -2:00 Port -02/-01 1943 Apr 17 22:00s @@ -2413,11 +2417,14 @@ Zone Atlantic/Azores -1:42:40 - LMT 1884 # Ponta Delgada -2:00 Port -02/-01 1966 Apr 3 2:00 -1:00 Port -01/+00 1983 Sep 25 1:00s -1:00 W-Eur -01/+00 1992 Sep 27 1:00s +# End of rearguard section. 0:00 EU WE%sT 1993 Mar 28 1:00u -1:00 EU -01/+00 -# This Zone can be simplified once we assume zic %z. Zone Atlantic/Madeira -1:07:36 - LMT 1884 # Funchal -1:07:36 - FMT 1912 Jan 1 1:00u # Funchal MT +# Vanguard section, for zic and other parsers that support %z. +# -1:00 Port %z +# Rearguard section, for parsers lacking %z; see ziguard.awk. -1:00 Port -01/+00 1942 Apr 25 22:00s -1:00 Port +01 1942 Aug 15 22:00s -1:00 Port -01/+00 1943 Apr 17 22:00s @@ -2427,6 +2434,7 @@ Zone Atlantic/Madeira -1:07:36 - LMT 1884 # Funchal -1:00 Port -01/+00 1945 Apr 21 22:00s -1:00 Port +01 1945 Aug 25 22:00s -1:00 Port -01/+00 1966 Apr 3 2:00 +# End of rearguard section. 0:00 Port WE%sT 1983 Sep 25 1:00s 0:00 EU WE%sT diff --git a/ziguard.awk b/ziguard.awk index 25de617..91f6896 100644 --- a/ziguard.awk +++ b/ziguard.awk @@ -23,6 +23,33 @@ # of the input data as best it can within the constraints of the # rearguard format. +# Given a FIELD like "-0:30", return a minute count like -30. +function get_minutes(field, \ + sign, hours, minutes) +{ + sign = field ~ /^-/ ? -1 : 1 + hours = +field + if (field ~ /:/) { + minutes = field + sub(/[^:]*:/, "", minutes) + } + return 60 * hours + sign * minutes +} + +# Given an OFFSET, which is a minute count like 300 or 330, +# return a %z-style abbreviation like "+05" or "+0530". +function offset_abbr(offset, \ + hours, minutes, sign) +{ + hours = int(offset / 60) + minutes = offset % 60 + if (minutes) { + return sprintf("%+.4d", hours * 100 + minutes); + } else { + return sprintf("%+.2d", hours) + } +} + BEGIN { dataform_type["vanguard"] = 1 dataform_type["main"] = 1 @@ -85,6 +112,16 @@ DATAFORM != "main" { } } + # If this line should differ due to Portugal benefiting from %z if supported, + # uncomment the desired version and comment out the undesired one. + if (/^#?[\t ]+-[12]:00[\t ]+Port[\t ]+[%+-]/) { + if (/%z/ == (DATAFORM == "vanguard")) { + uncomment = in_comment + } else { + comment_out = !in_comment + } + } + if (uncomment) { sub(/^#/, "") } @@ -92,6 +129,52 @@ DATAFORM != "main" { sub(/^/, "#") } + # Prefer %z in vanguard form, explicit abbreviations otherwise. + if (DATAFORM == "vanguard") { + sub(/^(Zone[\t ]+[^\t ]+)?[\t ]+[^\t ]+[\t ]+[^\t ]+[\t ]+[-+][^\t ]+/, \ + "&CHANGE-TO-%z") + sub(/-00CHANGE-TO-%z/, "-00") + sub(/[-+][^\t ]+CHANGE-TO-/, "") + } else { + if (/^[^#]*%z/) { + stdoff_column = 2 * /^Zone/ + 1 + rules_column = stdoff_column + 1 + stdoff = get_minutes($stdoff_column) + rules = $rules_column + stdabbr = offset_abbr(stdoff) + if (rules == "-") { + abbr = stdabbr + } else { + dstabbr_only = rules ~ /^[+0-9-]/ + if (dstabbr_only) { + dstoff = get_minutes(rules) + } else { + # The DST offset is normally an hour, but there are special cases. + if (rules == "Morocco" && NF == 3) { + dstoff = -60 + } else if (rules == "NBorneo") { + dstoff = 20 + } else if (((rules == "Cook" || rules == "LH") && NF == 3) \ + || (rules == "Uruguay" \ + && /[\t ](1942 Dec 14|1960|1970|1974 Dec 22)$/)) { + dstoff = 30 + } else if (rules == "Uruguay" && /[\t ]1974 Mar 10$/) { + dstoff = 90 + } else { + dstoff = 60 + } + } + dstabbr = offset_abbr(stdoff + dstoff) + if (dstabbr_only) { + abbr = dstabbr + } else { + abbr = stdabbr "/" dstabbr + } + } + sub(/%z/, abbr) + } + } + if (DATAFORM == "rearguard") { # In rearguard form, change the Japan rule line with "Sat>=8 25:00" -- 2.36.1

1 0

[PATCH] * europe: Fix a few more "Kiev"s in comments.
by Paul Eggert July 21, 2022

July 21, 2022

--- europe | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/europe b/europe index 55217a1..0c008b4 100644 --- a/europe +++ b/europe @@ -2845,18 +2845,18 @@ Zone Europe/Simferopol 2:16:24 - LMT 1880 2:00 - EET 1992 Mar 20 # Central Crimea used Moscow time 1994/1997. # -# From Paul Eggert (2022-04-18): -# The _Economist_ (1994-05-28, p 45) reports that central Crimea switched -# from Kiev to Moscow time sometime after the January 1994 elections. +# From Paul Eggert (2022-07-21): +# The _Economist_ (1994-05-28, p 45) reported that central Crimea switched +# from Kyiv to Moscow time sometime after the January 1994 elections. # Shanks (1999) says "date of change uncertain", but implies that it happened # sometime between the 1994 DST switches. Shanks & Pottenger simply say # 1994-09-25 03:00, but that can't be right. For now, guess it # changed in May. This change evidently didn't last long; see below. 2:00 C-Eur EE%sT 1994 May -# From IATA SSIM (1994/1997), which also says that Kerch is still like Kiev. +# From IATA SSIM (1994/1997), which also said that Kerch is still like Kyiv. 3:00 C-Eur MSK/MSD 1996 Mar 31 0:00s 3:00 1:00 MSD 1996 Oct 27 3:00s -# IATA SSIM (1997-09) says Crimea switched to EET/EEST. +# IATA SSIM (1997-09) said Crimea switched to EET/EEST. # Assume it happened in March by not changing the clocks. 3:00 - MSK 1997 Mar lastSun 1:00u # From Alexander Krivenyshev (2014-03-17): @@ -4078,7 +4078,7 @@ Link Europe/Istanbul Asia/Istanbul # Istanbul is in both continents. # The law documents themselves are at # http://w1.c1.rada.gov.ua/pls/zweb_n/webproc4_1?id=&pf3511=41484 -# From Vladimir in Moscow via Alois Treindl re Kiev time 1991/2 (2014-02-28): +# From Vladimir in Moscow via Alois Treindl re Kyiv time 1991/2 (2014-02-28): # First in Ukraine they changed Time zone from UTC+3 to UTC+2 with DST: # 03 25 1990 02:00 -03.00 1 Time Zone 3 with DST # 07 01 1990 02:00 -02.00 1 Time Zone 2 with DST -- 2.36.1

1 0