December 2020 - tz - lists.iana.org

Re: [tz] Change Request: Europe/Kiev to Europe/Kyiv
by John Hawkinson 18 Mar '22

18 Mar '22

I do not think we have handled this well; we have not given Victor Perov a good answer. Indeed, to some extent we've made it a "runaround." We can do better. We should take the time to write up a good lengthy explanation of the issues ("boilerplate"), because this a really important issue of concern to many people in the world and the project has indeed thought about it pretty carefully. Dismissing the inquiries because they are repetitive makes it seem like we haven't, and that unnecessarily upsets peopl. Victor Perev: I don't have time for a full write-up right now, but please consult the archives of the tz list (http://mm.icann.org/pipermail/tz/ or perhaps https://www.google.com/search?q=site%3Amm.icann.org%2Fpipermail%2Ftz%2F+kyiv which returns 203 results). The tz project is very conservative in its judgment for when the predominant English spelling of a city has changed, and so far the project has judged that Kiev is still preferred. We discussed it when major English newspapers and style guides changed from Kiev to Kyiv last year (prompted by the US presidential impeachment, which lead to a lot of discussion about Kyiv in America), and we will probably continue to discuss it as time goes on. But we've thought about it and discussed it a lot. The answers you got don't explain that, and that means we have not done a good a job as we should have. Sorry about that. In particular, I think Brian Inglis's answer was actually incorrect in a way that really matters ("Kiev is the correct English spelling"). There are multiple correct English spellings. It used to be that Kiev was the only one, but Kyiv is gaining popularity more and more. Paul Eggert <eggert(a)cs.ucla.edu> wrote on Sat, 15 Aug 2020 at 18:19:08 EDT in <cefc7f01-a3e9-f2a4-9ab9-5288147f994a(a)cs.ucla.edu>: > Thanks for bringing that to the mailing list (if I could shut off GitHub > pull requests I would). Although you cannot do so, we can handle them a little bit better. Please see https://docs.github.com/en/github/building-a-strong-community/creating-a-pu… You can create a template that explains to a would-be pull request submitter than pull requests will be closed and the project uses the mailing list for development discussions. ("I understand that the tz project does not use pull requests on github, and that if I enter a pull request here, it will be closed and I will be directed to send email to tz(a)iana.org.") For the particular case of regular, recurring issues, it may be worth while to keep one of #15, #26, and #27 open and mark the others as a duplicate of it, so that it is easier for newcomers to understand that this issue has been carefully considered and is not a simple oversight. https://github.com/eggert/tz/pulls?q=kiev Also, not to pick on Brian (again), but if the project policy is not to use github pull requests, it's not great to respond to pull requests on their substance, because it bifurcates the discussion and makes it seem like we actually do use pull requests ("except when we don't"). So what seems like a helpful thing may not be. -- jhawk(a)alum.mit.edu John Hawkinson

10 13

Italy April 1944 discrepancy between comment and data
by Alois Treindl 05 Oct '21

05 Oct '21

For Italy in 1944 zone Europe/Rome there is a discrepancy between the comment and the data. comment: # From Paul Eggert (2016-10-27): # Go with INRiM for DST rules, except as corrected by Inglis for 1944 # for the Kingdom of Italy. This is consistent with Renzo Baldini. # Model Rome's occupation by using C-Eur rules from 1943-09-10 # to 1944-06-04; although Rome was an open city during this period, it # was effectively controlled by Germany. Data for Italy is Rule Italy 1944 only - Apr 2 2:00s 1:00 S Data for C-Eur is: Rule C-Eur 1944 1945 - Apr Mon>=1 2:00s 1:00 S where Mon>=1 in 1944 is April 3. So Rome is NOT following C-Eur. I think the rule for Itay is right, only the comment is misleading.

4 9

FW: [Ext] The TZ Coordination
by Naela Sarras 02 Apr '21

02 Apr '21

Dear Paul, Please see the note below from our colleagues in Morocco regarding the upcoming timezone change for Morocco. Best regards, Naela Naela Sarras Director, IANA Operations ICANN From: EL MAAYATI Afaf <afaf(a)anrt.ma> Date: Wednesday, May 27, 2020 at 12:01 PM To: Naela Sarras <naela.sarras(a)iana.org> Cc: BENLEMLIH Hamida <benlemlih(a)anrt.ma> Subject: [Ext] The TZ Coordination Dear Naela, I hope this email finds you well, safe and healthy. Actually, I have a request concerning the configuration of the Time-Zone for Morocco. In the Database file: ftp://ftp.iana.org/tz/tzdb-2020a/africa, it’s mentionned that a program will be running to implement the transition dates: [cid:image001.jpg@01D6342E.01C70B10] Currently we are implementing GMT and we will move to GMT+1 next Sunday, May 31. So, if possible, would you please help to get in touch with Mr. Paul Eggert, in order to have the procedure to notify IANA officially, from a governmental source, with the changes of TZ in Morocco. Thank you in advance for your feedback and for your habitual support. Best Regards, Afaf ________________________________ 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.

9 16

Some time zone history (3)
by P Chan 02 Mar '21

02 Mar '21

Correction: > British Guiana/Guyana adopted GMT-4 on 1911-08-01, GMT-3:75 on 1915-03-01, GMT-3 on 1975-08-01 and GMT-4 on 1992-03-29. GMT-3:75 should be GMT-3:45 --------- Most of the documents below were obtained from British Online Archives and LLMC Digital. ---------- Barbados https://1drv.ms/u/s!AgX5Bc6Y-VsIi3ioucfhJMcNlHr_?e=wjYyQa Definition of Time Act, 1911 (1911-7) [1911-08-28] Defence (Daylight Saving) Regulations, 1942, 1942-04-13 Defence (Daylight Saving) (Repeal) Regulations, 1942, 1942-08-22 Defence (Daylight Saving) Regulations, 1943, 1943-04-16 Defence (Daylight Saving) (Repeal) Regulations, 1943, 1943-09-01 Defence (Daylight Saving) Regulations, 1944, 1944-03-21 Defence (Daylight Saving) (Repeal) Regulations, 1944, 1944-04-30 Standard time of GMT-4 was adopted in 1911. DST was observed in 1942-44. The transitions were: 1942-04-19 05:00 GMT 1942-08-31 06:00 GMT 1943-05-02 05:00 GMT 1943-09-05 06:00 GMT 1944-04-09 05:00 GMT 1944-09-10 06:00 GMT --------- Gambia https://1drv.ms/f/s!AgX5Bc6Y-VsIi0MbGvyuIXGge6Iq Interpretation Ordinance, 1914 (No. 12 of 1914) [1914-09-29] Interpretation Ordinance, 1933 (No. 10 of 1933) [1933-03-31] Notice No. 5 of 1942, Colony of the Gambia Government Gazette, Vol. LIX, No.2, 1942-01-15, p 2 Interpretation (Amendment) Ordinance, 1946 (No. 3 of 1946) [1946-07-15] Standard time of GMT-1 was adopted on 1933-04-01. On 1942-02-01, GMT was adopted as a war time measure. This was made permanent in 1946. --------- Malawi https://1drv.ms/f/s!AgX5Bc6Y-VsIi0sbGvyuIXGge6Iq Interpretation and General Clauses Ordinance, 1911 (No. 12 of 1911) [1911-07-24] Notice No. 124 of 1914, 1914-06-30, The Nyasaland Government Gazette, Vol. XXI, No. 8, 1914-06-30, p 122 Interpretation and General Clauses (Amendment) Ordinance, 1925 (No. 3 of 1925) [1925-04-02] In 1911, Zomba mean time was adopted as the legal time of Nysaland. In 1914, Zomba mean time switched from GMT+2:21:10 to GMT+2:21. On 1925-07-01, GMT+2 was adopted. ---------- Nigeria https://1drv.ms/f/s!AgX5Bc6Y-VsIi0cbGvyuIXGge6Iq Government notices for the transition in 1905 and 1908. Government Notice No. 427 of 1905, 1905-06-17, Government Gazette. Colony of Lagos, No. 32, 1905, 1905-06-21, p 395 Government Notice No. 742 of 1908, 1908-06-24, Government Gazette. Colony of Southern Nigeria, No. 44, Vol. 3, 1905-06-24, p 869 ---------- Sierra Leone https://1drv.ms/f/s!AgX5Bc6Y-VsIi1EbGvyuIXGge6Iq Government Notice No. 121 of 1913 , 1913-06-06, Sierra Leone Royal Gazette, Vol. XLIV, No. 1384, 1913-06-14, p 347 Alteration of Time Ordinance, 1932 (No. 34 of 1932) [1932-12-01] Alteration of Time (Amendment) Ordinance, 1938 (No. 25 of 1938) [1938-11-24] Defence Regulations (No. 9), 1939 (Regulations No. 9 of 1939),1939-09-05 Defence Regulations (No. 11), 1939 (Regulations No. 11 of 1939), 1939-09-27 Defence (Amendment) (No.17) Regulations, 1941 (Public Notice No.157 of 1941), 1914-12-04 Alteration of Time (Amendment) Ordinance, 1946 (No. 2 of 1946) [1946-02-07] Standard time of GMT-1 was adopted on 1913-07-01. Twenty minutes of DST was introduce in 1932 and was suspended in 1939. In 1941, GMT was adopted by Defence Regulations. This was made permanent in 1946. For DST in 1957-62, I have looked through the gazettes from 1957 to 1961 but could not find any laws or notices related to DST. Also, the Local Time Ordinance (Cap 2, 1960 Revised Edition) <https://books.google.com/books?id=B-U-AQAAIAAJ&pg=PA18> does not contain any provisions related to DST. Proposed Rules: # Rule NAME FROM TO - IN ON AT SAVE LETTER/S Rule SL 1932 only - Dec 1 0:00 0:20 -0040 Rule SL 1933 1938 - Mar 31 24:00 0 -01 Rule SL 1933 1939 - Aug 31 24:00 0:20 -0040 Rule SL 1939 only - May 31 24:00 0 -01 Rule SL 1939 only - Sep 5 0:00 0 -01 Zone Africa/Freetown -0:53:00 - LMT 1882 -0:53:00 - FMT 1913 Jul 1 # Freetown Mean Time -1:00 SL %s 1941 Dec 6 24:00 0:00 - GMT

2 5

Some time zone history (2)
by P Chan 20 Feb '21

20 Feb '21

Bahamas There were two periods of DST observed in 1941-1945: 1941-05-01 midnight to 1944-12-31 and 1945-02-01 to 1945-10-17 midnight. War Time Order 1942 [1942-05-01] and War Time (No. 2) Order 1942 [1942-09-29] Appendix to the Statutes of 7 George VI. and the Year 1942. p 34, 43 https://books.google.com/books?id=5rlNAQAAIAAJ&pg=RA3-PA34 https://books.google.com/books?id=5rlNAQAAIAAJ&pg=RA3-PA43 War Time Order 1943 [1943-03-31] and War Time Order 1944 [1943-12-29] Appendix to the Statutes of 8 George VI. and the Year 1943. p 9-10, 28-29 https://books.google.com/books?id=5rlNAQAAIAAJ&pg=RA4-PA9 https://books.google.com/books?id=5rlNAQAAIAAJ&pg=RA4-PA28 War Time Order 1945 [1945-01-31] and the Order which revoke War Time Order 1945 [1945-10-16] Appendix to the Statutes of 9 George VI. and the Year 1945. p 160, 247-248 https://books.google.com/books?id=5rlNAQAAIAAJ&pg=RA6-PA160 https://books.google.com/books?id=5rlNAQAAIAAJ&pg=RA6-PA247 ---------- Guyana British Guiana/Guyana adopted GMT-4 on 1911-08-01 , GMT-3:75 on 1915-03-01, GMT-3 on 1975-08-01 and GMT-4 on 1992-03-29. The Official Gazette of British Guiana. (New Series.) Vol. XL. July to December, 1915, p 1547 https://books.google.com/books?id=5-5CAQAAMAAJ&pg=SA1-PA547 Interpretation and general clauses (Amendment) Act 1975 (Act No. 27 of 1975) [1975-07-31] https://parliament.gov.gy/documents/acts/10923-act_no._27_of_1975_-_interpr… Interpretation and general clauses (Amendment) Act 1992 (Act No. 6 of 1992) [1992-04-18] https://parliament.gov.gy/documents/acts/5885-6_of_1992_interpretation_and_… Circular No. 10/1992 dated 1992-03-30 https://dps.gov.gy/wp-content/uploads/2018/12/1992-03-20-Circular-010.pdf ---------- Nigeria On 1914-01-01, standard time of GMT+0:30 was adopted for the unified Nigeria. Colonial Reports - Annual. No. 878. Nigeria. Report for 1914. (April 1916), p 27 https://libsysdigi.library.illinois.edu/ilharvest/Africana/Books2011-05/306… Interpretation Ordinance, 1914 (No. 4 of 1914) [1914-10-01] https://books.google.com.hk/books?id=mm5CAQAAMAAJ&pg=PA172 In 1919, standard time was changed to GMT+1. Interpretation Ordinance (Cap 2) The Laws of Nigeria, Containing the Ordinances of Nigeria, in Force on the 1st Day of January, 1923, Vol.I p 5-18 https://books.google.com.hk/books?id=BOMrAQAAMAAJ&pg=PA16 For the standard time used in Lagos before 1914, the Interpretation Ordinance of Southern Nigeria, 1908 revised edition defined “Time” to mean Greenwich time. That section was originated from Proclamation No. 11 of 1905 of the Protectorate of Southern Nigeria. But the Colony of Lagos was not merged into Southern Nigeria until May 1906. Moreover, the 1906 Report of Southern Nigeria says “all laws in force in any part of the territory prior to the commencement of the new system of government shall continue in force until further provision is made by the local legislature.” Lloyd's Register of Shipping (1915) says “Hitherto the time observed in Lagos was the local mean time. On 1st January, 1914, standard time for the whole of Nigeria was introduced … Lagos time has been advanced about 16 minutes accordingly.” Therefore it is possible that no standard time was adopted in Lagos until 1914. Interpretation Ordinance (Cap 2) Laws of the Colony of Southern Nigeria : being the schedule to the Statute laws revision ordinance, 1908, Vol.I, p 3-11 https://babel.hathitrust.org/cgi/pt?id=mdp.35112105426037&view=1up&seq=61 Colonial Reports - Annual. No. 554. Southern Nigeria. Report for 1906. (February 1908), p 43 https://libsysdigi.library.illinois.edu/ilharvest/Africana/Books2011-05/306… Lloyd's Register of Shipping. 1915-16. Vol. II.-Appendix. ,p 655 https://books.google.com/books?id=b_ROAQAAIAAJ&pg=PA655 ---------- Seychelles Standard Time was adopted on 1907-01-01. Standard Time Ordinance (Chapter 237) The Laws of Seychelles in Force on the 31st December, 1971, Vol. 6, p 571 https://books.google.com/books?id=efE-AQAAIAAJ&pg=PA571 ---------- Turks and Caicos Islands Standard Time Declaration Order 2015 (L.N. 15/2015) http://online.fliphtml5.com/fizd/czin/#p=2 Standard Time Declaration Order 2017 (L.N. 31/2017) http://online.fliphtml5.com/fizd/dmcu/#p=2 ---------- Vanuatu DST was observed in 1973/1974. The spring forward in 1984 should be on Sep 23. Joint Daylight Saving Regulation No 59 of 1973 New Hebrides Condominium Gazette No 336. December 1973 http://www.paclii.org/vu/other/VUNHGovGaz//1973/11.pdf#page=15 Joint Daylight Saving (Repeal) Regulation No 10 of 1974 New Hebrides Condominium Gazette No 336. March 1974 http://www.paclii.org/vu/other/VUNHGovGaz//1974/3.pdf#page=11 Summer Time Act No. 35 of 1982 [1983-09-01] http://www.paclii.org/vu/other/VUGovGaz/1982/32.pdf#page=48 Summer Time Act (Cap 157) Laws of the Republic of Vanuatu Revised Edition 1988 http://www.paclii.org/cgi-bin/sinodisp/vu/legis/consol_act1988/sta147/sta14… Summer Time (Amendment) Act No. 6 of 1991 [1991-11-11] http://www.paclii.org/vu/legis/num_act/sta1991227/ Summer Time (Repeal) Act No. 4 of 1993 [1993-05-03] http://www.paclii.org/vu/other/VUGovGaz/1993/15.pdf#page=59

4 11

zic bug: Wall-clock ordering of transition times
by Tim Parenti 04 Jan '21

04 Jan '21

I noticed a bug while incorporating changes to commentary for the Turks and Caicos Islands… https://mm.icann.org/pipermail/tz/2020-December/029609.html Our contemporaneous use of "3:00" in the UNTIL field for the 2018-03-11 change intentionally avoided two clock changes in a row (first from 01:59:59 AST to 01:00:00 EST, then from 01:59:59 EST to 03:00:00 EDT an hour later). https://github.com/eggert/tz/commit/8792d7bed2c684cf842592fd7779645f335a33f6 My recently-added commentary clarifies the reasoning behind this and concludes that the order was likely intended to take effect from 03:00 -04, once the Eastern US had sprung forward, and not at 02:00 -04 as the text suggests. However, I noticed that using "2:00" in the UNTIL field instead doesn't actually result in the expected extra transition: --- to2050.tzs 2020-12-05 14:11:12.000000000 -0500 +++ to2050new.tzs 2020-12-05 14:17:31.000000000 -0500 @@ -5201,7 +5201,7 @@ 2014-03-09 03 -04 EDT 1 2014-11-02 01 -05 EST 2015-03-08 03 -04 AST -2018-03-11 03 -04 EDT 1 +2018-03-11 02 -04 EDT 1 2018-11-04 01 -05 EST 2019-03-10 03 -04 EDT 1 2019-11-03 01 -05 EST It seems that, the 02:00 wall-clock time having already been approached once for the transition out from AST, zic assumes that the transition specified in the US Rule at the same wall-clock time has also taken simultaneous effect in Eastern Time, although in reality it wouldn't yet for another hour. In this case, the wall-clock times of these two transitions are identical, while in actuality the transitions are meant to take effect sequentially. It appears that this bug also manifests in other cases where the strict ordering of transitions does not exactly match the strict ordering of wall-clock times: Trying out "2:30" in the UNTIL field should mean that the Zone transition should happen 30 minutes BEFORE the US Rule would take effect (and thus require two transitions), but by wall-clock time, it would "appear" to be 30 minutes AFTER (fooling zic into thinking only the "latter" Zone transition is needed as the Rule would have "already" taken effect). And, indeed, the results are similarly incorrect here, too: --- to2050.tzs 2020-12-05 14:11:12.000000000 -0500 +++ to2050new.tzs 2020-12-05 14:36:07.000000000 -0500 @@ -5201,7 +5201,7 @@ 2014-03-09 03 -04 EDT 1 2014-11-02 01 -05 EST 2015-03-08 03 -04 AST -2018-03-11 03 -04 EDT 1 +2018-03-11 02:30 -04 EDT 1 2018-11-04 01 -05 EST 2019-03-10 03 -04 EDT 1 2019-11-03 01 -05 EST Certainly an edge case in this particular instance, but given that many historical transitions coincide tightly with transitions in other regions being "joined" or "left", perhaps one worth a further look. -- Tim Parenti

5 16

No Scottish time zone in the 1990s
by Clive D.W. Feather 30 Dec '20

30 Dec '20

An interesting (for us on TZ) little bit of history. https://www.bbc.co.uk/news/uk-50950961 "National archives: Sir John Major snubbed separate Scottish time zone" -- Clive D.W. Feather | If you lie to the compiler, Email: clive(a)davros.org | it will get its revenge. Web: http://www.davros.org | - Henry Spencer Mobile: +44 7973 377646

1 0

[tz-announce] 2020f release of tz code and data available
by Paul Eggert 29 Dec '20

29 Dec '20

The 2020f release of the tz code and data is available, reflecting the following change to the build procedure: 'make rearguard_tarballs' no longer generates a bad rearguard.zi, fixing a 2020e bug. (Problem reported by Deborah Goldsmith.) There are no changes to the data since 2020e. The build-procedure change was circulated on the tz mailing list and is intended for downstream consumers that can process only rearguard format. Please see the PS at the end of this email for more info about rearguard format. Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2020f.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2020f.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2020f.tar.lz As usual, links to the latest release files are here: 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 846c3ac7abc246094dd754ac6dc90423148a5107 dated 2020-12-29 00:17:46 -0800 and tagged '2020f' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 5f6bf1b508434842eb9dacacc744b5f3375c35b88e401ef372b5fde80ad2f523484fe52a6e99460e402230406ebf6a9261a97efde45a610f8e8085893d55c4ed tzcode2020f.tar.gz dd312def18c807452fda2e697514e2064c5f51ebdbedd0cfe6f231252c76ee5d4409f653b295ed5657b7d30b868690047fdb70a10942e69eaa40b77473e3f9ca tzdata2020f.tar.gz a2efd9cb6308c75de382ff1ddc524dad5da10d76d86c6bf41ab2f979fffae1356b2599b3fcc045eab1cb56b16f9371663da5be57c1f43591517be62e65abbf1c tzdb-2020f.tar.lz Here are the GPG digital signatures for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAl/q5ukACgkQ7ZfpDmKq fjSOqA//d2SuaDA9HEXuGXOgTV2f9Iu8x4XF3cIc/UYIh/9yi7T1jVhRD70rPjTO 0g1ohBPoT/oY5OaFholMuZfoIwNgPv2K4c05xNrmNdbbz/3iaddm1zpD5WutRw2c u+hqrR1C5p/ICoSEH+/SAwmBFYEpQYCnkFUScC7YeGoZzzpKls3l/8hvUFaKt8SW ssgS/nVA3L54W8Hdu8WUl2Nz7xmkN3zzRseZMsU3+CrUwXtGzyySZPAJR1Ryk1ee PgwZaoteeGFl08Y7QfvyZBc7xakgnMEdhFB+m2SH//RO6DLjjuWlSAV9wMCk6dZq Uu3yZDVfsV91kiXOavdZFGXQCGXFVmkU7cZnSlpGWuIQGDX0iLOdcuWTFSEw+Av6 UP0cKyX2gJdXaqsYaBpgkCNh0SzG8ui5sS+vimCXG0+0d3z5ru2sHOTSkDxAke6a Jbs5PCz4HXpkIbbE73j+GzaoGWvbzqIledXV+J18uOAcfX13Ejft1nMFyZYh2vvJ 3DH3j1KA0NMs1u9o2F3HWPQcGZKuLFg0BxU2hEeIqbEwXAs980Mo5xrDtFRk4VLy Sg/o6XiREeXV06gXLqlP0vKa+qf88J9u18wMuuiPX1NmNZOcdekVVZtYQ5VhDjbZ xcg3S7YG9HUB+SxnAWQ21jaioQPLYB0Sc2/2vo8VzvIDE9iy8FI= =WeIr -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAl/q5ukACgkQ7ZfpDmKq fjQ8ug//WH7DpYFvSYMKpSj6gG0m5lK0JXcs062EKGQNsVoUjSVImu3VPbpUS9tu cO3NCUmeqTmwhUOuZQN2qGAT2KyNhcLTlza8xuRQm/tJ7SYpArseY9rudQtkjbCi uWELQi5+a6CA/PBBRJzDJwQPTf4wDZr24vDd29tKqBho5T5cisudXHhqh1Bm0Bfr NPyPsS6+oLJofIVsU0I5V+fbnU98ny5I1r/OyVIJgAlvEcb0kMDr0fBfu1dNvJI9 Tyl3kvdLSMCgf/lRXEFYJpI0RuUeIAsOvHaSwSCHKGc7FHzgDiK1U5D/4z5Ipo02 0AQKkLFkEbzwou/5KtX2Q3+yba1AGu64C7elu+aKepUNGhkzAaJrl2xNNM25Sdn4 1WvxOt43GTIze0cr9UHm942sU5UxH0ahv4h9pEbqJ44UVzBhuDDqcMXYJEWhdhMf 6dgRA7SJThuX7tN758to9Ze9XyXMdzAPdJKs/wyLrRGyDq0dXlRTVPL4Nk9ZqRQh FYJlOhM2TGSg7VsNgn8gneODaaQJpJ7jVSIwicQtWES2K2oblrFz4LSeXm39xZDc 0JRNh/fSeRygCGrjD7CLqq88UGTxhEuZbEXKXSPMLC+7j7JF/CmCVj8HjNw8M3Cy uk/Tfamala66AGltxPwKchTPBJH8F4tZy+4krfYXByoIX5h+Ta4= =Fk0g -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAl/q5usACgkQ7ZfpDmKq fjSp4A//aoSQ/VDoYZhE5F7PXV+td9DTVGABdA6ubQppymgX8uJvuBgk46pDRmVw Yba4dVcblTzjbCNDCBf9+nkgj46hGdql10t9bjgBDKf5MVQwp8hDyQfj3qbJciBD E0JSMXw3JQpuK1YVqxTXldINxtaSaLJUhYh1inBmEs8uX+vrwzURmYhF7NLoG7GL ymClE3BAJwkNXuRJ4tAMhEaANdShnre+uJWWW7DeNZPrHVKhSSD7IyAWin3vNUEj FA3ELERWgTVbkpmsUUH+5VtUIp8dE9jGxzgaPfy4KmuN0D4qiEgjSg23AFZDWqwF jDX2OlQl7J9oQfeUUBooee1S6IkVCC0+WNJPhSjeeKV8CUBBT5YKtTAgnx14bgkc nL01dF49WxA2MrQMWd794jh6dpMwDzdWw4gdEMLoiSOKRpO5E5iHzjM7c0WWyrGl Hqh6ZmBZz+17wBFSd7QQtLpwWajl+yGgSONJcw0cnvdjleJ6m89vcdzsrsD55ONT uRZK1TEaZqYG6U6lk/XxDsVQiC1CQ9/vWOPT8bhd2wdIhf9g0skN+MNachKQfs11 9Xn+pfMk79Vgatbbq9rDk0F3v6gRjayYRDtcVCFoOmrdXWmRhQtvyerm6wCILsFU gWpdS8tIo/4dwbypyot/5fe0ZEUBJGfbe7PSZu7a64DTgecE5R8= =mWt8 -----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 rearguard_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

Joda-Time compiler broken again
by Stephen Colebourne 28 Dec '20

28 Dec '20

The latest 2020e release broke the Joda-Time compiler again. https://github.com/JodaOrg/joda-time/runs/1607329443?check_suite_focus=true… Presumably, some rule now contains a 31 in a 30 day month now? Stephen

5 8

[tz-announce] 2020e release of tz code and data available
by Paul Eggert 27 Dec '20

27 Dec '20

The 2020e release of the tz code and data is available. It reflects the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes: Briefly: Volgograd switches to Moscow time on 2020-12-27 at 02:00. Changes to future timestamps Volgograd changes time zone from +04 to +03 on 2020-12-27 at 02:00. (Thanks to Alexander Krivenyshev and Stepan Golosunov.) Changes to past timestamps Correct many pre-1986 transitions, fixing entries originally derived from Shanks. The fixes include: - Australia: several 1917 through 1971 transitions - Bahamas: several 1941 through 1945 transitions - Bermuda: several 1917 through 1956 transitions - Belize: several 1942 through 1968 transitions - Ghana: several 1915 through 1956 transitions - Israel and Palestine: several 1940 through 1985 transitions - Kenya and adjacent: several 1908 through 1960 transitions - Nigeria and adjacent: correcting LMT in Lagos, and several 1905 through 1919 transitions - Seychelles: the introduction of standard time in 1907, not 1906 - Vanuatu: DST in 1973-1974, and a corrected 1984 transition (Thanks to P Chan.) Because of the Australia change, Australia/Currie (King Island) is no longer needed, as it is identical to Australia/Hobart for all timestamps since 1970 and was therefore created by mistake. Australia/Currie has been moved to the 'backward' file and its corrected data moved to the 'backzone' file. Changes to past time zone abbreviations and DST flags To better match legislation in Turks and Caicos, the 2015 shift to year-round observance of -04 is now modeled as AST throughout before returning to Eastern Time with US DST in 2018, rather than as maintaining EDT until 2015-11-01. (Thanks to P Chan.) Changes to documentation The zic man page now documents zic's coalescing of transitions when a zone falls back just before DST springs forward. Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2020e.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2020e.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2020e.tar.lz As usual, links to the latest release files are here: 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 efc5c061920f1d5820d66b7ec88ebff144c55b3f dated 2020-12-22 15:14:34 -0800 and tagged '2020e' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 37656ee4400f6e7ac8b3d4b515ea2ae940de05e8a95873112a4ec08afc11227214f269e4ef1bedb0389497958dd07a6d4721191e441920bc45c235b029a8a885 tzcode2020e.tar.gz 1e64b5c91b9e56923cf8e3e079781c59c8afb6c379b38b9b91ef493929814d50c29a6368cfcf77db08a7af3b6876387bac5617f64ac965a5bddab436d17862c4 tzdata2020e.tar.gz 77e62a3717d179b13f35710dedd87d780649edf6c338c056e41ba58d49225e512074a5fbfa3ae52242bea6b28d1a08bb0e2b07ff7a3aed031dc9d357dac34170 tzdb-2020e.tar.lz Here are the GPG digital signatures for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAl/ifpwACgkQ7ZfpDmKq fjQrYA//Z3ky92YK4p8GAejA/69W92B2n+uATB7YPOVJXjWOieo+nmlJihEaY447 bxsLfrExy/AwM5wUoqu9JPQmjUGQYxQR0MjIdpzLeWNCGx+NM8n2j+9K00VXxIXX 356rhSNclm5a/1AmkeeDeYK1C8Fw3QIQnaqeTMHDZ/Txv2UncAMshHR2P+9c2i/k N5A+XK0X3+YNHs/0AHbFobRonynw68cogTeSdslMxFtjWV1iTNNR7c8hHHCDXMgJ sjF7hJ7d6RHBRDQn53XgJdR/OKPaj1RJXncP1Be9j6J1M5wepkHJFVS7/66dDl+g 7TyimxnE/y5gxNVk1JWF9ssz31ksGBRbwq1P8IdF3/EsNF3tTB3eqmKM7PB55Oiu k9MWSDo5/fjfdhH24oYUhocJmMN+n2iiBjAh+mWOq1KNPBGtugbztSZPNXuHDHn9 vsAVuuOdK7FvZcbzE0kMqh3gCmp1YBPcXUSnlqLGaowwlykfoYYR0MGz8AdvJreE 5Su2wfiPlI/B2zvVmJ1i2LFr+9nfVFWlmXGAwFmHunpEKTHB9b0HKXVdsJL9qZC2 Gm7SXPMzHEjZ1G420jT8Bx0qfGLC62jTq98QSK6BdcfLd0AsU+rstmQviFZOtSAv qEPrAXPXUraEwMs2/dR+eXR0DWQMEbUWgtmxJM3jHOGnWRseAQc= =xaDL -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAl/ifpwACgkQ7ZfpDmKq fjSC+w/9HzW/PbI7gfxfbPkF0fCyHCl2OWWrLlJi1m0G72balJ+BmkhI3vvnBGwK 3OKhvN/HOxA4d11JpXiYmPuQ7iuCDO8nRTDWbtg5nuEdP3FOJqUBD0HKDjTg/UUo haXoFxJwPklPqGOiIsFklEQWgVwpN+LwZkL7b2yjjadL0k5ukx6z/G2lJ5qF2i63 f3Gbe/oG/UYd3ERlDpjvgn2tJWfmoS0S3qU3Y9TpraL3NrmunnbtIFDW7SIEM2oP W4XmtkNgBQGlHS1/x/vocNo31h6KyzqVg6OSyvk88Fzp8vE+gHGOVTLR2RdNh/0H NQDi+Pj65KlIJUsjcLmZo+Huv+eNUfzwBcG+LGwUhay0q+2kaeGTs6epohYFNZen A/0/nzXJBohqcBnbLcBYVf+AZUHuPs5lTkG3OZpdRSvkmw6lELlJbBQMEf/HP/kG l43x9DEe0Dr2oDIEr1mfjszFJqKvSg43QJnTgUJtd0SqITazC1N9XuIZj0uXJ64g zfC1aByJ1FLNJmkMDKbl+OzVg7o53sS2gzL/EaGp43NeOPVa84w5MSWdZnuPz8xa 8KDdcaqWeY+mdLonfq5K/DZhOcV6UanBEXFFrmGZymSSqF2zYPpzPBB/7+B29S5F 68v8ScTY8a3fKjhQqrqzNOOKbVMSwM7m8dZ5o69nIW/knvdmxeg= =eekA -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAl/ifp0ACgkQ7ZfpDmKq fjQnxA//ZYROGBW1B1b7EY+j8b8z8oBsrzuN+PHkpmXqXre/rVJfIU7NoRoOoZ27 U3JDYPhQ6jy3fOCkW8Xa/eBwEe9PXfBnlpjAYbQ4d7KUvxzDauNG7Sch/aOKuQqE LIM9B+Gdyojn1dAimKcVh8z+lSH3f+gaL3/kCDAPDCJqxsDpbnzQ5rsgpf7OlkG8 6yBRo4wNsW6D49nEVScCPwtmlMQUBFesV0J49rZ74NL9eArIjjdHgwSSc0RtSTLx VT8yDmV1ZW93W4+ZKwfnyPb/u8w8O5NP42SoWHOdXV40UpyU/jWfioKPhbLr+D1R AU+uPE/GBpIPEd6dL75WNMQWvSPkER+QEcTYdzJIMiqOpwUXEADn5/miH3JiJ1Cx rgkQuukOzmmshL3YiKxWM2WT41NdVZn4MrXx3TfS2gw0Am4zElkRwcNanFc7Ksyl PNoJrypAKPnArG3+P0LSFxq9nQUsaajlYcAqYthRtzTicPA13iXWml/ATh1sw36H rJAEAVBg2TmIHo4/zlEuV7alrnBT0tIz38RtGvGA7lVB0w8ZLrh3BqyezucoK3Zc GsleX8wkJrrWMcdVPnRUCfCosx8IN57349mnL2g5v1B3Ij/ytYy4yDr8H7/vAX2c ddaxW1aluGBzL48ZKKJedDP/vZgRWINXMAyEyqdXW2G33aMsFlw= =IS+h -----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 rearguard_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'.

4 14