- tz - lists.iana.org

Correcting daylight-savings time for central Missouri prior to 1967
by Jane Eisenstein Nov. 24, 2018

Nov. 24, 2018

I was born and raised in central Missouri and know most of Missouri did not observe daylight-savings time prior to 1967. Areas close to Kansas City or St. Louis did observe daylight-savings time prior to 1967. I’ve also attached supporting scans of Missouri daylight-savings time information from the 1991 revision of Time Changes in the U.S.A. by Doris Chase Doane. The timezones database appears to assume all Missouri observed daylight savings whenever Chicago, Illinois did. I would like to correct this mistake, but am not clear how to go about doing so. Can the daylight-savings time be set at the state level, then overridden for particular communities? Best regards, Jane Eisenstein

9 25

Nauru Time history
by Phake Nick Nov. 19, 2018

Nov. 19, 2018

* Currently, the tz database say Nauru use LMT until 1921, and then switched to GMT+11:30 for the next two decades. * However, a number of timezone map published in America/Japan back then showed its timezone as GMT+11 per https://wiki.suikawiki.org/n/ナウルの標準時 * And it would also be nice if the 1921 transition date could be sourced. * The tz database currently show Nauru use GMT+9 within the time of 1942 Mar 15 and 1944 Aug 15, however the correspondence is not exact as Nauru was still under Japanese rule until year 1945. And I don't think it's likely for such switch to occur during WWII so it's probably an error. * Currently tz database shows the +11:30 -> +12 transition date as 1979 May, however the "Nauru Standard Time Act 1978 Time Change" http://ronlaw.gov.nr/nauru_lpms/files/gazettes/4b23a17d2030150404db7a5fa587… based on "Nauru Standard Time Act 1978 Time Change" http://www.paclii.org/nr/legis/num_act/nsta1978207/ defined that "Nauru Alternative Time" (GMT+12) should be in effect from 1979 Feb. Thus it appears that the current tz database transition time might be incorrect.

3 2

Hong Kong time 1941
by Phake Nick Nov. 18, 2018

Nov. 18, 2018

Today I went to check microfilm records stored at Hong Kong Public Library and found following situation that are inconsistent with tz database record. * Around April 1 1941, there're no news about DST on various newspapers that I checked. Time given for sunrise/sunset around the period are also continuous (as in they're minutes within each others on those days, indicating there are no change to time standard around 1941 April 1. * I have subsequently checked Hong Kong Observatory's site and the site now list the 1941 DST start date for Hong Kong as June 15. (url is same as the one in tz file but content is different from when the 2009 comment was made) I have not tried validating the info from those newspapers as I wasn't aware of the table's current content until I stopped using the library. * And then, on September 30 1941, according to Ta Kung Pao (Hong Kong edition), it was stated that fallback would occur on the next day (the 1st)'s "03:00 am (Hong Kong Time 04:00 am)" and the clock will fall back for a half hour. (03:00 probably refer to the time commonly used in mainland China at the time given the paper's background), after it was spring forward for an hour months ago. I cannot find out record of English newspaper from that day, but the sunrise/sunset time given by South China Morning Post for October 1st was indeed moved by half an hour compares to before. * After that, in December, the battle to capture Hong Kong started and the library doesn't seems to have any record stored about press during that period of time. Some media resumed publication soon after that within the same month, but there were not much information about time there. Later they started including a radio program guide when they restored radio service, explicitly mentioning it use Tokyo standard time, and later added a note saying it's half an hour ahead of the old Hong Kong standard time, and it also seems to indicate that Hong Kong was not using GMT+8 when it was captured by Japan. * Image of related sections on newspaper: 1941 September 30, Ta Kung Pao (Hing Kong) , "Winter Time starr tomorrow": https://i.imgur.com/6waY51Z.jpg (Chinese) 1941 September 29, South China Morning Post, Information on sunrise/sunset time and other things for September 30 and October 1: https://i.imgur.com/kCiUR78.jpg 1942 February 5, The Hong Kong News, Radio Program Guide: https://i.imgur.com/eVvDMzS.jpg

7 19

Higgins Time and TZ DB c.1886
by Brian Inglis Nov. 18, 2018

Nov. 18, 2018

Links to an interesting article and artifact referenced in comments on: https://www.jwz.org/blog/2018/08/higgins-time/ Arabian Flying Is Confusing article - Port Angeles Evening News, March 10, 1965, p. 4: https://newspaperarchive.com/port-angeles-evening-news-mar-10-1965-p-4/ Kendal & Dent's Time Chart of the World c.1886 - Evanion Catalogue - BL: https://www.bl.uk/catalogues/evanion/FullImage.aspx?EvanID=024-000002349&Im… -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised.

2 2

Korean DST 1940s-1960s and other aspects of Korean Standard Time and other aspects of tz database
by Phake Nick Nov. 17, 2018

Nov. 17, 2018

1. According to official announcement from Korean government, the DST end date in South Korea should be 1955-09-08 without specifying time http://theme.archives.go.kr/next/common/viewEbook.do?singleData=N&archiveEv… 1956-09-29 without specifying time http://theme.archives.go.kr/next/common/viewEbook.do?singleData=N&archiveEv… 1957-09-21 24 o'clock http://theme.archives.go.kr/next/common/viewEbook.do?singleData=N&archiveEv… 1958-09-20 24 o'clock http://theme.archives.go.kr/next/common/viewEbook.do?singleData=N&archiveEv… 1959-09-19 24 o'clock http://theme.archives.go.kr/next/common/viewEbook.do?singleData=N&archiveEv… 1960-09-17 24 o'clock http://theme.archives.go.kr/next/common/viewEbook.do?singleData=N&archiveEv… Contradicting the current tz database record that shows their end date as 00:00 of the next days. The effect should be same in almost all cases, but to be literally reflect the rule in tz database probably an update might be desirable. [Information via Suikawiki] 2. Regarding history of Korean time, there is a Korean wiki site https://namu.wiki/w/대한민국%20표준시 that say when Korea was using GMT+8:30 as standard time, the international aviation/marine/meteorological industry in the country refused to follow and continues to use GMT+9:00 for interoperability. Did the phenomenon actually occured back then and is there any further details about it? 3. Back in 2014 when Korean time history in tz database was discussed, the reliability of The International Atlas by Shanks was also being discussed. I checked the book on amazon.com and there's a review saying that the International Atlas say they've make up some information to fill holes in their research and use them to advance copyright claims to temporarily force tzinfo offline. I am not sure what happened back then in the year of 2011 when the comment was posted, but if that's true then tz database should probably be more actively removing anything related to Shanks from the database as those information are not fact and thus subject to copyright claims and thus cannot be released as public domain according to the license of tz database? Not to mention the accuracy of those data.

2 1

[PATCH] * tz-link.html: Mention Time4A.
by Paul Eggert Nov. 17, 2018

Nov. 17, 2018

--- tz-link.html | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/tz-link.html b/tz-link.html index 956af52..3a3c96b 100644 --- a/tz-link.html +++ b/tz-link.html @@ -372,10 +372,12 @@ and time <abbr>API</abbr></a> contains a class Java 8 <code>java.time</code>, which its users should migrate to once they can assume Java 8 or later. It is available under the <a href="https://www.apache.org/licenses/LICENSE-2.0">Apache License</a>.</li> -<li><a href="https://github.com/MenoData/Time4J/">Time4J – -Advanced date, time and interval library for Java</a> contains a class -<code>net.time4j.tool.TimezoneRepositoryCompiler</code> that compiles -<code><abbr>tz</abbr></code> source into a binary format. Time4J is +<li><a href="https://github.com/MenoData/Time4A">Time4A: Advanced date and +time library for Android</a> and +<a href="https://github.com/MenoData/Time4J/">Time4J: Advanced date, +time and interval library for Java</a> compile +<code><abbr>tz</abbr></code> source into a binary format. +Time4A is available under the Apache License and Time4J is available under the <a href="https://www.gnu.org/copyleft/lesser.html"><abbr>GNU</abbr> Lesser General Public License (<abbr title="Lesser General Public -- 2.17.1

1 0

Re: [tz] Was there a 1971-12-31 23:59:60?
by Levine, Judah Dr. (Fed) Nov. 13, 2018

Nov. 13, 2018

Applying a time stamp to an event in an end-user application with nanosecond accuracy or precision is very difficult because of the problems of measuring the transmission delay from the source to the end-user and the latency in the end-user application. These problems are generally at least as large as knowing the accuracy of the source with respect to UTC or UTC(lab). Although all of these things can be characterized statistically, that is not of much use for a single event which cannot benefit from averaging. Note that post-processing may not be of much help in determining the jitter in the processing latency. The data in Circular T are what they are because of the administrative and processing delays in computing UTC. The UTC(lab) is now and will probably always be an extrapolation, which is limited by the flicker and random-walk processes of the laboratory time scale. Although the publication of UTCr has decreased the processing delay, it is a provisional scale and is not of much use at the nanosecond level. Judah Levine Time and Frequency Division NIST Boulder On: 10 November 2018 22:24, "Steve Allen" <sla(a)ucolick.org<mailto:sla@ucolick.org>> wrote: On Sat 2018-11-10T19:54:11+0000 Levine, Judah Dr. (Fed) hath writ: > It is quite challenging to compute time intervals in the pre-1972 > era. That depends on the required precision. It is still challenging to compute intervals to nanoseconds. That requires grabbing all the relevant issues of BIPM Circular T and similar publications of the particular source of time if they are not members of the BIPM atomic clock club. One hundred years ago it was challenging to compute intervals to centiseconds, and that was the reason for the creation of BIH. When Anna Stoyko retired from the BIH in 1965 she published one final analysis of all the BIH data from 1922 to 1963. She produced plots showing how the time services of observatories had improved. Those plots are reproduced here https://na01.safelinks.protection.outlook.com/?url=https:%2F%2Fwww.ucolick.… In order to gather these data the BIH had been monitoring the arrival times of radio broadcast time signals since 1922. The volumes of Bulletin Horaire have the numbers that show many ways that various national observatories and time services messed up (and messed around with) the time they were providing. The data in the issues of Bulletin Horaire are the nightmare of the tzdb because taken to the absurd limit they would require that tzdb encode the millisecond-scale differences between the legal civil times of every nation whose transmitters were monitored by BIH. > Different timing laboratories had slightly different values for this > final time step. The goal was to bring all of the real-time > realizations of UTC to the same time. Well, much closer than before, but if they were the same then the subsequent issues of BIH Bulletin Horaire and now BIPM Circular T would be much terser publications. -- Steve Allen <sla(a)ucolick.org<mailto:sla@ucolick.org>> WGS-84 (GPS) UCO/Lick Observatory--ISB 260 Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 Lng -122.06015 Santa Cruz, CA 95064 https://na01.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.ucolick.o… Hgt +250 m

1 0

CalConnect Public Time Zone Workshop on February 5 in Zurich, Switzerland
by Dave.Thewlis＠calconnect.org Nov. 12, 2018

Nov. 12, 2018

Please note that this is NOT an IETF event. CalConnect <http://www.calconnect.org/> will host a Public Time Zone Workshop on Tuesday afternoon, February 5th, during its conference at Google in Zürich, Switzerland <http://www.calconnect.org/events/calconnect-xliv-february-4-8-2019>. The Time Zone Workshop will be Tuesday February 5th from 13:30 to 17:30 at the Google facility <http://www.calconnect.org/events/calconnect-xliv-february-4-8-2019#location>. This workshop will be focussed on the potential impact of EU Summer Time changes and how the changes might be mitigated; please see our news release <http://www.calconnect.org/news/2018/10/30/calconnect-calls-eu-reconsider-ti…>. The workshop is open to the public but you must register in advance. There is no fee to attend the workshop. Attendees are invited to stay for a Welcome Reception following the workshop. More information will be provided as planning continues. The workshop is intended for anyone who needs to plan and prepare for this and other TZ/DST changes, in particular representatives from governments, industries affected by tz changes (travel, financial, health, device manufacturers, etc.), organizations deploying tz data, and organizations maintaining and updating tz data. Please register for this event at https://www.eventbrite.com/e/eu-dst-timezone-change-public-workshop-tickets… <https://www.eventbrite.com/e/eu-dst-timezone-change-public-workshop-tickets…>. We invite anyone who is interested in or concerned by the pending changes and how time zone change information might better be distributed and implemented to attend. Dave Thewli -- Dave Thewlis, Executive Director CalConnect - The Calendaring and Scheduling Consortium +1 707 840 9391 voice | +1 707 498 2238 mobile | +1 415 946 3454 fax http://www.calconnect.org <http://www.calconnect.org/> | Dave.Thewlis(a)calconnect.org <mailto:Dave.Thewlis@calconnect.org>

2 1

Re: [tz] Epic fail for DST fallback in hospital health records
by Hal Murray Nov. 12, 2018

Nov. 12, 2018

eggert(a)cs.ucla.edu said: > Gawande A. Why doctors hate their computers. The New Yorker. 2018-11-12. > https://www.newyorker.com/magazine/2018/11/12/why-doctors-hate-their-comput… Thanks for the heads up. In case anybody doesn't recognize the name, the A is Atul. He's a surgeon, and a very good writer. His first two books are collections of his New Yorker articles. My reading on this whole mess is that the medical community doesn't take testing software seriously. It may be as simple as senior executives with budget problems aren't willing to pay for testing because they don't understand that you have to do lots of it if you expect your systems to work reliably. For background, I highly recommend Gawande's Checklist Manifesto. He led a WHO project to get airplane style checklists used in hospital operating rooms. Not much about software, lots about checklists and the pilot/cockpit culture. For info about medical software, I recommend Robert Wachter's Digital Doctor. It's the study of a screwup at UCSF hospital that almost killed a kid. Lots of info about software and UIs and testing. https://www.goodreads.com/book/show/23131174-the-digital-doctor -- These are my opinions. I hate spam.

6 9

Re: [tz] Was there a 1971-12-31 23:59:60?
by Levine, Judah Dr. (Fed) Nov. 11, 2018

Nov. 11, 2018

Hello, The current integer leap second system did not exist before 1972. There were a number of fractional-second adjustments and there were also frequency adjustments starting in the 1950s, when the length of the cesium second was defined. The final time adjustment at the start of 1972 was intended to incorporate the integral of the previous frequency steps, since the frequency of UTC was set equal to the SI second at that time. It is quite challenging to compute time intervals in the pre-1972 era. Different timing laboratories had slightly different values for this final time step. The goal was to bring all of the real-time realizations of UTC to the same time. Judah Levine On: 09 November 2018 22:29, "Steve Allen" <sla(a)ucolick.org<mailto:sla@ucolick.org>> wrote: On Fri 2018-11-09T22:04:35-0700 Paul Gilmartin via tz hath writ: > Subject: [tz] Was there a 1971-12-31 23:59:60? No. There was a step of 0.107758 seconds in UTC(BIH) at 1972-01-01. This was the final sub-second step in coordinated broadcast time signals. for the step that was applied to UTC(USNO) see Time Service Announcement series 14 number 8 (1971-10-08) at https://na01.safelinks.protection.outlook.com/?url=https:%2F%2Fwww.ucolick.… -- Steve Allen <sla(a)ucolick.org<mailto:sla@ucolick.org>> WGS-84 (GPS) UCO/Lick Observatory--ISB 260 Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 &nb

2 1

Julian calendar
by Arthur David Olson Nov. 10, 2018

Nov. 10, 2018

Alas, while the current tz package can get the day-skipping part of the Julian-to-Gregorian calendar transition right, it gets pre-transition weekdays worng. (Getting them right would require special casing for big offsets from standard time in localtime.c) @dashdashado Script started on Sat, Nov 10, 2018 6:47:15 PM $ cat fake Zone America/Somewhere -268:56:02 - LMT 1752 Sep 3 -4:56:02 - LMT $ ./zic fake $ ./zdump -v America/Somewhere America/Somewhere -9223372036854775808 = NULL America/Somewhere -9223372036854689408 = NULL America/Somewhere Thu Sep 14 04:56:01 1752 UT = Sat Sep 2 23:59:59 1752 LMT isdst=0 gmtoff=-968162 America/Somewhere Thu Sep 14 04:56:02 1752 UT = Thu Sep 14 00:00:00 1752 LMT isdst=0 gmtoff=-17762 America/Somewhere 9223372036854689407 = NULL America/Somewhere 9223372036854775807 = NULL $ exit exit Script done on Sat, Nov 10, 2018 6:47:36 PM

1 0

Was there a 1971-12-31 23:59:60?
by Paul Gilmartin Nov. 10, 2018

Nov. 10, 2018

Hello, Judah Levine, I get unexpected results on Linux with TZ=right/Universal. I downloaded https://data.iana.org/time-zones/releases/tzdata2018g.tar.gz to try to find an explanation. There, I find, in: leap-seconds.list ... # # Updated through IERS Bulletin C56 # File expires on: 28 June 2019 # #@ 3770668800 # 2272060800 10 # 1 Jan 1972 2287785600 11 # 1 Jul 1972 2303683200 12 # 1 Jan 1973 2335219200 13 # 1 Jan 1974 2366755200 14 # 1 Jan 1975 ... I tend to believe this, but in: leapseconds ... # There were no leap seconds before 1972, because the official mechanism # accounting for the discrepancy between atomic time and the earth's rotation # did not exist. # The correction (+ or -) is made at the given time, so lines # will typically look like: # Leap YEAR MON DAY 23:59:60 + R/S # or # Leap YEAR MON DAY 23:59:59 - R/S # If the leap second is Rolling (R) the given time is local time (unused here). Leap 1972 Jun 30 23:59:60 + S Leap 1972 Dec 31 23:59:60 + S Leap 1973 Dec 31 23:59:60 + S Leap 1974 Dec 31 23:59:60 + S ... Well, it's consistent with itself. 1971-12-31 23:59:60 is *before* 1972. But "leap-seconds.list" shows one more leap second that "leapseconds". I'm confused. Thanks, gil

3 2

Re: [tz] zdump bug?
by Paul Eggert Nov. 8, 2018

Nov. 8, 2018

On 10/28/18 9:23 PM, Paul Eggert wrote: > 'zdump New_York' is treated differently from 'zdump ./New_York'. It > might make sense for the code to try harder to treat only ".." > components differently. I installed the attached first patch to try to do that. The second attached patch silences a warning when running "make CFLAGS='$(GCC_DEBUG_FLAGS)' GCC_INSTRUMENT=" on my platform (I updated GCC recently).

3 5

Fwd:DST in Isral 1980 and 1984
by Astrodienst Team Nov. 7, 2018

Nov. 7, 2018

I received this document, which claims DST from 2 August 1980 - 13 Sept 1980 and 5 May 1984 - 25 August 1984. These two periods are not contained in the current TZ database, which has Rule Zion 1974 only - Jul 7 0:00 1:00 D Rule Zion 1974 only - Oct 13 0:00 0 S Rule Zion 1975 only - Apr 20 0:00 1:00 D Rule Zion 1975 only - Aug 31 0:00 0 S Rule Zion 1985 only - Apr 14 0:00 1:00 D Rule Zion 1985 only - Sep 15 0:00 0 S Rule Zion 1986 only - May 18 0:00 1:00 D Rule Zion 1986 only - Sep 7 0:00 0 S -------- Forwarded Message -------- Subject: Hello to astro system Date: Tue, 18 Sep 2018 03:18:57 +0300 From: Israel Tzaig <israheal(a)gmail.com> To: order(a)astro.ch <order(a)astro.ch> My name is Israel Sagi and I wanted to update you about daylight saving time in Israel. In 1980 there was a summer time from 3.8 to 13.9. This clock is not updated on your maps. Attached is a page from the Ministry of Interior for daylight saving time in Israel Thank you and hope you will use the information here. For a double check, I went to the archives of Yedioth Ahronoth (the most popular newspaper in Israel) in 1980 to make sure that there was a daylight saving time. I would be happy to send you a photo of the relevant articles (in Hebrew of course) נשלח מהאפליקציה 'דואר <https://go.microsoft.com/fwlink/?LinkId=550986>' עבור Windows 10

3 4

Epic fail for DST fallback in hospital health records
by Paul Eggert Nov. 6, 2018

Nov. 6, 2018

Sydney Lupkin reports in today's Kaiser Health News that Epic Systems, a leading system used for hospital health records, cannot handle DST fallbacks such as Sunday's fallback in the US. Lupkin writes: 'Carol Hawthorne-Johnson, an ICU nurse in California, said her hospital doesn’t shut down the Epic system during the fall time change. But she’s come to expect that the vitals she enters into the system from 1 a.m. to 2 a.m. will be deleted when the clock falls back to 1 a.m. One hour’s worth of electronic record-keeping “is gone,” she said.' Apparently competing systems have similar problems. Lupkin writes that many hospitals plan for Cerner (another major system) to be down after a DST fallback as well. Dr. Steven Stack, past president of the American Medical Association, said these DST glitches are "unacceptable", considering that Apple and Google seem to have dealt with seasonal time changes long ago. Although Lupkin didn't say so, credit should be given to the design for the Unix operating system that is the basis for these successes of Apple and Google, as Unix standardized on UTC in the early 1970s; apparently Epic and Cerner (both founded 1979) did not get the message. The moral of this story seems to be: arrange for your medical emergencies to occur some time other than early Sunday in the US. Source: Lupkin S. Like Clockwork: How Daylight Saving Time Stumps Hospital Record Keeping. Kaiser Health News. 2018-11-03. https://khn.org/news/like-clockwork-how-daylight-saving-time-stumps-hospita…

9 17

tzdata2018g.tar.gz failing to install in Java 8
by Carter, Tom Nov. 6, 2018

Nov. 6, 2018

Iana team: I am getting the following when trying to install tzdata2018g.tar.gz using the latest tzupdater.jar (2.2.0) for Java 8. Failed: java.lang.Exception: Failed while parsing file '/tmp/tz.tmp_5/asia' on line 1655 'Rule Japan 1948 1951 - Sep Sat>=8 25:00 0 S' java.lang.Exception: Failed while parsing file '/tmp/tz.tmp_5/asia' on line 1655 'Rule Japan 1948 1951 - Sep Sat>=8 25:00 0 S' at tools.tzdb.TzdbZoneRulesCompiler.parseFile(TzdbZoneRulesCompiler.java:377) at tools.tzdb.TzdbZoneRulesCompiler.compile(TzdbZoneRulesCompiler.java:191) at tools.tzdb.TzdbZoneRulesCompiler.<init>(TzdbZoneRulesCompiler.java:307) at com.sun.tools.tzupdater.ExternalModule.compileToJSRBinary(ExternalModule.java:153) at com.sun.tools.tzupdater.TimezoneUpdater.run(TimezoneUpdater.java:230) at com.sun.tools.tzupdater.TimezoneUpdater.main(TimezoneUpdater.java:634) Caused by: tools.tzdb.DateTimeException: Invalid value for SecondOfDay value: 90000 at tools.tzdb.ChronoField.checkValidValue(ChronoField.java:173) at tools.tzdb.LocalTime.ofSecondOfDay(LocalTime.java:210) at tools.tzdb.TzdbZoneRulesCompiler.parseMonthDayTime(TzdbZoneRulesCompiler.java:475) at tools.tzdb.TzdbZoneRulesCompiler.parseRuleLine(TzdbZoneRulesCompiler.java:399) at tools.tzdb.TzdbZoneRulesCompiler.parseFile(TzdbZoneRulesCompiler.java:354) ... 5 more Please advise when will this be fixed? Thanks, Tom L Carter Principal Architect: CS/BW, American Airlines Work#: (817) 963-7640 Cell: (972) 849-1416 Coordinates: 4N-5A-53@HDQ2 Meeting Room<https://americanairlines.webex.com/join/Tom.Carter> NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient(s). If you are not an intended recipient, please do not read, distribute, or take action in reliance upon this message. If you have received this in error, please notify me immediately by return email and promptly delete this message and its attachments from your computer.

7 10

[tz-announce] 2018g release of tz code and data available
by Joel da Rosa Nov. 5, 2018

Nov. 5, 2018

Hello! Fail on parser asia TZ (Japan Rule) persist: Using https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz as source for tzdata bundle. Failed: java.lang.Exception: Failed while parsing file '/tmp/tz.tmp/asia' on line 1655 'Rule Japan 1948 1951 - Sep Sat>=8 25:00 0 S' java.lang.Exception: Failed while parsing file '/tmp/tz.tmp/asia' on line 1655 'Rule Japan 1948 1951 - Sep Sat>=8 25:00 0 S' at tools.tzdb.TzdbZoneRulesCompiler.parseFile(TzdbZoneRulesCompiler.java:377) at tools.tzdb.TzdbZoneRulesCompiler.compile(TzdbZoneRulesCompiler.java:191) at tools.tzdb.TzdbZoneRulesCompiler.<init>(TzdbZoneRulesCompiler.java:307) at com.sun.tools.tzupdater.ExternalModule.compileToJSRBinary(ExternalModule.java:153) at com.sun.tools.tzupdater.TimezoneUpdater.run(TimezoneUpdater.java:230) at com.sun.tools.tzupdater.TimezoneUpdater.main(TimezoneUpdater.java:634) Caused by: tools.tzdb.DateTimeException: Invalid value for SecondOfDay value: 90000 at tools.tzdb.ChronoField.checkValidValue(ChronoField.java:173) at tools.tzdb.LocalTime.ofSecondOfDay(LocalTime.java:210) at tools.tzdb.TzdbZoneRulesCompiler.parseMonthDayTime(TzdbZoneRulesCompiler.java:475) at tools.tzdb.TzdbZoneRulesCompiler.parseRuleLine(TzdbZoneRulesCompiler.java:399) at tools.tzdb.TzdbZoneRulesCompiler.parseFile(TzdbZoneRulesCompiler.java:354) My environment: Linux Ubuntu 16.04 java version "1.8.0_191" Java(TM) SE Runtime Environment (build 1.8.0_191-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode) -- Atenciosamente, Joel da Rosa

2 1

Re: [tz] [tz-announce] 2018f release of tz code and data available
by Paul Eggert Nov. 2, 2018

Nov. 2, 2018

On 10/18/18 8:14 AM, Christos Zoulas wrote: > My folks are reporting that java does not like it: > > ERROR: Failed: java.lang.Exception: Failed while parsing file > '/tmp/tz.tmp_2/asia' on line 1655 'Rule Japan 1948 1951 - SepSat>=8 25:00 0 S' > ERROR: java.lang.Exception: Failed while parsing file > '/tmp/tz.tmp_2/asia' on line 1655 'Rule Japan 1948 1951 - Sep Sat>=8 25:00 0 S' > Thanks for the heads-up; please try the attached patch. Is there some way your folks can try the development version on GitHub every now and then? That "25:00" has been in the development version since last month and was explicitly called out when the patch was circulated on the mailing list <https://mm.icann.org/pipermail/tz/2018-September/026891.html>. It'd have been nice to catch the glitch before 2018f came out.

14 31

Re: [tz] Time zone confusion in Morocco
by Hicham Boushaba Nov. 2, 2018

Nov. 2, 2018

We Moroccans didn't know about the change also before Friday, our government didn't take the time to neither study nor discuss the matter with us. And the real issue, is that Android devices (maybe iOS devices, I'm not sure) update the tzdb only via a system upgrade/patch, and we know that Android OEMs rarely update their devices, so Moroccans will stay impacted for a long time, and non-tech people don't have the necessary skills to change the timezone manually.

9 12

[PROPOSED] Bring back attribute_pure for getzname
by Paul Eggert Nov. 1, 2018

Nov. 1, 2018

* localtime.c (getzname, getqzname): Bring back ATTRIBUTE_PURE. I was mistaken about GCC not needing this any more, as it’s still needed with GCC 8.2.1 when building with ‘make GCC_INSTRUMENT= CFLAGS='$(GCC_DEBUG_FLAGS)'’. --- localtime.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/localtime.c b/localtime.c index 7b72f9c..ac3790a 100644 --- a/localtime.c +++ b/localtime.c @@ -789,7 +789,7 @@ static const int year_lengths[2] = { ** Return a pointer to that character. */ -static const char * +static ATTRIBUTE_PURE const char * getzname(register const char *strp) { register char c; @@ -810,7 +810,7 @@ getzname(register const char *strp) ** We don't do any checking here; checking is done later in common-case code. */ -static const char * +static ATTRIBUTE_PURE const char * getqzname(register const char *strp, const int delim) { register int c; -- 2.19.1

1 0

Will Morocco switch from +01 to +00 during Ramadan next year?
by Paul Eggert Nov. 1, 2018

Nov. 1, 2018

Maamar Abdelkader wrote: > The 2019 Ramadan period is supposed to be from May 5th to June 4th. > We usually move clocks back the previous week end and come back to the +1 the week end after. > So it supposed to be sunday april 28 and sunday june 12. > > The government does not announce yet the decision about this temporarily change. > > But it s 99% sure that it will be the case, as the previous years. > > A non official survey was done these days, showing that 64% of asked peopke are ok for moving from +1 to +0 during Ramadan. > > https://leconomiste.com/article/1035870-enquete-l-economiste-sunergia-64-de… > > I will share the official decision once it s published. Thanks for the info. I installed the attached patches into the development version on GitHub to implement this. This patch doesn't exactly agree with the dates you specified (for 2019 it guesses falling back Sunday, May 5 and springing forward Sunday, June 9), but these dates are approximate until an official announcement and a methodical guess is better than no guess at all. Java users, please note that this patch uses negative DST in the main and vanguard formats; in rearguard format Morocco stays in the +00 timezone (instead of moving to +01 last weekend) and observes positive DST in every month but Ramadan.

2 2

Time zone confusion in Morocco
by Paul Eggert Nov. 1, 2018

Nov. 1, 2018

Since 2012 Morocco has been switching from +01 (DST) to +00 (standard time) for Ramadan. In an article in today's Morocco World News, Safaa Kasraoui implies (but does not explicitly state) that Morocco will continue this practice even after its time zone switch last weekend from +00 to +01, and thus that Morocco will switch from +01 (standard time) to +00 (presumably DST) during Ramadan next year. If so, we'll have to change tzdb again, this would be another use of negative DST, and I'll bring back my Emacs-based predictions of Ramadan for Morocco. Kasraoui also reports that MP Abdellatif Ouahbi has called on the Moroccan government to release the study that the government said it had conducted on time change. My guess is that no real study was conducted, that the government knew the change would be controversial, and that it announced the change with so little notice because it didn't want controversy to derail the change. The government's main argument for not using DST was the confusion and "tensions and diseases" of switchover, and its main argument for adopting +01 instead of +00 appears to be to smooth out peaks in electricity consumption, though it appears that there is no data to support either argument. As part of the time zone change, the government also changed school timetables so that schools will start at 09:00 instead of 08:00, effectively canceling the time zone change for schools. It said it will make further measures regarding DST, without giving details. Kasraoui reports, "Clocks set by the internet with Moroccan cities selected as the time zone returned to GMT on Sunday and, as of Wednesday, are still showing the wrong time." Presumably this mostly refers to Android and iOS phones; although my US-baseed Android 9 phone is not updated, the Ubuntu desktop that I'm typing this message on is updated. Ubuntu is downstream from Debian which in turn is downstream from tzdb, and the timeline for my desktop update was as follows (all times UTC): 2018-10-27 05:22:45 2018g timestamped 2018-10-27 05:23:38 2018g committed to development version 2018-10-27 12:10:11 2018g available from iana.org 2018-10-27 13:14:23 2018g created for Debian sid 2018-10-27 15:55:08 2018g announced on tz-announce(a)iana.org 2018-10-28 02:00:00 rule change takes effect in Morocco 2018-10-28 21:51:08 2018g created for Ubuntu bionic 2018-10-30 05:23:27 2018g updated on my desktop The update on my desktop was part of routine maintenance. Although Ubuntu is about as good as it gets in this area for a consumer-facing OS, we should be able to even better. Debian beat the deadline but Ubuntu (downstream from Debian) did not, my desktop had the wrong Morocco time for over two days, and my guess is that almost all cell phones and computers in Morocco still have the wrong data for Morocco. Reference: Kasraoui S. Benabdelkader: 68% of Moroccans Wanted an End to Time Changes. Morocco World News. 2018-10-31 13:44 +01. https://www.moroccoworldnews.com/2018/10/256539/

1 0

[PROPOSED] Fix Volgograd label in zone1970.tab
by Paul Eggert Oct. 31, 2018

Oct. 31, 2018

(Reported by Gleb Popov.) * zone.tab, zone1970.tab: Volgograd is now MSK+01. --- zone.tab | 2 +- zone1970.tab | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/zone.tab b/zone.tab index dcb6e1d..368a52d 100644 --- a/zone.tab +++ b/zone.tab @@ -332,9 +332,9 @@ RS +4450+02030 Europe/Belgrade RU +5443+02030 Europe/Kaliningrad MSK-01 - Kaliningrad RU +554521+0373704 Europe/Moscow MSK+00 - Moscow area RU +4457+03406 Europe/Simferopol MSK+00 - Crimea -RU +4844+04425 Europe/Volgograd MSK+00 - Volgograd RU +5836+04939 Europe/Kirov MSK+00 - Kirov RU +4621+04803 Europe/Astrakhan MSK+01 - Astrakhan +RU +4844+04425 Europe/Volgograd MSK+01 - Volgograd RU +5134+04602 Europe/Saratov MSK+01 - Saratov RU +5420+04824 Europe/Ulyanovsk MSK+01 - Ulyanovsk RU +5312+05009 Europe/Samara MSK+01 - Samara, Udmurtia diff --git a/zone1970.tab b/zone1970.tab index 7c86fb6..2729e6e 100644 --- a/zone1970.tab +++ b/zone1970.tab @@ -289,9 +289,9 @@ RS,BA,HR,ME,MK,SI +4450+02030 Europe/Belgrade RU +5443+02030 Europe/Kaliningrad MSK-01 - Kaliningrad RU +554521+0373704 Europe/Moscow MSK+00 - Moscow area RU +4457+03406 Europe/Simferopol MSK+00 - Crimea -RU +4844+04425 Europe/Volgograd MSK+00 - Volgograd RU +5836+04939 Europe/Kirov MSK+00 - Kirov RU +4621+04803 Europe/Astrakhan MSK+01 - Astrakhan +RU +4844+04425 Europe/Volgograd MSK+01 - Volgograd RU +5134+04602 Europe/Saratov MSK+01 - Saratov RU +5420+04824 Europe/Ulyanovsk MSK+01 - Ulyanovsk RU +5312+05009 Europe/Samara MSK+01 - Samara, Udmurtia -- 2.17.1

1 0

EU abolition of DST could be pushed back to 2021
by John Wilcock Oct. 30, 2018

Oct. 30, 2018

https://www.bbc.com/news/world-europe-46017347 > "If we aim to do this in 2019, as the [European] Commission suggested, > this will not be supported by the majority of member states," said > Austrian Transport Minister Norbert Hofer, who hosted his 27 EU > counterparts in Graz. > > Allowing until 2021 would help ensure the EU's three existing time > zones did not become a more complicated patchwork, Mr Hofer said. > -- John

1 0

zdump bug?
by Matt Johnson Oct. 29, 2018

Oct. 29, 2018

I notice when I run zdump like this: zdump /usr/share/zoneinfo/America/New_York The output is normal: America/New_York Sun Oct 28 18:23:35 2018 EDT But if I change to the America directory... cd /usr/share/zoneinfo/America zdump ./New_York The output is missing the abbreviation: ./New_York Sun Oct 28 22:23:48 2018 Is this expected? Seems like a subtle bug to me. The abbreviations are also missing with -v output. (Ran on Ubuntu Linux 16.04.5 LTS) Thanks, Matt

5 6