May 2020 - tz - lists.iana.org

Italy April 1944 discrepancy between comment and data
by Alois Treindl Oct. 5, 2021

Oct. 5, 2021

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 April 2, 2021

April 2, 2021

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

Removing systemv, pacificnew, Rule TYPEs, zic -y
by Tim Parenti Oct. 4, 2020

Oct. 4, 2020

I noticed recently that the systemv file, which adapted a subset of North American zones with limited rulesets to old versions of System V, has had all its once-useful bits commented out since 2005p. Looking back at list archives, even discussion at the time argued that the file wasn't really needed then. The attached proposed patch 0001 removes this obsolete file and its references. Of course, I was only looking at systemv in the first place because I'd also recalled that we're still distributing the pacificnew file, which has caused some confusion every so often and has likewise generally outlived its usefulness. This led me to the related file yearistype.sh, which is also unused, except as a default script to pass to the Makefile to process the TYPE field of Rule lines. Given that the TYPE field hasn't been used by tzdata since 2000f and has been more formally deprecated since 2015f, the whole unused feature is ripe for "spring cleaning". The attached proposed patch 0002 completely drops support for the TYPE field (marking it reserved for compatibility purposes) and causes non-trivial use of the field or use of zic's -y option to error (instead of warning as it has since 2017c). It also removes the pacificnew and yearistype.sh files that are no longer needed and updates documentation accordingly. I don't presently foresee any need to repurpose the nullified field down the road, but this is the next step in allowing us to "reclaim" it in the event that such a need should arise in the future. -- Tim Parenti

3 3

Updating zic.c to further match Link line field names
by Tim Parenti Oct. 3, 2020

Oct. 3, 2020

In working on my latest proposed patch, I also noticed an outdated error message in zic.c which referred to the FROM field of a Link line. We had updated these field names in comments and documentation in release 2014g to be more descriptive and readily understandable like the parameters of 'ln': https://github.com/eggert/tz/commit/78e3924ea43079a0f3333677a728e0f0ed679cd3 The attached proposed patch further updates the zic.c code to more consistently use these new names throughout. This mostly affects the naming of parameters and locals, but a few macros and struct fields are also updated for consistency. -- Tim Parenti

1 1

Tim Parenti as backup TZ Coordinator?
by Paul Eggert July 9, 2020

July 9, 2020

Tim Parenti's recent emails to the list reminded me that I'd long been meaning to nominate him to be my backup as TZ Coordinator. We should have a backup in case I am no longer available due to retirement or whatever, not that I'm planning to retire any time soon. I would like to start by giving him commit privileges to the development repository on GitHub, so that his contributions can become part of releases more easily. Tim has been a longtime and substantial contributor to tzdb, as evidenced by his detailed and careful patches. Although he's mostly worked in the tzdata area, he's also proficient on the code side, as his recent patch proposals demonstrate. He and I have corresponded by email about this and he's indicated his willingness to take on the responsibility. I'd appreciate reactions to Tim's offer to be backup; please respond within the next week.

12 13

Re: [tz] FW: [Ext] The TZ Coordination
by Paul Eggert May 28, 2020

May 28, 2020

On 5/28/20 3:41 AM, EL MAAYATI Afaf wrote: > we need to know if there is a procedure to notify IANA (TZ Coordination) officially, from a governmental source, with the official dates of TZ changes in Morocco. The procedure is to send email to tz(a)iana.org with official citations, preferably with pointers to copies in English since the mailing list is in English. For best results, give one years' notice before the dates of change. For more details, please see: https://data.iana.org/time-zones/tz-link.html#changes

1 0

zdump --version reports "unknown" on OpenSuse 15.1 [2020a]
by listclient＠hayo.de May 28, 2020

May 28, 2020

Hi all, when checking the timezone database version on my OpenSuse 15.1 Linux, I do not get the expected result. hayo@computer:~> sudo zdump --version zdump (tzcode) unknown Installed package: timezone - Time Zone Descriptions Is this a defect of the OpenSuse package or of the IANA code distribution? Regards, Hayo More Details ------------ Technical data: Installierte Version 2020a-lp151.2.9.1 Mo 18 Mai 2020 10:13:45 CEST Sa 23 Mai 2020 20:03:30 CEST System/Base BSD-3-Clause AND SUSE-Public-Domain 1,1 MiB 0 B openSUSE Leap 15.1 openSUSE http://bugs.opensuse.org x86_64 http://www.iana.org/time-zones timezone-2020a-lp151.2.9.1 0 File list: /etc/localtime /usr/bin/tzselect /usr/sbin/zdump /usr/sbin/zic /usr/share/zoneinfo ... Change log: Fr 24 Apr 2020 14:00:00 CEST Marketa Calabkova <mcalabkova(a)suse.com> - timezone update 2020a (bsc#1169582) * Morocco springs forward on 2020-05-31, not 2020-05-24. * Canada's Yukon advanced to -07 year-round on 2020-03-08. * America/Nuuk renamed from America/Godthab. * zic now supports expiration dates for leap second lists.

8 11

Re: [tz] Fwd: TR: Morocco : Time Change
by Semlali Naoufal May 27, 2020

May 27, 2020

Hello, I would like to inform you that the time has been advanced by one hour today on Android Smartphones while the time change should not be made until 31.05.2020 as already reported. Has the patch below been deployed correctly? For iPhone, the time is not changed. Regards, -----Message d'origine----- De : Paul Eggert <eggert(a)cs.ucla.edu> Envoyé : mercredi 15 avril 2020 06:26 À : Semlali Naoufal <N.Semlali(a)iam.ma>; Tim Parenti <tim(a)timtimeonline.com> Cc : Maamar Abdelkader <A.MAAMAR(a)iam.ma>; Time zone mailing list <tz(a)iana.org> Objet : Re: Morocco : Time Change Thanks for the heads-up. A proposed patch is attached. Looks like we'll need a new tzdb release soon, since the current release is wrong for Morocco starting May 24. ________________________________ [Description : cid:image002.jpg@01CC9EE4.44A57D10]Eco – geste: privilégiez la sauvegarde électronique, si nécessaire imprimez en recto-verso ________________________________ Ce message et toutes les pièces jointes sont adressés à l'attention exclusive de leurs destinataires et sont strictement confidentiels. Si vous le recevez par erreur, merci de le détruire après en avoir informé l'expéditeur sans délai. Toute divulgation, copie ou usage par une personne autre que son destinataire sont interdits. Maroc Telecom décline toute responsabilité pour toute altération, déformation ou falsification subie par le message au cours de sa transmission. Retrouvez toutes les informations de Maroc Telecom sur www.iam.ma . ________________________________ This message and its attachments are intended only for the person or entity to which it is addressed and are strictly confidential. If you have received this in error, please delete the material from any computer after having informed the sender. Any copy or other use of this information by persons or entities other than the intended recipient is prohibited. Maroc Telecom accepts no liability for any alteration, distortion or falsification that may occur during the transmission of this message. All information about Maroc Telecom on www.iam.ma .

5 4

Typo in a 1900 date of europe tz file
by josep lladonosa capell May 27, 2020

May 27, 2020

Hello, I was just reading the europe tz file and found a typo. The comment in the file gives the date 26/6/1900 but in fact it was July (7) not June (6). In the same text there is a reference to the official document of 26/7/1900. Attached you will find the patch.

1 0

Re: [tz] Welcome to the "tz" mailing list
by Sundar Sarma May 25, 2020

May 25, 2020

we have used this code to get the IANA tz version. public static String getTimezoneDatabaseIANAVersion() { File readmeFile = new File(ZONEINFO_PATH, "README"); File alternativeReadmeFile = new File(ZONEINFO_PATH, "README.txt"); if (!readmeFile.exists()) { readmeFile = alternativeReadmeFile; } out read me.txt file contain generated by Gradle Based on http://www.iana.org/time-zones/repository/releases/tzdata2020a.tar.gz means we are using correct tzdata2020a. But still why there is issue? Something wrong with tz db?? regards, sundar On Fri, May 22, 2020 at 9:12 PM Sundar Sarma <gkssarma59(a)gmail.com> wrote: > ZoneRulesProvider.getVersions( String zoneId ). > which gives the version used by Java. > > this above code gives the version used by java. > > that is correct. Bu the above code is java.time > > we are using joda.time in our application. > > So could you please tell me that how to get the version used by java in > joda time?? > > thanks, > sundar > > On Thu, May 21, 2020 at 6:39 PM Michael H Deckers < > michael.h.deckers(a)googlemail.com> wrote: > >> >> On 2020-05-21 12:39, Sundar Sarma wrote: >> >> >> > Still i did not understand why this test case is failing with new 2020a >> tz. >> >> >> The version of the IANA database installed in the operating >> system may well differ from the version used by Java.time. >> The latter can be determined with the method >> ZoneRulesProvider.getVersions( String zoneId ). >> which gives the version used by Java. >> >> HTH. >> >> Michael Deckers. >> >> >> >>

3 4