- tz - lists.iana.org

Re: [tz] tz Digest, Vol 138, Issue 71
by Rich Armstrong March 27, 2023

March 27, 2023

Though this list usually doesn't include discussion of the time-zone-rule data that Microsoft maintains in the Windows registry, it seems worth considering how to ensure the two repositories of time-zone rules might be kept in sync—not to mention IATA's repository. Thoughts and opinions from any MS representatives would be welcome. (Incidentally, I was born at 11:50 PM at a place and time when hospitals recorded births on standard time even though the general population observed DST. Consequently, I reserve the right to celebrate my birthday on the 12th and/or 13th of July.) ________________________________ From: tz <tz-bounces(a)iana.org> on behalf of tz-request(a)iana.org <tz-request(a)iana.org> Sent: Monday, March 27, 2023 1:29 PM To: tz(a)iana.org <tz(a)iana.org> Subject: tz Digest, Vol 138, Issue 71 Send tz mailing list submissions to tz(a)iana.org To subscribe or unsubscribe via the World Wide Web, visit https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.o… or, via email, send a message with subject or body 'help' to tz-request(a)iana.org You can reach the person managing the list at tz-owner(a)iana.org When replying, please edit your Subject line so it is more specific than "Re: Contents of tz digest..."

1 0

Urgent | Palestine Timezone "Asia/Gaza | Asia/Hebron" Daylight Changed unitl 29/04/2023
by Rifat Maswadeh March 27, 2023

March 27, 2023

Dear Sir, I'm Rifat From Palestine, Yesterday 25/03/2023 at 2:00 AM time changed "Daylight" +1 and set +3 GMT , This changed not updated in last Palestinian government decision about change daylight time in coming 3 years (2023,2024,2025) as follows : *29/04/2023 * [image: image.png] Thanks ! - attached

2 1

(no subject)
by Andrea Singletary March 27, 2023

March 27, 2023

Will 2023c have Asia/Beirut starting DST this year on March 30? What does this mean for future years? Wish the cabinet would've clarified that while they were on the subject, as Spring Forward intersects with Ramadan for the next few years... -- Sent from my pocket-sized infinite improbability generator

4 5

Lebanon reverse summertime delay
by Hagop Jamkojian March 27, 2023

March 27, 2023

Hi there, Just wanted to let you know that the Lebanese prime minister has decided to reverse the decision again https://www.bbc.com/news/world-middle-east-65090888 effective Wednesday night 😕 Timezone DB (https://github.com/eggert/tz) is still not updated to show this change, so wanted to give you a heads up. Best regards, Hagop Jamkojian

1 0

Lebanese Time Zone
by S J March 27, 2023

March 27, 2023

Hello, Your recent changes to Lebanon's adherence to DST is wrong: "This year Lebanon springs forward April 20/21 not March 25/26. (Thanks to Saadallah Itani.)" https://data.iana.org/time-zones/tzdb/NEWS The government of Lebanon did not issue a law decree stating this change and proper legal procedures were not followed. This led to civil action locally where all respected media and groups are not abiding by this decision, taken without any proper legal procedures. Please correct the change on your end to avoid adding to the massive confusion. All devices have already updated to DST, so your change is only adding to the confusion. Thank you for your understanding. I do not give the right to use my name, email or any other identifying information on any public communications or messages or updates.

2 1

Lebanon Resumes DST on March 29/30
by Bassel Shurbaji March 27, 2023

March 27, 2023

Hello, I thought I should let you know that the government of Lebanon announced that it will resume *DST* on* March 29/30* instead of* April 20/21* as per your latest *Release 2023b*. https://twitter.com/MTVLebanonNews/status/1640312857890832389 https://twitter.com/ALJADEEDNEWS/status/1640313313790681088 Best, Bassel Shurbaji

1 2

Re: [tz] Fw:Time Zone Iran
by Paul Eggert March 27, 2023

March 27, 2023

On 2023-03-26 23:39, Patrick.Stergonschegg(a)orf.at wrote: > Hello, > > > I just noticed that the Windows time zone for "UTC +03:30 Tehran" is probably being computed incorrectly. > > > It seems that DST +1 is being added, although Iranian Government announced that they will not switch to DST anymore, beginning in 2023. > > > Official IR News Agency announcement: http://irna.ir/xjJ3TT > > Current Time: https://time.ir > > > I assume that Microsoft imports IANA time zone data: http://bit.ly/3ZmGzTE > > > In the file tzdata2023b\asia on line 1625 it says: > > 3:30 Iran +0330/+0430 > > > I assume the line should be changed and a new line should be added, e.g.: > > 3:30 Iran +0330/+0430 2022 > > 3:30 - +0330 I don't see a need for such a change, as the "Iran" rules end this way: Rule Iran 2021 2022 - Mar 21 24:00 1:00 - Rule Iran 2021 2022 - Sep 21 24:00 0 - The shell command 'zdump -i -c 2021,2030 Asia/Tehran' outputs this: TZ="Asia/Tehran" - - +0330 2021-03-22 01 +0430 1 2021-09-21 23 +0330 2022-03-22 01 +0430 1 2022-09-21 23 +0330 which looks OK: it stops after 2022. If your MS-Windows host disagrees, perhaps you need to update its tables. I don't know how that works, though. > > More ressources: > > http://bit.ly/3lQC9qp > > https://www.timeanddate.com/worldclock/iran > > > I am looking forward to any feedback. > > > Thanks a lot, > Patrick > >

2 1

Lebanon's Cabinet Reverses Decision of DST Delay
by Patrick March 27, 2023

March 27, 2023

Hello IANA, This is to keep you updated that Lebanon has reverted its DST shift decision of the 23. https://www.reuters.com/world/middle-east/lebanons-cabinet-reverses-decisio… Thank you! Yours, --- Patrick Louis

1 0

Re: [tz] Lebanon will not spring forward this weekend
by Saadallah Itani March 27, 2023

March 27, 2023

Cancellation of DST postpone - official announcmenet Regards, Saad Ext. 2229 Sent from my iPhone > On 27 Mar 2023, at 1:30 PM, Saadallah Itani <sitani(a)aub.edu.lb> wrote: > > Dear Paul, > > Lebanese government announced to revert back the DST (March) timing and not to postpone to April on the evening of Wednesday at 23:59 > > Source: http://mtv.com.lb/News/1353208 > > > Please create a new db file. > > Thank you > > Regards, > Saad > Ext. 2229 > > Sent from my iPhone > >> On 24 Mar 2023, at 12:43 AM, Paul Eggert <eggert(a)cs.ucla.edu> wrote: >> On 3/23/23 13:22, Saadallah Itani wrote: >> >>> I hope Linux Vendors pull the new tzdb changes soon. >> >> We first have to publish tzdb 2023b with the patch for Lebanon <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.…>, which I hope to do quite soon. >> >> Unfortunately, many GNU/Linux and other downstream suppliers take some time (a week or more) to test changes before they release data to their users. So unless you're using one of the smaller, faster-moving distros like Alpine Linux you'll likely be out of luck. >> >> People in Lebanon can work around the problem temporarily with an approximation like TZ='EET-2EEST,M4.3.5/0,M10.5.0/0' (this is good for predicted timestamps from April 15, 2022 up to but not including March 31, 2024). If your system doesn't support POSIX TZ strings (many cell phones are like this), you can instead use an approximation like TZ='Africa/Tripoli' (good for predicted timestamps from March 27, 2022 up to April 21 of this year).

1 0

Lebanon DST change reverted
by Rany Hany March 27, 2023

March 27, 2023

Greetings, The DST change for Lebanon that was adopted in 2023b should be reverted 48 hours from now. The cabinet met today and rolled it back. The Council of Ministers decided to adopt daylight saving time once again starting from Wednesday night (needs details on exactly when "Wednesday night" is, I presume Thursday). Sources: * https://www.lbcgroup.tv/news/breaking-news/694239/%D9%85%D8%B9%D9%84%D9%88%… * https://www.mtv.com.lb/News/%D9%85%D8%A8%D8%A7%D8%B4%D8%B1/1353208/%D9%85%D…

1 1

Re: [tz] Lebanon will not spring forward this weekend
by Saadallah Itani March 27, 2023

March 27, 2023

Dear Paul, Lebanese government announced to revert back the DST (March) timing and not to postpone to April on the evening of Wednesday at 23:59 Source: http://mtv.com.lb/News/1353208 Please create a new db file. Thank you Regards, Saad Ext. 2229 Sent from my iPhone > On 24 Mar 2023, at 12:43 AM, Paul Eggert <eggert(a)cs.ucla.edu> wrote: > On 3/23/23 13:22, Saadallah Itani wrote: > >> I hope Linux Vendors pull the new tzdb changes soon. > > We first have to publish tzdb 2023b with the patch for Lebanon <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.…>, which I hope to do quite soon. > > Unfortunately, many GNU/Linux and other downstream suppliers take some time (a week or more) to test changes before they release data to their users. So unless you're using one of the smaller, faster-moving distros like Alpine Linux you'll likely be out of luck. > > People in Lebanon can work around the problem temporarily with an approximation like TZ='EET-2EEST,M4.3.5/0,M10.5.0/0' (this is good for predicted timestamps from April 15, 2022 up to but not including March 31, 2024). If your system doesn't support POSIX TZ strings (many cell phones are like this), you can instead use an approximation like TZ='Africa/Tripoli' (good for predicted timestamps from March 27, 2022 up to April 21 of this year).

1 0

Lebanon to go back to DST midnight Wednesday March 29th
by Jad Baz March 27, 2023

March 27, 2023

Lebanon to go back to DST midnight Wednesday March 29th https://twitter.com/ALJADEEDNEWS/status/1640313313790681088?t=G_VQcAnq10PSY… https://twitter.com/LBCI_NEWS/status/1640312096972742656?s=19

1 0

Lebanon DST change internally disputed
by Jad Baz March 26, 2023

March 26, 2023

Lebanon is going through many internal disputes surrounding the latest decision to delay DST Many institutions are refusing to comply with the change and are going to adopt regular DST on Sunday Mar 26th Those institutions include but are not limited to: - News agencies - Religious organizations - Schools, universities, etc... The refusal is mainly centered the legality of that decision and, obviously, the technical chaos it will create because of its short notice Moreover, as some of the below articles mention, this is also causing sectarian strife All of these concerns are important to bring to light in view of IANA's procedures for updating timezone data: If you would ask today "what the average person on the street would think the time actually is", it's not at all clear what the answer would be Below are some links about these latest developments: https://www.cnn.com/2023/03/25/middleeast/lebanon-daylight-savings-intl/ind… https://www.lbcgroup.tv/news/lebanon-news/693963/lbci-refuses-to-comply-wit… https://www.lbcgroup.tv/news/news-bulletin-reports/693989/lebanese-patriarc… http://www.mtv.com.lb/en/news/local/1352862/bkerke--we-are-committed-to-swi… http://www.mtv.com.lb/en/news/live_feed/1352804/mtv-will-not-comply-with-th… https://today.lorientlejour.com/article/1332635/postponement-of-daylight-sa…

10 20

Time Zone Iran
by Patrick.Stergonschegg＠orf.at March 26, 2023

March 26, 2023

Hello, I just noticed that the Windows time zone for "UTC +03:30 Tehran" is probably being computed incorrectly. It seems that DST +1 is being added, although Iranian Government announced that they will not switch to DST anymore, beginning in 2023. Official IR News Agency announcement: http://irna.ir/xjJ3TT Current Time: https://time.ir I assume that Microsoft imports IANA time zone data: http://bit.ly/3ZmGzTE In the file tzdata2023b\asia on line 1625 it says: 3:30 Iran +0330/+0430 I assume the line should be changed and a new line should be added, e.g.: 3:30 Iran +0330/+0430 2022 3:30 - +0330 More ressources: http://bit.ly/3lQC9qp https://www.timeanddate.com/worldclock/iran I am looking forward to any feedback. Thanks a lot, Patrick

1 0

Lebanon DST change update - central bank to use two timezones
by Jad Baz March 25, 2023

March 25, 2023

Lebanon's central bank said it would only adopt government decision (of postponing DST) for work shifts and schedules but would stick to regular DST time in its systems and transactions https://www.mtv.com.lb/news/%D9%85%D9%80%D9%80%D8%AD%D9%80%D9%80%D9%84%D9%8… https://twitter.com/BeirutCityGuide/status/1639653667694428161?s=20

1 0

[tz-announce] 2023b release of tz code and data available
by Paul Eggert via tz-announce March 23, 2023

March 23, 2023

The 2023b release of the tz code and data is available. It follows so closely on the 2023a release because Lebanon's government announced that Lebanon's spring-forward transition previously scheduled for the end of this week has been delayed until April 20. This release contains the following change: Briefly: Lebanon delays the start of DST this year. Changes to future timestamps This year Lebanon springs forward April 20/21 not March 25/26. (Thanks to Saadallah Itani.) Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2023b.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2023b.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2023b.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 71faa2a55db2c9f21f4099b58c28536673982e0a dated 2023-03-23 19:50:38 -0700 and tagged '2023b' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 94058ceabfdaa62eeff9be804a030f0eb95b4099b62fbb7e55557e8b934c8d883f488a3a6996331e24aebd147d66c19a73fb925a3dd929c630a9e11b51003b7f tzcode2023b.tar.gz 0f697b872ef02109d2098db12d0effc834b2ac5438921e0867f2c70987f305a47dc3eac720c344bb3757c902a7653109621e943564bdfbf00937077c311aa29b tzdata2023b.tar.gz 286ab1bf768dda48d4066d2477de0f3db9c26e55e26c1a4f33b450268255f28d57360bffe602a3bc29f8a281b7e0ff17880fe1d14914d6361f62abb7526e5081 tzdb-2023b.tar.lz Here are GPG digital signatures for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmQdELYACgkQ7ZfpDmKq fjQpIQ//eOaHIqWDFcotP/ntWHses+E1PaalrArGe6uoGJYR3Aql9GBIM/BrhBZH oiCeRxxsLLoU4ZoJdrEh3Q4q4a3g/j5NGL3oi1ktlwHz1dnJFd2UQ+XlK2mv2/Lb o+cwaM0RV8SZojClxXF/ditXgsJ+EGbSX7WYKX7XfCxdWwFw+ZZPPcYvmXvenFCl wtJWjgo11a3V7OpKk4kfX/EuoNoHTF7uOIr943Id96JFM0z7LET1zaoKzObMs0+l Afyi1Rl0bxO6rlPH+HRJb41cac1YXMcoRkz0rzvaZalEA4FYFYIsA4nbuVB1DGIW xzQLErGgBg9NFLSIQJmocS7V3T3KpSeIXAfUMN3XMUMVfOwv9Fm0ZdzgPEH3/Xhr h/6C1a18Q+xeicqaB7Hm+nybH51sFxajx9xoGcr+Ij+1ze1W4Rk7LnHC6+tsqQ/D N+P1fBEcb33C3/T8G2s+OWNMRInotcqAnZYUqLkFTmNbWEC1xdWdUZGxY+0PxDSX c7UGAgj7E9G4JS684AkcpVgIJUwz0XyQIZkJHudg7FyEjW7U7qIycXUwC+RCVtWb tnJX9TxzP01/kD3R3C8CALByCJW4OTlpwcETqACjUF6JBpAHHbFWGY1znBs/zsDa PSMozhoQ3moWHRBsW3PU7XBsxOf6kDMrqUxWTo1oKVv0Jy5xfO0= =UybO -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmQdELYACgkQ7ZfpDmKq fjQJpg//cdQED6jsk1BnqHOCL1/PPUxJsl1SmDlcAoO4o7Odt5AlTFq6P6zGzRze F+P1P6k9mD09IyiQC3m3wQaROoyAoaErPeuzwmoDT/rBVNRraSE0t8xy2jDytkne CH3f1TMYYqQOWpQnDxzMKByypkNCG9o0ryzhTMWRI9BNnLZqwRnyRFWPdLYM5O7/ DxFk3YbtoB9IoO2LR32dqYxrrKKb6cjr7exTGI+0WQNwQEK0HV/62bImDmparUei 8BZKc9fk41xNYJJxdew81pSAmRK6TMHPOG5cvs8KPLIb/lKfG21wJXL0wDr0U4wy L15riEQlkRckzG2IIV2OB5F+5MY7NWNHubuJ0YEBDJkPMQKfBPSkZM1xkvosiend 8BBgHPBH4HiZ9z/ZvrRXyIjOOpYuko9wyiqtRpqSp4OimB2RMV6VG8oSD+OG3YCj VhF2+KlZwLj9mG9sOeslDuBnp4h4eyCvVoILQNE0qYjeHGY4WTkqP/l29ZI2+rQW cfcOk8atl4ojmekmsLcoz3EnJLtDIgtLtchHTIKsDQgZnVNASnvpaZXU3l8T6fZf 0PitHf90Qj2WWkuiMkNBbS0q4D/CknH7pqy1TY8/IWQRrvPp9deLDEMs+TcSleOk 1HZ1bxgCL1lgqQGiqC66Ybyy794bG6g3CclFkSHGGB8UcC1hkg8= =o96Z -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmQdELgACgkQ7ZfpDmKq fjRyIhAAiuZfMpkCkyrVZycCouQsPeYtUPSeJpbaUHktBWZYxZ7JwCvLEFx9RC1+ Pz3Siiwes7Q0R0yuFCOr11oDfS9br22WOuvSYdaNacdxp8Xas8s5vKwj5ObJcu+a sYyrKMBlEf4nPiwZTXNaX5OW+kNJEFS9A+TS2vJ0Us3JzWrcfucBVnSwDqIkXWO5 99JXfqENH5OtxX5hbrGLCJ6g0A48tFgHWCXWIQ3NyCZQQzylLjQubXZHkcn9VVhP R1eesSskihJrNpUAaTS8eneZeJ9sdT7iulk+cgCI+uTMl+QOFtiEBxtF7Osj1faq xgguz7qIP2h47EIZDsBpKvyyOxL5MDsrGvbu/1zi6QzbBjIXR7UQ1s9OzZy+Zh+r Nxav3vYHXHpayFn7i6/BTEjLak4Jdr526DwyM9OAxiq9Bx4d6LAk3H14OHFKa6i8 6Nbp+4SjhuD+ycjyyU49SIdCYvakXgHHYHSnngXQzp9LO01cG4tHfnFadYN+l6Va iu+HqPBQqbieuKqqtC9Zvx0xSFxUQLnraVTERkaUFPNRPhxiezMStPCCAbAhceAc cXsfbhcrQrvd46L9Lm89+ywkNsrVw9e/j3yWsHTAxhqpyda6v/XRUV9LgqwSUego MKQT5q/XB7Zn7stC6Fj/XHzh4Ty4yLJ65SWjreXV1+C+fqijVA8= =BTwz -----END PGP SIGNATURE-----

1 0

Lebanon DST last minute postponed, IANA not informed!
by Jad Baz March 23, 2023

March 23, 2023

Dear timezone coordinators, My name is Jad Baz, I am a software engineer from Lebanon I just wanted to bring to your attention an issue concerning Lebanon's last minute cancellation of DST this Sunday (March 26th 2023) Lebanon, as part of the EEST timezone, is supposed to enter in DST this Sunday However, this was postponed due to Ramadan It was announced today (Thu March 23rd) by several news outlets that the Secretary General of the Council of Ministers decided to change postpone DST from this Sunday March 26th to April 21st Below, you will find a few links to news articles in English from trusted Lebanese news agencies: - https://www.lbcgroup.tv/news/lebanon-news/693669/lebanon-postpones-daylight… - https://www.mtv.com.lb/news/local/1352516/lebanon-postpones-daylight-saving… I checked the latest IANA updates from March 22nd and did not find mention of this latest development I think this decision was taken haphazardly without much regard for how this change will be propagated (as are most decisions in Lebanon, sadly...) I know my question is coming quite last minute But I'm wondering what needs to be done to save the situation as this is causing a lot of chaos (eg airlines) I looked at the procedures doc and initially thought that there must be some formal communication that needs to go out from government employees but it seems that "what the average person on street would think the time actually is" is enough So my questions are: - Are the above articles enough to make this change? Or is there any other data you need that I can help with? - Do you expect this might be amended by Sunday? If not, what's a more realistic estimate of a schedule? Thank you very much, Jad Baz

1 0

DST Change in Lebanon
by Rany Hany March 23, 2023

March 23, 2023

Hello, Lebanon has extended daylight savings time until April 20 2023 (exceptionally this year). It's so that people fasting this ramadan stop their fasting at 5PM instead of 6PM. Sources: - https://twitter.com/grandserail/status/1638874765954785280 - https://twitter.com/timourazhari/status/1638877448447115266 Best

1 0

Fwd: [tz-announce] 2023a release of tz code and data available
by Saadallah Itani March 23, 2023

March 23, 2023

1 0

Asia/Bangkok
by Chris Walton March 22, 2023

March 22, 2023

Paul, Sorry for the timing of this message; I know you are in the middle of trying to push out 2023a. At some point in the last few months the description of Asia/Bangkok in zone1970.tab changed from "Indochina (most areas)" to "north Vietnam". Is this really what you intended? -chris

2 1

[tz-announce] 2023a release of tz code and data available
by Paul Eggert via tz-announce March 22, 2023

March 22, 2023

The 2023a release of the tz code and data is available. This release contains the following changes: Briefly: Egypt now uses DST again, from April through October. This year Morocco springs forward April 23, not April 30. Palestine delays the start of DST this year. Much of Greenland still uses DST from 2024 on. America/Yellowknife now links to America/Edmonton. tzselect can now use current time to help infer timezone. The code now defaults to C99 or later. Fix use of C23 attributes. Changes to future timestamps Starting in 2023, Egypt will observe DST from April's last Friday through October's last Thursday. (Thanks to Ahmad ElDardiry.) Assume the transition times are 00:00 and 24:00, respectively. In 2023 Morocco's spring-forward transition after Ramadan will occur April 23, not April 30. (Thanks to Milamber.) Adjust predictions for future years accordingly. This affects predictions for 2023, 2031, 2038, and later years. This year Palestine will delay its spring forward from March 25 to April 29 due to Ramadan. (Thanks to Heba Hamad.) Make guesses for future Ramadans too. Much of Greenland, represented by America/Nuuk, will continue to observe DST using European Union rules. When combined with Greenland's decision not to change the clocks in fall 2023, America/Nuuk therefore changes from -03/-02 to -02/-01 effective 2023-10-29 at 01:00 UTC. (Thanks to Thomas M. Steenholdt.) This change from 2022g doesn't affect timestamps until 2024-03-30, and doesn't affect tm_isdst until 2023-03-25. Changes to past timestamps America/Yellowknife has changed from a Zone to a backward compatibility Link, as it no longer differs from America/Edmonton since 1970. (Thanks to Almaz Mingaleev.) This affects some pre-1948 timestamps. The old data are now in 'backzone'. Changes to past time zone abbreviations When observing Moscow time, Europe/Kirov and Europe/Volgograd now use the abbreviations MSK/MSD instead of numeric abbreviations, for consistency with other timezones observing Moscow time. Changes to code You can now tell tzselect local time, to simplify later choices. Select the 'time' option in its first prompt. You can now compile with -DTZNAME_MAXIMUM=N to limit time zone abbreviations to N bytes (default 255). The reference runtime library now rejects POSIX-style TZ strings that contain longer abbreviations, treating them as UTC. Previously the limit was platform dependent and abbreviations were silently truncated to 16 bytes even when the limit was greater than 16. The code by default is now designed for C99 or later. To build in a C89 environment, compile with -DPORT_TO_C89. To support C89 callers of the tzcode library, compile with -DSUPPORT_C89. The two new macros are transitional aids planned to be removed in a future version, when C99 or later will be required. The code now builds again on pre-C99 platforms, if you compile with -DPORT_TO_C89. This fixes a bug introduced in 2022f. On C23-compatible platforms tzcode no longer uses syntax like 'static [[noreturn]] void usage(void);'. Instead, it uses '[[noreturn]] static void usage(void);' as strict C23 requires. (Problem reported by Houge Langley.) The code's functions now constrain their arguments with the C 'restrict' keyword consistently with their documentation. This may allow future optimizations. zdump again builds standalone with ckdadd and without setenv, fixing a bug introduced in 2022g. (Problem reported by panic.) leapseconds.awk can now process a leap seconds file that never expires; this might be useful if leap seconds are discontinued. Changes to commentary tz-link.html has a new section "Coordinating with governments and distributors". (Thanks to Neil Fuller for some of the text.) To improve tzselect diagnostics, zone1970.tab's comments column is now limited to countries that have multiple timezones. Note that leap seconds are planned to be discontinued by 2035. Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2023a.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2023a.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2023a.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 f24b84a13556c12441dd55c323f9a8fd3b6fbbee dated 2023-03-22 12:39:33 -0700 and tagged '2023a' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: d45fc677a0a32ae807bf421faceff675565ee15e3ff42d3a4121df10e1f7855ac16b27fbc28bd365f93c57f40c5bdf19cde88546f7090cfab7676cac0a5516a4 tzcode2023a.tar.gz 10aadd6eba50f63f427399281065ba34cb474f6a854f8dc7a6f4f1343b1474a05f22b69b1e113ea67bb5f3f479253610a16b89d9dfa157bf0fde4c69aa3d6493 tzdata2023a.tar.gz 8e959f6cad84e9481ed5a6efcc8d7126d41fadfdc860715fea87fb15f7dcfdbc4c9d49828df2945ee9304dbdd3370c5b5048c62637bdd4f4962830ba101008bd tzdb-2023a.tar.lz Here are GPG digital signatures for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmQbXA8ACgkQ7ZfpDmKq fjSDXRAAjfD1GMYAFHDvXOlCCitgTsTjBBuPHPbrQ7gTWno9uX8bvss3aXCUslHv sfzCHMKhJqMXGLzSQQ5jEP/k4fOjNJyIQbVlrY9XljpdGeOdYa1E0zr95dIf4/ta NUY9XxzFnd3hwQuc6LY77MOv2Xyy/5RAGajD2DTpYTLjE0ffMFK371efs//GcLqe aCIWBdet1rJyih6CoyzfNvl6QHQOxZLSlE2E3DYu430fTi/UhmTcaATW8gRNulL5 kXamzD9l45/cGOx/jHP6CkJIqFTFV4W1/W/VyjIEgRE0KGbuQO3LV0avohjhmmwm hS6H6RJYfgeF+vwmo3unN+vUwPLhkPUiz2NO/Uf0n22AVQlUOrEP0XVXYW8aRd3H ewDrlvDCMkvmKqEb8k0jqbmjqTgeblKoqeS7gIShhVmrIli8oN4mguWg5WaeRWF/ l3uYtBXOg/DJMwENrB+4u0+PRWuR2T5OW/E4NvaKIu58qzozP7WEmlEwv9KWZB+z ffmNaVgXqSCz50K6gvhoDKLn5YBgpB9kXDd+YrcqPUAyD0sDWhBC2Hx9HHePOfQl dFB+ijja5HB8aZD/rX0iLrSwp/Ndt4l2QjXY9SMjTiWx4SgGGmGCANQqCDZGD31a C8bdEMH4qQeOPZ/NsPB6KaJsqALNroF07YeINu0YfWkw89ZF/r4= =mRAo -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmQbXA8ACgkQ7ZfpDmKq fjRngg/8D8E5sJIt412pmR7yIQYnsG44nSiELNpiewG+SF4DofW7quQDQEjDMdVn seLU9okE1/l+1SN6eibMJgvho/6HWkU9kWLzYCY29sljTVYqEu6vLo1IY1OJIkjC 9yieL33oLkN4LIeSMzR4QOCkRfusYNRYq3uryVtMu7R6HP2PgMlmmJf/imV192tj ONJXNA4Y30EvJ3lHuXMbr7fNg9hXSLjRy1NPKjp5OVZ3jZVXPljrC+egAfhLjZdQ uB5a3uGjAX+KjemCHwTmrrmmcUlaHxFxlfN5gX5cNIXuyrYtz0PAhy+MhBM5F9iY erYWg6EfBr7IfSyS1JcDZ1ypwZ66EpKxXfWZNm+HFA4dDdnWgvlM4n1OyKjw03Dq 4/agYr34cUDhfBUS57dtpZSibtdpbh8oiqxc+wXV3KZcHXVpX3XRyGTH1UVINfnF nXArC09JKUt7Tjol83TPH0jDXJAxabkgUDJHfpeQ5A8r3GNW1PQ/OF25ieRb+AFQ jWFbiEIxSXmUwnRc6wHiLX/gU0TT7vVMokN5erx9IGwrDEQAljuEJoj2bYFT/q9D 8jFA+48r/nK2r33+OBrz6aryoMNptquuMG0XR4aSr6KO3e622+vuF4nSN7hg2sAM /bMLSlzOGUEmOZ2D7hP5MDdWw5L0WQAjX7/8xKzdlMhqkx4Mc9Q= =OxWX -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmQbXBAACgkQ7ZfpDmKq fjQJaQ//aj78DFo7hiHX7VNnyEIKdddIApk6PKN6XkfCxVyXDxztE9w4Bf8LhYR2 hw0TFDtaIDpW0tb6OTQ/r/I2xMmeYKT52YPKL6KtKmc8tmzM4DiBT0CT/c//nxSl elxnuRI1wPbvP21XjuqbKBztN7ID1KC6YAs78045Cek+1K1lx5z9QcnYNLGIBwn3 EP4zi3qkMKQRKuT07ESQy4+y7hezPy9CPZMObmQ/v4nmUk0OIvbHGBK0TAc8D6kI Tsv1mAk4FHnbpbtpdXwfGDGpYfBs8giMHH6M+ZGdaT452hKrOwCgrvzsGlOxsxDc Ht4iASO78OEjdA/5cEscYYdoxOQCcTeDQEfWYx5bNfCFNvUKzrs79Qs1GaQ9riXW zdRBjW0sKbKZUoM9ZPjtYxRfh8PrZY9qDoZ4orF/39jl3SkBYkCC8IsKtEEVUYm/ ELH930IXmJ49sVdl+9ROGgqGUPcaVfouZf/+qf8d6HSEolOgrXe9FkB9E42RLBXw ETO/yL0MHPRiJU8U2agRV3AMiJoxM07ZvH54BgAsSXl1vr7xaCMqy5B38R7U/Tmj Sp7pqvtKhUcqyLHRi073GZmdV3pFhRsfAgiXTpRdNTAyJpN+y6jO9pZg6YYEfb+w kql/6Gp76ffGQU1j3OnvmVnmS22a34WiBZ0iYsKhrU/sym3Pk88= =SZ+n -----END PGP SIGNATURE-----

1 0

Summer Time in Palestine for 2023s year
by heba.hamad March 22, 2023

March 22, 2023

3 2

Re: [tz] [tzcode 2022g] Undeclared variable/typo in zdump.c
by Paul Eggert March 22, 2023

March 22, 2023

On 2023-03-22 02:55, panic wrote: > I contact you directly, because access to the mailing list is currently > very limited (new subscriber). Thanks, I'll include a copy of your email below, so that other subscribers of the tz mailing list can see it. > I try to cross-compile tzcode 2022g from GNU/Linux (NixOS) to Windows > using GCC 12.2.0 (x86_64-w64-mingw32) and get this compilation error: > >> In file included from zdump.c:14: >> zdump.c: In function 'zdump_tzalloc': >> zdump.c:264:38: error: 'initial_envptrs' undeclared (first use in this function); did you mean 'initial_nenvptrs'? >> 264 | if (ckd_add(&initial_nenvptrs, initial_envptrs, 1) >> | ^~~~~~~~~~~~~~~ >> private.h:414:51: note: in definition of macro 'ckd_add' >> 414 | # define ckd_add(r, a, b) __builtin_add_overflow(a, b, r) >> | ^ >> zdump.c:264:38: note: each undeclared identifier is reported only once for each function it appears in >> 264 | if (ckd_add(&initial_nenvptrs, initial_envptrs, 1) >> | ^~~~~~~~~~~~~~~ >> private.h:414:51: note: in definition of macro 'ckd_add' >> 414 | # define ckd_add(r, a, b) __builtin_add_overflow(a, b, r) >> | ^ >> make: *** [<builtin>: zdump.o] Error 1 > > I suspect `initial_envptrs` is a typo and should be `initial_nenvptrs`, > as the former does not occur anywhere else. > > Building natively for Linux works just fine. For cross-compilation, I > build additionally with > >> "CFLAGS+=-DHAVE_DIRECT_H" >> "CFLAGS+=-DHAVE_SETENV=0" >> "CFLAGS+=-DHAVE_SYMLINK=0" >> "CFLAGS+=-DRESERVE_STD_EXT_IDS" > > `-DHAVE_SETENV=0` selects the alternative path in `zdump_tzalloc` and in > combination with a recent GCC triggers error. Normally, `HAVE_SETENV=1` > and the code path is not compiled. Maybe the combination of a recent GCC > and > `-DHAVE_SETENV=0` is rarely tested and therefore the typo was not > discovered before. > > Cheers, > -- panic Thanks for the bug report. I've never built with that particular combination, and you exposed a couple of typos. I reproduced the problem artificially on GNU/Linux by building with "make CFLAGS='-DHAVE_SETENV=0'" and installed the attached patches. This fix should appear in the next release, which should be soon.

1 0

[PATCH] Pacify gcc -Wunused-parameter
by Paul Eggert March 22, 2023

March 22, 2023

* zdump.c (localtime_rz, tzfree): [! USE_LOCALTIME_RZ]: Mark unused args with ATTRIBUTE_MAYBE_UNUSED. Problem found when compiling with -DUSE_LTZ=0 on Fedora 37 with GCC 12.2.1 20221121 (Red Hat 12.2.1-4). --- zdump.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/zdump.c b/zdump.c index 77ecb18..88bcd3a 100644 --- a/zdump.c +++ b/zdump.c @@ -228,7 +228,7 @@ localtime_r(time_t *tp, struct tm *tmp) # undef localtime_rz # define localtime_rz zdump_localtime_rz static struct tm * -localtime_rz(timezone_t rz, time_t *tp, struct tm *tmp) +localtime_rz(ATTRIBUTE_MAYBE_UNUSED timezone_t rz, time_t *tp, struct tm *tmp) { return localtime_r(tp, tmp); } @@ -304,7 +304,7 @@ tzalloc(char const *val) } static void -tzfree(timezone_t initial_environ) +tzfree(ATTRIBUTE_MAYBE_UNUSED timezone_t initial_environ) { # if !HAVE_SETENV environ = initial_environ; -- 2.39.2

1 0

Time Zone Database
by EL MAAYATI Afaf March 22, 2023

March 22, 2023

Dear Paul, I'm Afaf EL MAAYATI from National Telecommunications Regulatory Agency in Morocco. Actually, in the current version of Time Zone Database (https://www.iana.org/time-zones) for Africa region, and especially for Morocco, it’s mentionned that a program will be running to implement the transition dates. According to this program, the next transition dates (during 2023) are as below : - March 19, 2023 (switching to GMT). - April 30, 2023 (switching back to GMT+1). In fact, we will switch back to GMT+1, advancing 60 minutes, on Sunday, April 23 at 2:00 a.m (not on April 30). Please refer to the official annoncement, published by the Ministry of Digital Transition and Administration Reform: https://www.mmsp.gov.ma/fr/actualites/passage-%C3%A0-l%E2%80%99heure-gmt-%C… So, would you please update the program, in order to consider « April 23 at 2:00 a.m » (for switching back to GMT+1). Thank you in advance for your feedback and for your habitual support. Thank you. Best Regards, Afaf EL MAAYATI National Telecommunications Regulatory Agency Morocco [https://www.anrt.ma/images/ANRT-Signature.jpg] ________________________________ Ce message, son contenu et toutes les pièces jointes sont adressés à l'attention exclusive de leur (s) destinataire (s) et sont strictement confidentiels : ils relèvent de la correspondance privée. Toute publication, utilisation ou diffusion, même partielle, par des personnes autres que les destinataires est interdite et doit être autorisée par l'Agence Nationale de Règlementation des Télécommunications (ANRT, Royaume du Maroc). Si vous recevez ce message par erreur, nous vous prions de le détruire après en avoir informé son expéditeur sans délai. L’ANRT décline toute responsabilité pour toute altération, déformation ou falsification subi par le message et ses pièces jointes au cours de leur transmission. Retrouvez toutes les informations de l’ANRT sur son site Web à l’adresse suivante : http://www.anrt.ma. ________________________________ This message, its content and its attachments are intended for the exclusive use of the named addressee (s) and are strictly confidential. Any copy or other use of this information by persons or entities other than the intended recipient is prohibited and should be authorized by the National Agency of Telecommunications Regulation (ANRT, Morocco). If you have received this communication in error, please delete the material and notify the sender. The ANRT accepts no liability for any alteration, distortion or falsification that may occur during the transmission of this message. All information about ANRT can be found on our website at the following address http://www.anrt.ma. ________________________________ إن هذه الرسالة ومحتواها ومرفقاتها موجهة خصيصا للشخص المرسل إليه وتعتبر سرية وتصنف ضمن خانة المراسلات ذات طبيعة شخصية. ويمنع منعا كليا نشر أو استعمال أو بث، ولو بطريقة جزئية، لهذه الرسالة من طرف أشخاص غير المرسل إليهم ما لم يتم الترخيص بذلك من طرف الوكالة الوطنية لتقنين المواصلات (المملكة المغربية. في حالة ما إذا توصلتم هذه الرسالة عن طريق الخطأ، يرجى منكم العمل على إتلافها فورا بعد إخبار الشخص المرسل إليه بذلك. ولا تتحمل الوكالة الوطنية لتقنين المواصلات أي مسؤولية عن أي تحريف أو تغيير أو تزييف قد يلحق بمحتوى الرسالة أو بمرفقاتها خلال عملية الإرسال. للمزيد من المعلومات، يرجى الاطلاع على الموقع الإلكتروني للوكالة الوطنية لتقنين المواصلات : http://www.anrt.ma.

2 3