- tz - lists.iana.org

Chile's Aysén Region polled about switching from -04/-03 to -03 all year
by Paul Eggert March 20, 2025

March 20, 2025

Beginning this week and continuing through the end of the month, the citizens of Chile's Aysén Region are being polled virtually for a non-binding resolution[1] to switch from the their current timekeeping regime TZ="America/Santiago" (-04 in winter, -03 in summer) to permanent -03 (like TZ="America/Punta_Arenas"). If this happens, we'll need to create a new Zone America/Coyhaique to record the change, which would likely have practical effect on 2025-04-05 at the earliest. Unfortunately, the SurveyMonkey form used for the poll requires no authentication, which raised plausible worries this week about ballot-stuffing[2]. [1]: https://www.diarioregionalaysen.cl/noticia/actualidad/2024/11/lanzan-consul… [2]: https://www.diarioregionalaysen.cl/noticia/actualidad/2024/11/encuesta-sobr…

3 4

Iran's transition from +04:00 to +03:30 in 1978
by Roozbeh Pournader March 18, 2025

March 18, 2025

I hunted down the exact time of Iran's transition from +0400 to +0330. It was Friday 1357/8/19 AP=1978-11-10. Here's a newspaper clip from the Ettela'at newspaper, dated 1357/8/14 AP=1978-11-05, translated from Persian (at https://w.wiki/DUEY) "Following the government's decision about returning the official time to the previous status, the spokesperson for the Ministry of Energy announced today: At the hour 24 of Friday 19th of Aban (=1978-11-10), the country's time will be pulled back half an hour. In this way, the country's official time which in the last thirty months had been moved forward by about an hour and a half will return to its previous status." I will double-check the various other transition times for 1977 to 1980, but at the first glance they are either correct or may only be off by at most a day or two. Thanks a lot, Roozbeh

2 2

Leave
by Javier Esquivel Téllez March 18, 2025

March 18, 2025

leave *La información contenida en este correo electrónico y sus documentos adjuntos es confidencial y privilegiada y para el uso único y exclusivo del destinatario, por lo que queda estrictamente prohibido el uso, reproducción, retransmisión o divulgación no autorizada de su contenido. Si recibió este mensaje por error, por favor notifíquelo al remitente y bórrelo junto con sus documentos adjuntos de inmediato.* *SAFTU TECNOLOGIAS, S.A.P.I. de C.V. (SAFTU) es el responsable del uso y protección de sus datos personales. Cualquier dato personal o sensible recibido o enviado libre y voluntariamente por su titular en el presente correo se protegerá de acuerdo al aviso y políticas de privacidad de SAFTU, y será tratado para los fines descritos en el mismo, incluyendo para organizar bases de datos, prestarle los servicios o información solicitada, y mantener la comunicación. Si usted es titular de datos personales en posesión de SAFTU, y desea obtener más información sobre los términos y condiciones en que serán tratados y la forma en que podrá ejercer sus derechos ARCO, puede consultar nuestro aviso de privacidad integral en www.saftu.com <http://www.saftu.com/>*

1 0

Dump of Asia/Tehran changes?
by Roozbeh Pournader March 18, 2025

March 18, 2025

Can someone please kindly give me a dump of Asia/Tehran changes according to the latest tzdata for the years 1977-1981? I'm trying to piece together the newspaper bits and pieces and compare with the tz database, and it seems that there is clearly some transitions missing. Specifically, I find the following lines confusing: 4:00 Iran %z 1979 3:30 Iran %z Does that mean we think Iran switched from UTC+4:00 to UTC+3:30 on Jan 1, 1979? Thanks a lot, Roozbeh

3 3

[PROPOSED] Cite Neumann & von Blanckenburg’s 2025 DST review
by Paul Eggert March 15, 2025

March 15, 2025

* tz-link.html (Costs and benefits of time shifts): Add citation and brief summary. --- tz-link.html | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/tz-link.html b/tz-link.html index f4f76fdd..ad2cc972 100644 --- a/tz-link.html +++ b/tz-link.html @@ -985,6 +985,14 @@ a Sleep Research Society position statement</a>. doi:<a href="https://doi.org/10.1093/sleep/zsac236">10.1093/sleep/zsac236</a>. After reviewing the scientific literature, the Sleep Research Society advocates permanent standard time due to its health benefits. +<li>Neumann P, von Blanckenburg K. <a +href="https://journals.sagepub.com/doi/full/10.1177/0961463X241310562">What +time will it be? A comprehensive literature review on daylight saving time</a>. +<em>Time Soc</em>. 2025-01-21. +doi:<a href="https://doi.org/10.1177/0961463X241310562">10.1177/0961463X241310562</a>. +This reviews DST's effects on electricity, health, crime, road safety, +and the economy, focusing on research since 2010, and concludes that +year-round standard time is preferable overall. <li>Rishi MA, Cheng JY, Strang AR <em>et al</em>. <a href="https://jcsm.aasm.org/doi/10.5664/jcsm.10898">Permanent standard time is the optimal choice for health and safety: -- 2.45.2

1 0

false story re canceling DST in Canaries and Spain
by Paul Eggert March 15, 2025

March 15, 2025

Last week saw a widely spread false story that daylight saving time will be canceled in Spain and in the Canary Islands, starting in the year 2026. The story was reported as fact in the Daily Mirror[1], which evidently got it from the Canarian Weekly[2]. Both stories said that the last clock change would be this month (implying permanent daylight saving time), that the change would officially take place in 2026 (contradicting the last-clock-change assertion), and that this had been confirmed by the Official State Gazette (BOE), i.e., Spain's Boletín Oficial del Estado. As Gazette Life noted Thursday[3], the story is false. There is no change to Spain's timekeeping plans. I guess the bogus story is based on a misreading of Order PCM/186/2022 dated 2022-03-11[4], which listed DST transitions for 2022 through 2026. A copy of this old order was recently marked as updated by BOE (I don't know why), and my guess is that the "new" order popped up on some reporter's AI, which generated the hallucination that Spain was discontinuing DST. This reminds me of the 2023 false story about Greenland abolishing DST that was first published, as far as I can determine[5], by Bloomberg's Lebawit Lily Girma. Although I had an email correspondence about that bogus story with two Bloomberg editors, the bogus story was never corrected or retracted. I expect the same thing would happen with the Daily Mail and the Canarian Weekly, so I am not bothering to write them. We can expect more of these falsehoods in the era of generative AI, which makes it easier to write bogus stories that superficially look authentic. I am seeing considerably more use of generative AI even in scholarly papers on the subject. [1]: Bautista A. Huge EU country loved by Brits will stop changing clocks in 2026. The Mirror. 2025-03-11. https://www.mirror.co.uk/travel/huge-eu-country-loved-brits-34832825 [2]: The Canary Islands are set to abandon clock changes from 2026. Canarian Weekly. 2025-03-09. https://www.canarianweekly.com/posts/The-Canary-Islands-are-set-to-abandon-… [3]: No change on clocks for Spain and Canaries. Gazette Life. 2025-03-13. https://gazettelife.com/news/no-change-on-clocks-for-spain-and-canaries/ [4]: Orden PCM/186/2022, de 11 de marzo, por la que se publica el calendario del período de la hora de verano correspondiente a los años 2022 a 2026. https://www.boe.es/eli/es/o/2022/03/11/pcm186 [5]: Eggert P. Did Greenland abolish daylight saving from 2024 on? https://mm.icann.org/pipermail/tz/2023-April/032870.html

1 0

Ireland Time Zone
by Chris Brown March 11, 2025

March 11, 2025

Hello, We received a notification from a customer that the Ireland Time Zones sprung forward too early. According to what I found the following is true: Last Sunday of March 01:00 GMT - Last Sunday of October 01:00 GMT = GMT+1 Last Sunday of October 01:00 GMT - Last Sunday of March 01:00 GMT = GMT+0 As of the time this issue was reported the Eire (GMT+1) and Europe/Dublin (GMT+1) time zones need to be GMT+0, however, they are GMT+1. Are there any standard troubleshooting tips I can pass along to our developers? I’m looking through the documentation I can find and the threads and have seen a couple regarding Irelands time zones, but nothing conclusive on how to solve our issue moving forward. I’d like to understand if this is an error, or if there is a configuration we need to make on our end to ensure the time zones are correct in our system. [cid:image001.jpg@01DB927E.D1C45080] [Meazure Learning]<https://us.content.exclaimer.net/?url=https%3A%2F%2Fwww.meazurelearning.com…> meazurelearning.com [Facebook]<https://us.content.exclaimer.net/?url=https%3A%2F%2Fwww.facebook.com%2FMeaz…> [X]<https://us.content.exclaimer.net/?url=https%3A%2F%2Fx.com%2Fmeazurelearning…> [LinkedIn]<https://us.content.exclaimer.net/?url=https%3A%2F%2Fwww.linkedin.com%2Fcomp…> Christopher Brown Product Manager [cid:image006.png@01DB927E.D1C45080] cbrown(a)meazurelearning.com<mailto:cbrown@meazurelearning.com> [cid:image007.png@01DB927E.D1C45080] 205-807-0349<tel:205-807-0349> [cid:image008.png@01DB927E.D1C45080] 205-807-0349<tel:205-807-0349> [cid:image009.png@01DB927E.D1C45080] Alabama, US (35244) [cid:image010.png@01DB927E.D1C45080]

2 1

Paraguay DST is no longer in use
by Nicolas Elisardo Garcia March 7, 2025

March 7, 2025

Paraguay currently observes Paraguay Time (PYT) all year. DST is no longer in use. Clocks do not change in Paraguay. The previous DST change in Paraguay was on October 15, 2024. Is there a new software release available for this update? Thanks in advance, Regards. Este mensaje y todos los archivos adjuntos a él son para uso exclusivo del destinatario y pueden contener información confidencial o propietaria, cuya divulgación es sancionada por ley. Si usted recibió este mensaje erróneamente, por favor notifíquenos respondiendo al remitente, borre el mensaje original y destruya las copias (impresas o grabadas en cualquier medio magnético) que pueda haber realizado del mismo. Todas las opiniones contenidas en este mail son propias del autor del mensaje y no necesariamente coinciden con las de Claro o alguna de las empresas accionistas. La publicación, uso, copia e impresión total o parcial de este mensaje o documentos adjuntos queda prohibida. Cualquier situación y/o comportamiento que pudiera resultar contrario a lo establecido en el Código de Ética disponible en https://www.americamovil.com/Spanish/gobierno-corporativo/Programa-de-Integ… - comunicarlo, incluso anónimamente, a través de la página web https://denuncias.americamovil.com/. This message and any attachments are for exclusive usage of an addressee and may contain confidential or privileged information whose disclosure is subject to penalty by law. If you are not the addressee, please notify the sender by return e-mail, delete the original message and destroy any existing copy no matter if printed or recorded. Any opinions contained in this e-mail are those of the author of the message and do not necessarily coincide with those of Claro or its shareholders. No part of this message or attachments may be used or reproduced in any manner whatsoever. Any situation and/or behavior that could be contrary to the provisions of the Code of Ethics available at https://www.americamovil.com/English/corporate-governance/integrity-and-com… - report it, even anonymously, through the website https://denuncias.americamovil.com/. Este mensaje y todos los archivos adjuntos a él son para uso exclusivo del destinatario y pueden contener información confidencial o propietaria, cuya divulgación es sancionada por ley. Si usted recibió este mensaje erróneamente, por favor notifíquenos respondiendo al remitente, borre el mensaje original y destruya las copias (impresas o grabadas en cualquier medio magnético) que pueda haber realizado del mismo. Todas las opiniones contenidas en este mail son propias del autor del mensaje y no necesariamente coinciden con las de Claro o alguna de las empresas accionistas. La publicación, uso, copia e impresión total o parcial de este mensaje o documentos adjuntos queda prohibida. Cualquier situación y/o comportamiento que pudiera resultar contrario a lo establecido en el Código de Ética disponible en https://www.americamovil.com/Spanish/gobierno-corporativo/Programa-de-Integ… - comunicarlo, incluso anónimamente, a través de la página web https://denuncias.americamovil.com/. This message and any attachments are for exclusive usage of an addressee and may contain confidential or privileged information whose disclosure is subject to penalty by law. If you are not the addressee, please notify the sender by return e-mail, delete the original message and destroy any existing copy no matter if printed or recorded. Any opinions contained in this e-mail are those of the author of the message and do not necessarily coincide with those of Claro or its shareholders. No part of this message or attachments may be used or reproduced in any manner whatsoever. Any situation and/or behavior that could be contrary to the provisions of the Code of Ethics available at https://www.americamovil.com/English/corporate-governance/integrity-and-com… - report it, even anonymously, through the website https://denuncias.americamovil.com/.

7 6

Re: buffer overflow in zic
by Paul Eggert March 6, 2025

March 6, 2025

On 2025-03-05 21:56, Евгений Горбанев wrote: > I found this scenario while researching the postgresql code using Svace > static analyzer. > Well, try this scenario: > > $ cd /tmp > $ wget https://data.iana.org/time-zones/releases/tzdb-2025a.tar.lz > $ tar xf tzdb-2025a.tar.lz > $ cd tzdb-2025a > $ make CFLAGS='-fsanitize=address -g' > $ touch test > $ ./zic -l test -d . Thanks for the explanation and recipe. I can reproduce the problem. Please try the attached proposed patch. I installed it into the development repository <https://github.com/eggert/tz>. Thanks.

1 0

buffer overflow in zic
by Evgeniy Gorbanev March 5, 2025

March 5, 2025

Hello! IfoundthatifI runzictocreatea linkonanotherdevice, the bufferoverflowinzip.c:1422inversion2025awill occur. Inthislinei==0. The commandtoreplay: ./zic -l test -d . -t /path/to/link_on_another_device Best regards, Evgeniy Gorbanyov

4 4

DST offsets other than +1
by Doug Ewell March 4, 2025

March 4, 2025

1. Are there any time zones that currently observe DST with an offset other than adding one hour? (For this question, I am treating “negative DST” zones like Europe/Dublin and Africa/Windhoek as if they observed “standard” time in winter and adjusted time in summer. Also, for this question I am only interested in current practice, not historical.) 2. Is there an easy way I could have looked up this information in the tz files? (“Easy” means without exhaustively parsing all the Rule and Zone lines, as a processor would have to do.) Thanks, -- Doug Ewell, CC, ALB | Lakewood, CO, US | ewellic.org

6 8

North Dakota HB 1259 requiring year-round standard time
by asinglet＠epic.com March 1, 2025

March 1, 2025

https://legiscan.com/ND/text/HB1259/2025 HB 1259 passed the North Dakota House last week. No idea on whether it will pass the ND Senate or be signed into law. The tricky thing about this bill is that it does not have an implementation time frame. Theoretically if it moves through in the next week or two, we could be looking at a repeat of the Lebanon 2023 fiasco. I hope if they are going to pass it, they take their time.

4 4

Maryland HB1290
by Arthur Olson Feb. 21, 2025

Feb. 21, 2025

The hearing on Maryland House Bill 1290, "Full-Year Daylight Saving Time," has been cancelled: https://mgaleg.maryland.gov/mgawebsite/Legislation/Details/hb1290 In past years such bills died in committee, but only having had a hearing; this is the earliest death yet for such a bill. Perhaps the state legislators have more important matters on their minds this year. @dashdashado

2 1

EST5EDT should not resolve to America/New_York because they have different offsets
by Austin Hill Feb. 21, 2025

Feb. 21, 2025

Hello - I recently filed a GitHub issue against the perl DateTime::TimeZone library, which uses your database: https://github.com/houseabsolute/DateTime-TimeZone/issues/58#issue-28644459… I noticed that EST5EDT now resolves to America/New_York. This is problematic because the two do not have the same offset - EST5EDT is -5:00 and America/New_York is -04:56:02. My ticket was closed because the behavior appears to be caused by changes in your database in commit a0b09c0 ( https://github.com/eggert/tz/commit/a0b09c0230089252acf2eb0f1ba922e99f7f4a03 ). Is this something that you would consider changing? Thanks! - Austin Hill

9 16

localized date without time
by Alejandro Colomar Feb. 12, 2025

Feb. 12, 2025

Hi Paul, Link: <https://github.com/shadow-maint/shadow/issues/1057> Currently, shadow utils' passwd(1) (and several other programs) uses UTC time when printing. That is: $ passwd -S alx alx P 2023-09-20 0 99999 7 -1 the date from above is a UTC representation of $ sudo cat /etc/shadow | grep alx | cut -f3 -d: 19620 However, shadow utils programs, such as chage(1), use local time in input. That timestamp was set by chage(1), interpreting a local date: $ sudo chage -d 2023-09-21 alx $ sudo cat /etc/shadow | grep alx | cut -f3 -d: 19620 $ date Wed Jul 31 07:54:17 CEST 2024 This is rather confusing, and we think that passwd(1) should also print the date in local time, when printing human-readable dates. However, I think it might be better to show the timezone information together with the date, to be clear that what we're printing is local time. Do you think that's reasonable? Or maybe it's understood that when printing a date some timezone information is implicitly local? I didn't find any way to print timezone information in ISO 8601, if you don't print the time together with the date. That is, ISO 8601 says: C.1.3.1 Date A date string represents one of the following: • year, month, and day (e.g. 2001-02-03) • year and month (e.g. 2008-12 ) • year (e.g. 2008) and C.1.3.2 Date and Time A date/time string is composed according to one of three representations as illustrated in the following three examples: • 2001-02-03T09:30:01 • 2004-01-01T10:10:10Z • 2004-01-01T10:10:10+05:00 but I don't see any way to print something like 2023-09-21+02:00 in standardese. Is this a defect in ISO 8691? I see that in C.1.3.2, it says "Zone-offset may be omitted or included", so I guess we can just omit it. What do you think we should do? Thanks! And have a lovely day! Alex -- <https://www.alejandro-colomar.es/>

5 17

ELIZA Reanimated
by Brooks Harris Jan. 23, 2025

Jan. 23, 2025

ELIZA Reanimated: The world’s first chatbot restored on the world’s first time sharing system https://arxiv.org/pdf/2501.06707 Has anyone asked ELIZA what time it is?

3 3

Re: Notice of a problem with the Asia/Tokyo time zone
by Paul Eggert Jan. 22, 2025

Jan. 22, 2025

> From: Patrick BENNY <patrick.benny(a)mixi.co.jp> > Date: Mon, Jan 20, 2025 at 6:41 PM > The Asia/Tokyo time zone seems to have been linked with Australia, probably > by mistake. > Please see this related difference from the zone1970.tab file, observed > when comparing 2024b and 2025a. > > 186c186 > < JP +353916+1394441 Asia/Tokyo > --- >> JP,AU +353916+1394441 Asia/Tokyo Eyre Bird Observatory > > The Eyre Bird Observatory should probably be linked with an Australian time > zone instead of Asia/Tokyo. Actually that line should be OK, as the Eyre Bird Observatory region (unlike the rest of Australia) has observed Tokyo time since 1970. The comments at the start of zone1970.tab say this about the "Eyre Bird Observatory" in column 4: # Comments; present if and only if countries have multiple timezones, # and useful only for those countries. For example, the comments # for the row with countries CH,DE,LI and name Europe/Zurich # are useful only for DE, since CH and LI have no other timezones. "Eyre Bird Observatory" is useful only for AU, since JP has no other timezones; so this is another example of that column-4 idea.

4 4

Medovukha factory in Kazakhstan advances its clocks by 1/20 of a day
by Paul Eggert Jan. 21, 2025

Jan. 21, 2025

Last year's move to unify Kazakhstan into a single UTC+05 time zone is seeing some pushback. In "Anger over Kazakh Time Zones" (2024-12-24)[1] RFE/RL's Chris Rickleton and Tasqyn Bolatuly reported that one lawmaker asserted that a majority his party in parliament would support a law to reverse the decision. Although government executive officials still strongly support the move, we'll need to keep an eye on the situation. Rickleton and Bolatuly also reported how one private firm is addressing the problem: > Almas Tangytuli, the owner of a company that produces medovukha, a honey-based alcoholic drink similar to mead, says he is already doing something similar. > > After struggling with the new time, he set the clocks at his factory just east of Oskemen forward by a 1 1/5 hour for the sake of his workers, who keep livestock in villages nearby. > > "After work, there was no time for them to sort out their barns in the steppe, where there is no lighting. In the morning, their cattle make a rush for the fields. You can't tell cattle that the clocks have changed," Tangytuli told RFE/RL. 1 1/5 hour is 72 minutes, or 1/20 of a day. I wonder where Tangytuli got that number? Oskemen is about 5.5 hours ahead of UTC, so he has overcorrected and is about 0.7 hours ahead of local mean time; surely this is not entirely for the sake of the cows. The fractional hour vaguely reminds me of William Willett's 1907 proposal to implement daylight saving time by advancing clocks by 20 minutes each in four successive Sundays.[2] But although Willett wanted his construction workers to get to his worksites earlier during the day, he wrote nothing about his workers' cows. [1]: https://www.rferl.org/a/33249639.html [2]: https://www.webexhibits.org/daylightsaving/willett.html

1 0

Re: [tz-announce] 2025a release of tz code and data available
by Paul Eggert Jan. 21, 2025

Jan. 21, 2025

On 2025-01-16 11:21, Geert Hendrickx wrote: > On Thu, Jan 16, 2025 at 09:37:50 -0800, Paul Eggert via tz-announce via tz wrote: >> ... Paraguay adopts permanent -03 starting spring 2024. > > starting spring *2025* ? Actually, "spring 2024" is correct. Release 2025a says the legal change occurred in Paraguay on 2024-10-15 at 00:00, which is spring in the southern hemisphere. The clocks didn't change then: only tm_isdst changed, and since tm_isdst is obsolescent that wasn't enough to prompt a new TZDB release right away. The first change to predicted timestamps is this year on March 22 at 00:00, when Paraguay is now predicted to stay at -03 instead of falling back from -03 to -04. This will be autumn in the southern hemisphere.

1 1

[tz-announce] 2025a release of tz code and data available
by Paul Eggert via tz-announce 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

Re: Windows compile failure for iana time zones
by Paul Eggert Jan. 15, 2025

Jan. 15, 2025

On 1/13/25 05:17, Manuela Friedrich wrote: > It seems that your commit 1ee9daa91818f5d4ab6937352453813fa333e105 > fails with: > localtime.c(309): error C2099: initializer is not a constant Thanks for reporting that. Which compiler are you using and what version and what compiler flags are you using? Does the following uninstalled patch fix things for you? If not, what's the value of _MSC_VER when you use your compiler flags? diff --git a/private.h b/private.h index 0a546e02..3e64da4e 100644 --- a/private.h +++ b/private.h @@ -26,7 +26,11 @@ because RHEL 7 (whose GCC defaults to C89) extended life cycle support (ELS) is scheduled to end on 2028-06-30. */ #ifndef PORT_TO_C89 -# define PORT_TO_C89 0 +# if defined _MSC_VER && _MSC_VER < 1800 +# define PORT_TO_C89 1 +# else +# define PORT_TO_C89 0 +# endif #endif /* SUPPORT_C89 means the tzcode library should support C89 callers Perhaps we could use the patch with a different value in place of 1800, or perhaps we should just remove the " && _MSC_VER < 1800". Microsoft says[1] that it didn't add support for C99-style compound literals until Visual Studio 2013. Are you using an older version of MSVC? If so, it's past end-of-life[2] and I doubt whether we should worry about it. [1]: https://learn.microsoft.com/en-us/previous-versions/visualstudio/visual-stu… [2]: https://devblogs.microsoft.com/visualstudio/support-ends-for-older-versions…

3 5

Paraguay may adopt permanent DST soon
by Heitor David Pinto Jan. 13, 2025

Jan. 13, 2025

Today the Congress of Paraguay passed a bill to observe UTC-3 permanently, equivalent to permanent DST. The bill still needs to be approved by the president. https://www.abc.com.py/politica/2024/09/24/congreso-sanciona-horario-de-ver… The text of the bill says that it would enter into force on the first Sunday in October 2024, the same date currently scheduled to start DST. But in practice, it would only make a difference from the fourth Sunday of March 2025, the date currently scheduled to end DST. https://silpy.congreso.gov.py/web/expediente/132531

10 20

[PROPOSED 1/3] Alias asctime, ctime result
by Paul Eggert Jan. 10, 2025

Jan. 10, 2025

I misread C99, and in a 2022-11-30 patch caused asctime and ctime to return different pointers when !SUPPORT_C89. However, C99 and later still require that these two functions return the same pointers, so revert that part of the 2022-11-30 change. * asctime.c (buf_ctime): Remove. All uses replaced with buf_asctime. --- asctime.c | 13 +------------ 1 file changed, 1 insertion(+), 12 deletions(-) diff --git a/asctime.c b/asctime.c index 1bfcafe9..491d23bf 100644 --- a/asctime.c +++ b/asctime.c @@ -30,16 +30,6 @@ enum { STD_ASCTIME_BUF_SIZE = 26 }; */ static char buf_asctime[2*3 + 5*INT_STRLEN_MAXIMUM(int) + 7 + 2 + 1 + 1]; -/* A similar buffer for ctime. - C89 requires that they be the same buffer. - This requirement was removed in C99, so support it only if requested, - as support is more likely to lead to bugs in badly written programs. */ -#if SUPPORT_C89 -# define buf_ctime buf_asctime -#else -static char buf_ctime[sizeof buf_asctime]; -#endif - /* On pre-C99 platforms, a snprintf substitute good enough for us. */ #if !HAVE_SNPRINTF # include <stdarg.h> @@ -86,8 +76,7 @@ asctime_r(struct tm const *restrict timeptr, char *restrict buf) register const char * mn; int year, mday, hour, min, sec; long long_TM_YEAR_BASE = TM_YEAR_BASE; - size_t bufsize = ((buf == buf_ctime - || (!SUPPORT_C89 && buf == buf_asctime)) + size_t bufsize = (buf == buf_asctime ? sizeof buf_asctime : STD_ASCTIME_BUF_SIZE); if (timeptr == NULL) { -- 2.47.1

1 2

v2024b Mexico rules
by Ertan Küçükoglu Jan. 8, 2025

Jan. 8, 2025

Hello, Below is a section taken from v2024b northamerica file # Rule NAME FROM TO - IN ON AT SAVE LETTER/S Rule Mexico 1931 only - April 30 0:00 1:00 D Rule Mexico 1931 only - Oct 1 0:00 0 S Rule Mexico 1939 only - Feb 5 0:00 1:00 D Rule Mexico 1939 only - Jun 25 0:00 0 S Rule Mexico 1940 only - Dec 9 0:00 1:00 D Rule Mexico 1941 only - Apr 1 0:00 0 S Rule Mexico 1943 only - Dec 16 0:00 1:00 W # War Rule Mexico 1944 only - May 1 0:00 0 S Rule Mexico 1950 only - Feb 12 0:00 1:00 D Rule Mexico 1950 only - Jul 30 0:00 0 S Rule Mexico 1996 2000 - Apr Sun>=1 2:00 1:00 D Rule Mexico 1996 2000 - Oct lastSun 2:00 0 S Rule Mexico 2001 only - May Sun>=1 2:00 1:00 D Rule Mexico 2001 only - Sep lastSun 2:00 0 S Rule Mexico 2002 2022 - Apr Sun>=1 2:00 1:00 D Rule Mexico 2002 2022 - Oct lastSun 2:00 0 S If you look closely, the first rule has the full month name April written and not a three letter short version like the rest of the list. I wonder if that is the new format and not an error. Thanks & Regards, Ertan

2 1

[PROPOSED 1/7] Modernize date man page
by Paul Eggert Jan. 8, 2025

Jan. 8, 2025

* date.1: Update the example to next year. Remove duplication of spec with strftime, as this is too much of a pain to maintain separately for what is just a demo; but give an example for clarity. Update list of files accessed, to match current code. --- date.1 | 110 +++++++++------------------------------------------------ 1 file changed, 16 insertions(+), 94 deletions(-) diff --git a/date.1 b/date.1 index 01907bc7..9b025bc9 100644 --- a/date.1 +++ b/date.1 @@ -35,7 +35,7 @@ command without arguments writes the date and time to the standard output in the form .ce 1 -Wed Mar 8 14:54:40 EST 1989 +Sat Mar 8 14:54:40 EST 2025 .br with .B EST @@ -49,92 +49,17 @@ If a command-line argument starts with a plus sign (\c .q "\fB+\fP" ), the rest of the argument is used as a .I format -that controls what appears in the output. -In the format, when a percent sign (\c -.q "\fB%\fP" -appears, -it and the character after it are not output, -but rather identify part of the date or time -to be output in a particular way -(or identify a special character to output): -.nf -.sp -.if t .in +.5i -.if n .in +2 -.ta \w'%M\0\0'u +\w'Wed Mar 8 14:54:40 EST 1989\0\0'u - Sample output Explanation -%a Wed Abbreviated weekday name* -%A Wednesday Full weekday name* -%b Mar Abbreviated month name* -%B March Full month name* -%c Wed Mar 08 14:54:40 1989 Date and time* -%C 19 Century -%d 08 Day of month (always two digits) -%D 03/08/89 Month/day/year (eight characters) -%e 8 Day of month (leading zero blanked) -%h Mar Abbreviated month name* -%H 14 24-hour-clock hour (two digits) -%I 02 12-hour-clock hour (two digits) -%j 067 Julian day number (three digits) -%k 2 12-hour-clock hour (leading zero blanked) -%l 14 24-hour-clock hour (leading zero blanked) -%m 03 Month number (two digits) -%M 54 Minute (two digits) -%n \\n newline character -%p PM AM/PM designation -%r 02:54:40 PM Hour:minute:second AM/PM designation -%R 14:54 Hour:minute -%S 40 Second (two digits) -%t \\t tab character -%T 14:54:40 Hour:minute:second -%U 10 Sunday-based week number (two digits) -%w 3 Day number (one digit, Sunday is 0) -%W 10 Monday-based week number (two digits) -%x 03/08/89 Date* -%X 14:54:40 Time* -%y 89 Last two digits of year -%Y 1989 Year in full -%z -0500 Numeric time zone -%Z EST Time zone abbreviation -%+ Wed Mar 8 14:54:40 EST 1989 Default output format* -.if t .in -.5i -.if n .in -2 -* The exact output depends on the locale. -.sp -.fi -If a character other than one of those shown above appears after -a percent sign in the format, -that following character is output. -All other characters in the format are copied unchanged to the output; -a newline character is always added at the end of the output. -.PP -In Sunday-based week numbering, -the first Sunday of the year begins week 1; -days preceding it are part of -.q "week 0" . -In Monday-based week numbering, -the first Monday of the year begins week 1. -.PP -To set the date, use a command line argument with one of the following forms: -.nf -.if t .in +.5i -.if n .in +2 -.ta \w'198903081454\0'u -1454 24-hour-clock hours (first two digits) and minutes -081454 Month day (first two digits), hours, and minutes -03081454 Month (two digits, January is 01), month day, hours, minutes -8903081454 Year, month, month day, hours, minutes -0308145489 Month, month day, hours, minutes, year - (on System V-compatible systems) -030814541989 Month, month day, hours, minutes, four-digit year -198903081454 Four-digit year, month, month day, hours, minutes -.if t .in -.5i -.if n .in -2 -.fi -If the century, year, month, or month day is not given, -the current value is used. -Any of the above forms may be followed by a period and two digits that give -the seconds part of the new time; if no seconds are given, zero is assumed. +that is processed by +.BR strftime (3) +to determine what to output; +a newline character is appended. +For example, the shell command: +.ce 1 +date +"%Y\*-%m\*-%d %H:%M:%S %z" +.br +outputs a line like +.q "2025\*-03\*-08 14:54:40 \*-0500" +instead. .PP These options are available: .TP @@ -149,16 +74,13 @@ past the epoch of 1970-01-01 00:00:00 UTC, where should be an integer, either decimal, octal (leading 0), or hexadecimal (leading 0x), preceded by an optional sign. .SH FILES -.ta \w'/usr/share/zoneinfo/posixrules\0\0'u +.ta \w'/usr/share/zoneinfo/Etc/UTC\0\0'u /etc/localtime local timezone file .br /usr/lib/locale/\f2L\fP/LC_TIME description of time locale \f2L\fP .br /usr/share/zoneinfo timezone directory .br -/usr/share/zoneinfo/posixrules default DST rules (obsolete) -.br -/usr/share/zoneinfo/GMT for UTC leap seconds -.PP -If /usr/share/zoneinfo/GMT is absent, -UTC leap seconds are loaded from /usr/share/zoneinfo/GMT0 if present. +/usr/share/zoneinfo/Etc/UTC for UTC leap seconds +.SH SEE ALSO +.BR strftime (3). -- 2.47.1

1 6