- tz - lists.iana.org

Comments
by Arthur David Olson April 24, 2023

April 24, 2023

Fun fact: the time zone database is 80% comments by volume. @dashdashado

7 8

Mexico timezones
by Var Nazari April 10, 2023

April 10, 2023

Hello, Mexico has recently abolished daylight savings except for where they border with the United States. I believe the timezone database is now inaccurate because it should not be showing CDT for most of the country any longer and should be CST instead. It seems like this was addressed in release notes for the tzdb version 2022f and 2022g but I'm not sure that the correct changes were applied. Could you verify/explain why the timezones in Mexico are still recorded as CDT? Is this a mistake? Thank you

3 5

Changing 24:00 to 0:00 where possible
by Jacob Pratt April 5, 2023

April 5, 2023

While writing a parser for tzdb files, I noticed that some rules are for a given date at 24:00, rather than the following day at 0:00. While in some cases this is unavoidable (Egypt), in others there is no reason this is necessary (Belize). I think it would be reasonable to change 24:00 to 0:00 where possible, incrementing the day, day of week, and month as appropriate. This would reduce the need for special casing values to those that have a technical reason. Jacob Pratt

8 12

Error in the "America/Santiago" timezone for one week of September 2022
by Javier Ayala March 31, 2023

March 31, 2023

Hello, There is an error in the 'America/Santiago' timezone. The week between September 4th, 2022 and September 10th, 2022 should have the offset of -4.0, but it currently shows -3.0. This error occurred due to the 2022 Chilean national plebiscite <https://en.wikipedia.org/wiki/2022_Chilean_national_plebiscite>, which caused the government to postpone the scheduled time change by one week, from September 3rd to September 10th. Sources: - Decree in Chile's Official Gazette: https://www.diariooficial.interior.gob.cl/publicaciones/2022/08/13/43327/01… - News published in Chile's government website: https://www.gob.cl/noticias/ministerio-del-interior-informa-respecto-al-cam… Greetings, Javier Ayala

2 1

(no subject)
by Jack Bakaev March 29, 2023

March 29, 2023

Hello, Lebanon decided to postpone the DST till end of April instead of march 25-26 TZ complied then the cabinet of Ministers in Lebanon decided yesterday March 27 to revert to DST during the night of March 29-30. please do not revert Lebanon DST back to March 25-26! this will cause problems for those who who already complied with the postponement please revert to DST during the night of March 29-30. Jack Bakaev Internet Society - Lebanon Chapter Chapter Secretary

2 1

Re: [tz] [PROPOSED 2/2] Fix comments on Lebanon this week
by Paige Tummons March 29, 2023

March 29, 2023

Hi Paul, I'm reaching out regarding your request for comments<https://mm.icann.org/pipermail/tz/2023-March/032833.html> on the proposal to revert back to 2023a instead of updating 2023c to reflect the Lebanon DST change of 30 March. I've been working closely with medical centers in Lebanon to ensure that their healthcare systems are in continuous legal compliance with the government directives. We have been in close communication with Lebanese government authorities who legally consider the spring forward event to be on 30 March (with the jump being from 11:59:59 PM on 29 March to 01:00:00 AM on 30 March). We are strongly urging you to reflect this update in the 2023c file, to avoid the published tzdata file being in direct conflict with the government directive of the spring DST event in Lebanon happening on 30 March. The Prime Minister met with the cabinet yesterday, and together they agreed that Lebanon DST happens on the 30th of March. No government authorities consider the 26 March 2023 event to be the "true" DST time for Lebanon. Thanks, Paige Tummons

3 2

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

March 28, 2023

The 2023c release of the tz code and data is available. This release's code and data are identical to 2023a. In other words, this release reverts all changes made in 2023b other than commentary, as that appears to be the best of a bad set of short-notice choices for modeling this week's daylight saving chaos in Lebanon. (Thanks to Rany Hany for the heads-up about the government's announcement this week.) Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2023c.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2023c.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2023c.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 ddb8cf09d54ecc486ed6665edcdd642abccd4eef dated 2023-03-28 12:42:14 -0700 and tagged '2023c' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: fa18bae9c0e7c061bc9d5f5f2eb9967f0e4ddb2baafdee9887fa30cd0c60f4aa6f21eacffb17df0d59d26ff54d08c5dcefa98159309eba497e86443624913a82 tzcode2023c.tar.gz 608bd286ebcbd0004cfdc1da183273f08aff61f90c8867661154453d77a05d421e4c46ad6d066a1fe2e87d5c82ec0f1c0224667a3b35f3180a3eb7f6ff84cbf5 tzdata2023c.tar.gz b59dbfc598b98f325797ff587bd2e8b27aadc52924eeb0b26cd18cdaca56224c436a20950bc73de9b9b46e98d640a24d8cb797a8f49ada15ea2f42a70a6efe22 tzdb-2023c.tar.lz Here are GPG digital signatures for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmQjQ8MACgkQ7ZfpDmKq fjTp4BAAvitWlH49WQ+Cfs//1bBy7ifW1I5PNXSZFIDSNsZUGhrXOkZ/b6l3jAEF Z76GL7PQb5d/QHdKAIYeDheGnGf/8Wh4PFGzBkiyZgEdeZk6QLtE1n71Fu1x7gca IQOmVTzwVAf9f+fbizsaTarqg30TnPzUsuHiljInOaV8GkTt0VUkIZ5LeH09kdpY Rq6BIiehGikkBLyvCpyCTGZ4H8IKgR0GMkIHWQwj0mw/WROnT+xAfzTUrtD7zJK2 5+Ek2kj0UDB9DbprIkCZyh56W1OZ4m5OuAd9wHdx1ZOPfE6jq0lm+2B2kX4759mQ U66wyATu1qqqlc/2HUe464SWCyNTEDGbCCygfryInKd9Y+QORhK9yOsDfskVcGgX qTE2U20YzMqHP34fgTUsOC+mQ9e+qR1CvnCGAv3y1wpUIj1r9Opq7cI1uCvVE6xn nJhU1oE+z4HjhT2TZSS+gVM8D6p+z096sOkRnFg+mIh7XzSYYSFRojcGLnSAkg+o K68yPfXPu0subUGi5dH1XLQQYM0v0sqCATu5jKwU4YyyHoUuWDi9mooReAkSaj+y KON+VuYMRZZfJqzdc0HcXUsqlY/nK6/INRbtgvEKlMRLBn5oGbWIRnlyQvJA814v fsaewl80tRZAtXs/hwHrSGX1vxMkMaaDk5frG9BG/EkupBZa/rk= =fwRN -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmQjQ8MACgkQ7ZfpDmKq fjScAg/+LKVw3MFKXvXhDAJX9FPL+ZtvFc+XCwkAxylFA8rrLYjNTo+X7vdyu/AV 1YSkQFqPrPJrVMlffRm/NaQI59vOhkIQZ4Ingd0IFzfHIJMSMVU1C359mpUnxgce XLLUA12+Mjo3SEO/QYOZLhkpvzoJ2loPdgAUtraysunZdgYVdOubd8EpbWtZ/d9u cdKJriVWaHwcmEPXmZOcAhjTA2immhIrAd4G1FzuHFJNjdjIzJyXzxATWEk3mQ0z ZOQcpWGzf50OL9Atri4e8Nm4mXjguQHRebfYv8QVHAvxcdjGFc5yqvVrwGaNLGtV oadxHA3J/hmWS7mg7/pYDKabTNeoXrXWEzY8VXRbPnfvtbUXh9g4t9JDlgocHpQQ wAC3Hb/mvMFON68aCPWQeHxcHXOrAm2KHlGblJA9iI364S6v3iK7gd16lzZSbuTy G8jAt7YUilZxyIIV0GVMjQD9oG6bVm6ApccVVIBPHqlW1J09ON0koWRiNGqdbr8F BTh3ORBCo0qU+BvYF6mL9SCIrbGUvr4NdwY9aKaB04HPZz244fD2kLPt1z5v+7K6 cQrhdVQ6CqejhlJXRm4cQdeEzJhgxw+cFc256e8WpoofVu5rDws2d2KQZkqHGiFH A5jSKg2PWfZcqPoTdRg19DlUUdDBH8xybXzK5ExjHdDDO7KInGU= =XC0E -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmQjQ8QACgkQ7ZfpDmKq fjS96g//dxNELnczZASWUk7n+EJ5EbMjamjOOAde6r/Mpy/71DLg0AatISKt+Ph+ 7lAVzQRip6o4mZNZb9PZ6yP3r1rYKUymaOahtiwv5oC2lSmm2jCMRlFslHJ/feQc czOfCfd7ggpmg95Iqx81WYfc2lSbXzNArpvqBEjApqtkOLbpJ7A7s2JFn7o3lnD2 E1gMeiIbM4doq2Dfqzc3sJ2kyn/zmsA2g/HO64DZ9RUiDJlbOAZctIAfDiSkHE8q MTdSIVlKrOXDzmzvN1YMXyIPbo4ZaFCjvSZ5xbEpu8nf1IrLq0WqkU41T+4cq3zD Vq0NHrADU49npWh1qn/PTJunln6I6BHIXzyDAAZL+Ij1lcplRh/ZdszZBxU267Qx 6rvEqeea1jQPEKS2/x9aMSWk4mwooB1pYHjnpgS+ZP1CLHtrWVtf5zU4Z2sODWBd p1otOWWgR1nq7b4qc0OZwwVzuJN8rtptEf0PuxgKZnLLoVmgEpU5WxA5FjhTsJmm 1nbv676DfIN31NOfSGcP12Lcp2KjZ2Cfj++zmQruTlZcjpWYEJiRjiecqELBWo7S jw96jrEUQi6mVn6jhzV0Sxdiig9M0hmzMj0bcx2BvldbUFCbZscAproR9fHeqpZM Q4F6QphFyP5Y3kBKARZZ3HmM6Kc5ZWkG6WzLeTkTdcxqHZLrp8c= =YTzD -----END PGP SIGNATURE-----

1 0

[PROPOSED 1/2] Adjust attribution at Jad Baz’s request
by Paul Eggert March 28, 2023

March 28, 2023

--- NEWS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/NEWS b/NEWS index fe0e809..f400425 100644 --- a/NEWS +++ b/NEWS @@ -5,7 +5,7 @@ Unreleased, experimental changes Changes to past and future timestamps Model Lebanon's DST chaos by reverting data to tzdb 2023a. - (Thanks to Jad Baz for the heads-up.) + (Thanks to Rany Hany for the heads-up.) Release 2023b - 2023-03-23 19:50:38 -0700 -- 2.39.2

8 26

Policy Suggestion: Minimum time period betwen releases
by Howard Hinnant March 28, 2023

March 28, 2023

Recent events have brought to my attention the need to put a damper on chaos caused by poor planning. When governments give little notice to changes in time zone rules, this is not a problem that this group can fix, or should even try. I propose a minimum period of 30 days between successive IANA tz database releases. The train leaves the station no more frequently than once every 30 days (and will probably be less frequent). Whatever information is solid before the release date makes it on the train. Otherwise it can wait another 30 days (at least). My recommendation is in part based on this common statement: Poor planning on your part does not constitute an emergency on my part https://www.incirlik.af.mil/News/Commentaries/Display/Article/303134/poor-p… This week’s chaos isn’t unusual. In fact it is normal, especially for some countries. If they can’t be bothered to make a plan in advance and stick with it, I don’t see why this group of volunteers needs to compensate for that. Let the politicians lie in the beds they make. Howard

11 16

Reversal of timezone database file 2023b
by Roy Saad March 28, 2023

March 28, 2023

Dear Coordinator, The Lebanese government has reversed the decision to delay the shift to daylight savings time by a month (As per the articles below). Kindly update the time zone database to reverse the changes made in 2023b. (Sorry for the inconvenience created by incompetent public servants) https://www.bbc.com/news/world-middle-east-65090888 https://news.sky.com/story/lebanon-time-row-government-reverses-controversi… https://www.washingtonpost.com/world/2023/03/27/lebanon-daylight-saving-tim… Thank you and best regards, ROY SAAD Partner & Strategic IT Advisor 9th Fl., Confidence Centre, st. 15 , Sin El Fil, Metn 27076117, Lebanon T: +961 1 493 503 F: +961 1 489 172 M: +961 3 518230 www.trisq.com

1 0