- tz - lists.iana.org

FYI Time zone used in Fort Pierre SD USA
by RICK MCDERMID Dec. 25, 2015

Dec. 25, 2015

FYI, see below for some information regarding the City of Fort Pierre SD USA time zone. It looks like Fort Pierre and the surrounding Stanley County unofficially use Central Time.. Rick McDermid, Chilliwack BC Canada rickmcdermid(a)shaw.ca ----- Original Message ----- From: "Administration" <Admin1(a)fortpierre.com> To: "RICK MCDERMID" <rickmcdermid(a)shaw.ca> Sent: Monday, December 21, 2015 1:46:47 PM Subject: RE: Question about time in Fort Pierre Hi Rick Yes, Fort Pierre is technically located in the Mountain time zone as is the rest of Stanley County. Most of Stanley County and Fort Pierre uses the Central time zone due to doing most of their business in Pierre so it simplifies schedules. I have lived in Stanley County all my life and it has been that way since I can remember. (43 years!) I hope this helps you. If you have any further questions let me know. Thanks! Kelly City of Fort Pierre From: RICK MCDERMID [mailto:rickmcdermid@shaw.ca] Sent: Monday, December 21, 2015 3:22 PM To: admin1(a)fortpierre.com Subject: Question about time in Fort Pierre Hello. I'm updating some geographic data, and I have a question about your time zone. I understand that Fort Pierre is officially on Mountain time, while Pierre is on Central time. However, based on your location right across the river, it looks like you might actually use the same time as Pierre. Could you tell me which time zone you use? If you do follow Central time like Pierre, do you know if the rest of Stanley County does likewise? Do you know if there is any history to the issue? If you do go by the unofficial Central time I will pass the info along to www.iana.org , a non-profit which (among other things) publishes a global time zone database used widely for computer apps and the like. Thanks for your help. Rick McDermid, Chilliwack BC Canada rickmcdermid(a)shaw.ca

4 4

Admins should check expiration date of leap second file
by Martin Burnicki Dec. 22, 2015

Dec. 22, 2015

Folks, I've just checked some of the commonly known sources for the leap second file to be used with NTP and found that some sites on the internet only provide outdated versions of the leap second file. Some of the files will expire on 28 December 2015. So if you have an NTP daemon running and a leap second file specified in the ntp.conf file you should check if you have a current copy of the file installed, or otherwise update the leap second file. Unlike earlier version of ntpd (up to 4.2.6*), current versions (4.2.8*) of the NTP daemon really evaluate the expiration date of the file, and don't accept outdated an outdated leap second file. For many NTP installations this doesn't really matter, but - if an applications expects a current TAI offset set in the OS kernel then it won't get the correct information without a valid leap second file - if a valid leap second file is available then the leap second information takes precedence over leap second announcements from upstream servers, etc., so a valid leap second files provides some protection against wrong leap second announcements from faulty upstream servers. The original leap second file from NIST is available via this link: ftp://time.nist.gov/pub/leap-seconds.3629404800 (current) ftp://time.nist.gov/pub/leap-seconds.list (link to current) and the current version expires 28 June 2016. However, unfortunately the NIST server is often not reachable. The IERS which decides whether a leap second is to be scheduled or not, is now also providing an own leap second file: https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.3651350400 (current) https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list (link to current) However, this file already expires on 28 January 2016, which is pretty early. I've already contacted the folks at IERS and asked them to set the expiration date to shortly before the next leap second event. I guess they will provide a new leap second file shortly after the next bulletin C has been published in January 2016. The USNO formerly also provided an own version of a leap second file via ftp://tycho.usno.navy.mil/pub/ntp/ However, on this web page there is only an outdated copy of the IERS file now, which expires on 28 December 2015. I've already tried to contact the folks at USNO and asked them to update their server, but haven't received a reply, yet. A copy of the current leap second file can also be found in the current Time Zone data package provided by the IANA. Since the IETF web site provides an unpacked copy of the tzdata archive the NIST file is also available here: http://www.ietf.org/timezones/data/ http://www.ietf.org/timezones/data/leap-seconds.list (shipped with tzdata, copy of a NIST file) Since this is a copy of the current NIST file this file is valid until 28 June 2016. Another copy of the current NIST leap second file is available via the Meinberg web site: http://www.meinberg.de/download/ntp/leap-seconds.list Hope this helps. Martin -- Martin Burnicki Senior Software Engineer MEINBERG Funkuhren GmbH & Co. KG Email: martin.burnicki(a)meinberg.de Phone: +49 (0)5281 9309-14 Fax: +49 (0)5281 9309-30 Lange Wand 9, 31812 Bad Pyrmont, Germany Amtsgericht Hannover 17HRA 100322 GeschÃ¤ftsfÃ¼hrer/Managing Directors: GÃ¼nter Meinberg, Werner Meinberg, Andre Hartmann, Heiko Gerstung Web: http://www.meinberg.de

1 0

[PROPOSED PATCH] Add Dublin Core profile attribute
by Paul Eggert Dec. 13, 2015

Dec. 13, 2015

* tz-link.htm: Add profile attribute to head element. See: http://dublincore.org/documents/2008/08/04/dc-html-notes/ --- tz-link.htm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tz-link.htm b/tz-link.htm index ca2f2bc..e448184 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -2,7 +2,7 @@ PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html> -<head> +<head profile="http://dublincore.org/documents/2008/08/04/dc-html/"> <title>Sources for Time Zone and Daylight Saving Time Data</title> <link rel="schema.DC" href="http://purl.org/DC/elements/1.1/"> <meta http-equiv="Content-type" content='text/html; charset="UTF-8"'> -- 2.1.0

2 4

[PATCH] Change Cayman abbreviations to CIST and CIDST
by Paul Eggert Dec. 11, 2015

Dec. 11, 2015

A bill to implement US-style daylight saving time has been published by the Cayman Islands Gazette, so it looks like our clock predictions are still on track. The bill gives Cayman-specific time zone abbreviations, though, so we need to change tzdata for that. * NEWS: Document this. * northamerica (Cayman): New rule. It is like the US since 2016, but with different LETTER/S. (America/Cayman): Use it. --- NEWS | 3 +++ northamerica | 17 +++++++++++------ 2 files changed, 14 insertions(+), 6 deletions(-) diff --git a/NEWS b/NEWS index 121e0e4..ac0369c 100644 --- a/NEWS +++ b/NEWS @@ -11,6 +11,9 @@ Unreleased, experimental changes America/Metlakatla switched from PST all year to AKST/AKDT on 2015-11-01 at 02:00. (Thanks to Steffen Thorsen.) + Time zone abbreviations for America/Cayman have been changed from + EST/EDT to CIST/CIDST, as per the 2015-11-25 daylight-saving bill. + Changes affecting future time stamps Asia/Tehran now has DST predictions for the year 2038 and later, diff --git a/northamerica b/northamerica index e916524..38a8beb 100644 --- a/northamerica +++ b/northamerica @@ -2688,16 +2688,21 @@ Zone Atlantic/Bermuda -4:19:18 - LMT 1930 Jan 1 2:00 # Hamilton # Cayman Is -# From Paul Eggert (2015-05-15): +# From Paul Eggert (2015-12-08): # The Cayman government has decided to introduce DST in 2016, the idea being -# to keep in sync with New York. The legislation hasn't passed but the change -# seems quite likely. See: Meade B. Cayman 27. -# http://www.cayman27.com.ky/2015/05/15/clock-ticks-toward-daylight-saving-ti… +# to keep in sync with New York. The enabling legislation has been published, +# and seems quite likely to be approved. See Cayman Islands +# Extraordinary Gazette No. 92 (2015-11-25), Supp. 2, which specifies the +# abbreviations CIST and CIDST. +# http://www.gov.ky/portal/pls/portal/docs/1/12274400.PDF + +# Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S +Rule Cayman 2016 max - Mar Sun>=8 2:00 1:00 D +Rule Cayman 2016 max - Nov Sun>=1 2:00 0 - Zone America/Cayman -5:25:32 - LMT 1890 # Georgetown -5:07:11 - KMT 1912 Feb # Kingston Mean Time - -5:00 - EST 2016 - -5:00 US E%sT + -5:00 Cayman CI%sST # Costa Rica -- 2.1.0

3 3

[PATCH 0/1] Allow 'backzone' to be incorporated in 'right' data
by Ian Abbott Dec. 10, 2015

Dec. 10, 2015

The REDO macro in the Makefile currently allows you to build POSIX data, 'right' data, or both sets with either the default. It also allows information from the 'backzone' file to be incorporated into the POSIX data set but not if the 'right' data is being built to. There may be some unlucky bar steward out there who needs to incorporate the 'backzone' file data into the 'right' data set, or into both the POSIX and 'right' data sets, so I added a few extra targets to the Makefile for your consideration. See patch in following email.

2 11

Request to include www.timejones.com - tz database version 2014.8
by Web Master Dec. 9, 2015

Dec. 9, 2015

Hi, Greetings! First of all immense thanks for the introduction of tz database to the world. We are writing from www.timejones.com, an ultra simple time and weather services portal that helps people with time and weather information for 150000 places on Earth. We have developed this web site using tz database version 2014.8/ PHP 5.4.39 and hosted on a Apache/2.2.29. Could you please kindly include www.timejones.com under the section "Web sites using recent versions of the tz database" in http://cs.ucla.edu/~eggert/tz/tz-link.htm ? Thanks in advance! Best Regards, Webmaster(a)timejones.com

3 2

[PATCH 1/1] * LICENSE: New file.
by James Knight Dec. 8, 2015

Dec. 8, 2015

Adding a license-specific file to aid in package management and other possible use cases. Signed-off-by: James Knight <james.knight(a)rockwellcollins.com> diff -Naur tz_a/LICENSE tz_b/LICENSE --- tz_a/LICENSE 1969-12-31 19:00:00.000000000 -0500 +++ tz_b/LICENSE 2015-10-23 17:59:01.702710278 -0400 @@ -0,0 +1,21 @@ +Unless otherwise specified, all files in the tz code and data are in +the public domain, so clarified as of 2009-05-17 by Arthur David Olson. +The few exceptions are code derived from BSD, which uses the BSD license. + +date.c and strftime.c: +---------------------- +Copyright (c) 1985, 1987, 1988 The Regents of the University of California. +All rights reserved. + +Redistribution and use in source and binary forms are permitted +provided that the above copyright notice and this paragraph are +duplicated in all such forms and that any documentation, +advertising materials, and other materials related to such +distribution and use acknowledge that the software was developed +by the University of California, Berkeley. The name of the +University may not be used to endorse or promote products derived +from this software without specific prior written permission. +THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR +IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED +WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. +

2 1

CCTZ time zone library for C++ from Google
by Tim Parenti Dec. 8, 2015

Dec. 8, 2015

FYI, last month, Google released and open-sourced cctz <https://github.com/google/cctz>, a new time zone library for C++. My favorite quote from the announcement <http://google-opensource.blogspot.com/2015/09/introducing-cctz-simple-time-…> on their Open Source Blog: > *"Time zones are logical and easy to use." —no one ever* -- Tim Parenti

6 9

Re: [tz] Question about historical TZData for North Carolina
by Paul Eggert Dec. 7, 2015

Dec. 7, 2015

On 12/07/2015 04:25 AM, Clifford Ribaudo wrote: > http://ncpedia.org/time-zones > > The relevant section of the article states that: > > On 28 Sept. 1947 North Carolina adopted Eastern Standard Time statewide. > > During World War I, North Carolina adopted Daylight Time for the periods 31 Mar.-27 Oct. 1918 and 30 Mar.-26 Oct. 1919. Between 1 Aug. 1941 and 9 Feb. 1942, state offices operated on Daylight Time; from 9 Feb. 1942 to 30 Sept. 1945, North Carolina implemented what President Franklin D. Roosevelt called "War Time." From 1946 to 1965 North Carolina did not observe Daylight Time, but since 1966 the state has followed the national schedule. > > So in summary that means we have: > > 1) Sep 28 1947 statewide adoption of ET > 2) Mar 31 - Oct 27 1918 Adopted Daylight Time > 3) Mar 30 - Oct 26 1919 Adopted Daylight Time > 4) Feb 9 1942 - Sep 30 1945 Adopted War Time > 5) 1946 - 1965 Daylight time NOT observed > 6) 1966 - Entire state adopts national schedule for Daylight time. > > So I would propose that this data be added to an America/North_Carolina entry in backzone That's useful info. Let me try to summarize what work would need to be done to get this in (and this may help to explain why it hasn't been done yet....). First, that source is better than nothing, but it has real problems. First, it cites secondary sources (Doane is an old astrology book if I'm not mistaken, and the DOT source is also secondary), and these secondary sources are often in error. Second, it summarizes the secondary sources without giving full details, e.g., it doesn't say which part of North Carolina formerly observed Central Time, and it doesn't give the times that switchovers occurred. Someone should read the secondary sources directly, or better yet, read the primary sources that they are based on, to get as many details as we can. Second, whatever data we come up with needs to be put in tzdata form, with commentary citing the sources. You can look at the existing 'northamerica' and 'backzone' files for examples, and read the tzfile man page (and the file 'Theory', which explains naming and in particular why we shouldn't use the name 'America/North_Carolina') for details. The result should be a patch to the file 'backone' in Git form. If that's all done and the patch goes in, you should be able to run 'make posix_packrat', and use the result in your programs.

1 0

Possible DST Discrepancies for Manitoba, Canada
by Rena B Dec. 7, 2015

Dec. 7, 2015

Across the board, I've come across a possible discrepancy that I can't seem to let go off. The years 1957 - 1963 in the data base for Manitoba. Winnipeg and Selkirk both switch for those years appropriately, but none of the other Manitoba towns I've tried have. My birth date is June 1957 in one of the town and I cannot find out if DST was province wide for that year. I believe there were 2 years in this time frame that Winnipeg did not subscribe to DST (1960-61). Would very much appreciate if you have the resources to look into this? If the rest of the towns in Manitoba followed Winnipeg/Selkirk, then there is a large error margin happening. Regards, Rena Bergman

3 2