- tz - lists.iana.org

[PATCH] Minor changes to iso3166.tab
by Jiri Bohac Nov. 17, 2016

Nov. 17, 2016

As noted in the file, the table intentionally differs from the ISO 3166 English names, mostly using even shorter names than the official short name. In a few cases, it seems to be out of sync with ISO for no good reason: Official changes in ISO, where new is same length or shorter than original: Cape Verde -> Cabo Verde Czech Republic -> Czechia UTF-8 now used elsewhere, so why not for Curaçao: Curacao -> Curaçao No good reason to differ from the standard?: Macau -> Macao Personally, I would also change "Britain" to "United Kingdom", I think it's where people would look first. But it would go from shorter to longer, so I did not include it in the patch. It's still much shorter than many other names. Would "United Kingdom" make sense here? --- iso3166.tab | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/iso3166.tab b/iso3166.tab index 7a8df2c..0e07afd 100644 --- a/iso3166.tab +++ b/iso3166.tab @@ -74,11 +74,11 @@ CN China CO Colombia CR Costa Rica CU Cuba -CV Cape Verde -CW Curacao +CV Cabo Verde +CW Curaçao CX Christmas Island CY Cyprus -CZ Czech Republic +CZ Czechia DE Germany DJ Djibouti DK Denmark @@ -170,7 +170,7 @@ MK Macedonia ML Mali MM Myanmar (Burma) MN Mongolia -MO Macau +MO Macao MP Northern Mariana Islands MQ Martinique MR Mauritania -- Jiri Bohac <jbohac(a)suse.cz> SUSE Labs, SUSE CZ

6 11

Hungary considers moving to +02 year-round
by Paul Eggert Nov. 17, 2016

Nov. 17, 2016

A bill to put Hungary on permanent EET (+02) has passed a parliament committee unanimously. The full parliament is scheduled to vote on it next week. Presumably this would require coordination with the EU, which may mean delays before the change would take effect. See: End of Hungaro-pessimism? - the times they are changing in the Hungarian Parliament. Hungary Today 2016-11-16. http://hungarytoday.hu/news/may-end-hungaro-pessimism-time-changing-questio… Horváth A. Vége az óraátállításnak? Magyar Nemzet 2016-11-16. http://mno.hu/gazdasag/vege-az-oraatallitasnak-1371621

1 0

Turkey ZoneInfo
by Sundeep Dasari Nov. 16, 2016

Nov. 16, 2016

Hi Iam trying to extract turkey zoneinfo from "tzdata2016i.tar.gz" package and is not successfully. I have done the following to extract turkey zone info: zic -d ./mytemp/ asia zic -d ./mytemp/ europe Turkey should be either in Europe or in Asia. Please provide me with your support in this regard. -- Thanks Sundeep.

3 2

tzdata2016g missing version information
by Howard Hinnant Nov. 12, 2016

Nov. 12, 2016

As is known, the version number no longer appears in the Makefile. The release notes in NEWS say: > To support the more-accurate version number, its > specification has moved from a line in the Makefile to a new > source file 'version’. The version file does not appear in the uncompressed tzdata2016g database. This is hurting my ability to report the version of the database to my clients. Can we please put a version file in the database? Howard

18 49

"impossible" glitch right at the DST changeover: it had to happen
by scs＠eskimo.com Nov. 11, 2016

Nov. 11, 2016

The mother in this story says she had a hard time "wrapping her head around it", but readers of this list will have little trouble: "Twins' Daylight Saving Time Birth Results in Bizarre Age Twist" http://abcnews.go.com/Lifestyle/twins-daylight-saving-time-birth-results-bi… Yes, one twin was born on the early morning of November 6 at 1:39, and his little brother was born 31 minutes later, at 1:10.

1 0

[PROPOSED] * CONTRIBUTING: Call the GitHub repository "development"
by Paul Eggert Nov. 11, 2016

Nov. 11, 2016

Instead of the old adjective "experimental". --- CONTRIBUTING | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING b/CONTRIBUTING index e40102e..22addd2 100644 --- a/CONTRIBUTING +++ b/CONTRIBUTING @@ -18,10 +18,10 @@ data should contain commentary citing reliable sources as justification. Please submit changes against either the latest release in -<ftp://ftp.iana.org/tz/> or the master branch of the experimental -Git repository. If you use Git the following workflow may be helpful: +<ftp://ftp.iana.org/tz/> or the master branch of the development +repository. If you use Git the following workflow may be helpful: - * Copy the experimental repository. + * Copy the development repository. git clone https://github.com/eggert/tz.git cd tz -- 2.7.4

1 0

Re: [tz] tzdata2016g missing version information
by Dempsey, Peter Nov. 10, 2016

Nov. 10, 2016

Hi, On 09/29/2016 08:590 AM, Eggert, Paul wrote: >Yes, it appears that the Oracle software assumed that the Makefile would have a VERSION line that specifies the version number. That assumption was never documented or guaranteed and is no longer valid. >Perhaps you can work around the problem by modifying the Makefile to say "VERSION = 2016g" (I don't have the Oracle software and so can't easily test this). >We are discussing a better way to address this problem in the future. @Paul Eggert: The Oracle Timezone Update Tool can be downloaded from here: http://www.oracle.com/technetwork/java/javase/documentation/tzupdater-readm…. This tool has two ways of updating the timezone database: 1. Online where the timezone database is downloaded from: -l http://www.iana.org/time-zones/repository/tzdata-latest.tar.gz 2. Offline where the timezone database is loaded locally: -l file:///tmp/tzdata2016g.tar.gz The tzdata file published on the IANA site needs to include the VERSION information so that this tool can work. When do you think this can be provided? I need to test the Oracle Timezone Updater Tool as soon as possible because I have customers with critical systems dependent on the time zone database. @Susan Abraham: I don't know if you are involved with the Timezone Updater Tool but this tool currently can't update the timezone because the database doesn't contain the VERSION information. @Kim Davies: I am adding you to keep you directly in the loop. Best regards, Pete -- This electronic message may contain proprietary and confidential information of Verint Systems Inc., its affiliates and/or subsidiaries. The information is intended to be for the use of the individual(s) or entity(ies) named above. If you are not the intended recipient (or authorized to receive this e-mail for the intended recipient), you may not use, copy, disclose or distribute to anyone this message or any information contained in this message. If you have received this electronic message in error, please notify us by replying to this e-mail.

7 15

Danish Time not UTC
by Brian Inglis Nov. 10, 2016

Nov. 10, 2016

According to the DK NMI DANIAmet: https://daniamet.dk/en/nmi/time-and-frequency/ "The law on time (Law No 83, 29/03/1893) prescribe that the time in Denmark is determined by mean solar time and not the UTC time." -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

6 10

Failed to update tzdata2016g and higer with tzupdater
by Sawadee.Prakayphetchara＠thomsonreuters.com Nov. 9, 2016

Nov. 9, 2016

Hi, We found an issue when try to update timezone with the tzdata2016g.tar.gz - tzdata2016i.tar.gz The problem is that VERSION in the Makefile is not correct, the correct value should match with tz version i.e. 2016i not unknown. # Version number for the distribution, overridden in the 'tarballs' rule below. VERSION= unknown The workaround has been mention in, http://stackoverflow.com/questions/39832866/tzupdater-failing-with-tzdata20… * Update Makefile of http://www.iana.org/time-zones/repository/releases/tzdata2016g.tar.gz: Original value of VERSION variable is unknown and you need to update it to 2016g. * Regenerate tzdata2016g.tar.gz.sha512 file So far we need to apply the workaround on each release. It would be great if you can correct the version in next release? Regards, Sawadee M.

2 1

Timezones - what's so hard?
by Michael Douglass Nov. 7, 2016

Nov. 7, 2016

http://www.gocomics.com/pearlsbeforeswine#mutable_1511244

3 2

[PROPOSED] Port ar usage to POSIX
by Paul Eggert Nov. 7, 2016

Nov. 7, 2016

* Makefile (libtz.a): Use 'ar -rc' instead of 'ar ru', as 'ar -rc' is standardized by POSIX and GNU 'ar' 2.26.1 (Ubuntu 16.04.1) warns about the obsolete form 'ar ru'. --- Makefile | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Makefile b/Makefile index 74b950c..1b714a8 100644 --- a/Makefile +++ b/Makefile @@ -542,7 +542,8 @@ force_tzs: $(TZS_NEW) cp $(TZS_NEW) $(TZS) libtz.a: $(LIBOBJS) - $(AR) ru $@ $(LIBOBJS) + rm -f $@ + $(AR) -rc $@ $(LIBOBJS) $(RANLIB) $@ date: $(DATEOBJS) -- 2.7.4

1 0

Compiler warning in tzcode2016g about SIZE_MAX being wider than int
by Tom Lane Nov. 6, 2016

Nov. 6, 2016

When trying to build 2016g using macOS's current compiler (or, probably, any reasonably late-model version of clang), I get cc -DTZDIR=\"/usr/local/etc/zoneinfo\" -c -o zic.o zic.c zic.c:434:51: warning: implicit conversion from 'unsigned long long' to 'int' changes value from 18446744073709551615 to -1 [-Wconstant-conversion] int amax = nitems_max < SIZE_MAX ? nitems_max : SIZE_MAX; ~~~~ ^~~~~~~~ /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/stdint.h:153:20: note: expanded from macro 'SIZE_MAX' #define SIZE_MAX UINT64_MAX ^~~~~~~~~~ /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/stdint.h:87:27: note: expanded from macro 'UINT64_MAX' #define UINT64_MAX 18446744073709551615ULL ^~~~~~~~~~~~~~~~~~~~~~~ 1 warning generated. Or in other words, clang is pointing out, quite correctly, that SIZE_MAX won't fit in an int. This doesn't represent a runtime bug because the condition "nitems_max < SIZE_MAX" can never fail, but that just begs the question why have it. I am not aware of any C implementation that has ever had INT_MAX > SIZE_MAX, and surely there are none in use today. I suggest, therefore, a fix along the lines of $ diff -u zic.c~ zic.c --- zic.c~ 2016-09-06 00:39:50.000000000 -0400 +++ zic.c 2016-10-20 13:06:39.000000000 -0400 @@ -431,8 +431,7 @@ return ptr; else { int nitems_max = INT_MAX - WORK_AROUND_QTBUG_53071; - int amax = nitems_max < SIZE_MAX ? nitems_max : SIZE_MAX; - if ((amax - 1) / 3 * 2 < *nitems_alloc) + if ((nitems_max - 1) / 3 * 2 < *nitems_alloc) memory_exhausted(_("int overflow")); *nitems_alloc = *nitems_alloc + (*nitems_alloc >> 1) + 1; return erealloc(ptr, size_product(*nitems_alloc, itemsize)); Alternatively one might think of changing the types of nitems_max and amax to size_t --- but that would just make it even more crystal clear that the "nitems_max < SIZE_MAX" conditional is useless. And if, somewhere, one did find a C implementation in which size_t is narrower than int, that coding wouldn't work at all. Basically I don't see a way of dealing with this that is superior to just assuming that INT_MAX is less than or equal to SIZE_MAX. regards, tom lane

4 8

Daylight saving in Trkey problem
by Caner Aydinbey Nov. 6, 2016

Nov. 6, 2016

Hello. We have linux machine and we have app in there. FOr date command, it shows true date but in spring boot application, we cant get true date. It iss 1 hour later. So we follow guides to update but we cant manage. for example here http://www.oracle.com/technetwork/java/javase/tzupdater-readme-136440.html#… Please suggest us something to do. -- Caner Aydin Software Developer Infoowl Software Solutions & Consultancy +90 542 788 62 64 <%2B90%20530%20960%2035%2053> www.infoowl.net

3 4

Tonga returns to DST on 2016-11-06
by Tim Parenti Nov. 6, 2016

Nov. 6, 2016

Tonga will observe DST from 2016-11-06 02:00 until 2017-01-15 03:00, in line with Fiji. http://mic.gov.to/news-today/press-releases/6375-daylight-saving-set-to-run… This came through as a pull request on the Github repo: https://github.com/eggert/tz/pull/19 Originally submitted patch and proposed follow-up attached. -- Tim Parenti

10 27

zic fails for soft-links-only target volume
by Tom Lane Nov. 4, 2016

Nov. 4, 2016

I received a complaint that zic recently started to fail when the target directory is on a volume that doesn't support hard links. (The complainant is using some weird VMware Fusion setup, but I think this might be true on Windows generally.) It used to go through just fine, creating symlinks instead, but as of 2016g it fails with something like ./zic: link from /home/postgres/testversion/share/timezone/US/Eastern failed: Operation not permitted It appears to me that the problem is that commit 35484e98c broke the case of linking to an existing symlink. This happened because itsdir() was modified to return 2 not 0 for a symlink, but dolink() throws an EPERM error for that, because it wasn't taught about the change. There's no reason to disallow that case, so I propose this patch: diff --git a/zic.c b/zic.c *** a/zic.c --- b/zic.c *************** dolink(char const *fromfield, char const *** 824,830 **** ** there's a fair chance of root running us. */ fromisdir = itsdir(fromfield); ! if (fromisdir) { char const *e = strerror(fromisdir < 0 ? errno : EPERM); fprintf(stderr, _("%s: link from %s/%s failed: %s\n"), progname, directory, fromfield, e); --- 824,830 ---- ** there's a fair chance of root running us. */ fromisdir = itsdir(fromfield); ! if (fromisdir < 0 || fromisdir == 1) { char const *e = strerror(fromisdir < 0 ? errno : EPERM); fprintf(stderr, _("%s: link from %s/%s failed: %s\n"), progname, directory, fromfield, e); BTW, you can test this behavior without needing to have such a volume at hand, by forcing the link() attempt to fail like this: *************** dolink(char const *fromfield, char const *** 840,845 **** --- 840,846 ---- progname, directory, tofield, e); exit(EXIT_FAILURE); } + staysymlink = true; // for testing purposes only!! link_errno = (staysymlink ? ENOTSUP : link(fromfield, tofield) == 0 ? 0 : errno); if (link_errno == ENOENT && !todirs_made) { regards, tom lane

2 7

Why did you rename Russian zone name abbreviations
by Sergei Turchanov Nov. 3, 2016

Nov. 3, 2016

Hello! https://github.com/eggert/tz/commit/1ac038c2c3f25f7211474ae08feb6afb820 e35fe Why did you rename Russian zone name abbreviations? Can you provide a rationale for this change? This change breaks date parsing, etc... With best regards, Sergei Turchanov.

9 22

[PROPOSED] Fix EEST typos in Palestine before 1948
by Paul Eggert Nov. 3, 2016

Nov. 3, 2016

* NEWS: Document this. * asia (Asia/Gaza, Asia/Hebron): Fix typos, to use "EEST" instead of "EET" when abbreviating summer time before 1948. --- NEWS | 8 ++++++++ asia | 4 ++-- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/NEWS b/NEWS index da5c2a5..db9f03d 100644 --- a/NEWS +++ b/NEWS @@ -1,5 +1,13 @@ News for the tz database +Unreleased, experimental changes + + Changes to past time zone abbreviations + + Asia/Gaza and Asia/Hebron now use "EEST", not "EET", to denote + summer time before 1948. The old use of "EET" was a typo. + + Release 2016i - 2016-11-01 23:19:52 -0700 Briefly: Cyprus split into two time zones on 2016-10-30, and Tonga diff --git a/asia b/asia index 67164b3..bb7534a 100644 --- a/asia +++ b/asia @@ -2616,7 +2616,7 @@ Rule Palestine 2016 max - Oct lastSat 1:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Gaza 2:17:52 - LMT 1900 Oct - 2:00 Zion EET 1948 May 15 + 2:00 Zion EET/EEST 1948 May 15 2:00 EgyptAsia EE%sT 1967 Jun 5 2:00 Zion I%sT 1996 2:00 Jordan EE%sT 1999 @@ -2629,7 +2629,7 @@ Zone Asia/Gaza 2:17:52 - LMT 1900 Oct 2:00 Palestine EE%sT Zone Asia/Hebron 2:20:23 - LMT 1900 Oct - 2:00 Zion EET 1948 May 15 + 2:00 Zion EET/EEST 1948 May 15 2:00 EgyptAsia EE%sT 1967 Jun 5 2:00 Zion I%sT 1996 2:00 Jordan EE%sT 1999 -- 2.7.4

1 0

Re: [tz] Why did you rename Russian zone name abbreviations
by Paul Eggert Nov. 3, 2016

Nov. 3, 2016

On 11/02/2016 08:50 AM, turchanov(a)vl.ru wrote: > ... having "date" command output "Wed Nov 2 09:54:58 +10 2016" make > it very difficult to understand where the system is. That's fine, as the "date" command is supposed to be about *when*, not about *where*. > 2. Since the inception of tzdata Olson stated rules for abbreviated > names clearly and unambiguously > (https://github.com/eggert/tz/blob/master/Theory) That old guideline has been deprecated, as mentioned in the Theory file. > 3. I have an impression that you (un-)intentionally confuse an > abbreviated name with a GMT offset. No, the idea is that if there is no common English-language abbreviation for a time zone, tzdata uses a numeric abbreviation instead. > > if one needed a GMT offset it would have used %z-family flags. The problem is not that software needs a GMT offset. It's that software unwisely requires a time zone abbreviation even when no such abbreviation exists in common English-language practice. Although we could simply leave the abbreviation empty in this case, it's more useful to fill it with a placeholder that conveys information to users of applications that unwisely output the abbreviation as-is. > By changing the abbreviated zone name you in effect change the > original full zone name. Why didn't change Asia/Vladivostok to > Asia/+10 as well?! That wouldn't work, as Vladivostok was at +11 before 2014, and at +09 before 2011. Even in the US, where alphabetic time zone abbreviations are common, we wouldn't link America/Indiana/Petersburg to US/Eastern, because Petersburg observed Central Time before 2007. > > 5. You justify your decision to remove abbreviated names by declaring > them as an "invention". Yes. I invented these abbreviations. I didn't use any formal procedure. The (now-deprecated) guideline about them in the Theory file was written after the fact, partly in an attempt to justify them. When I invented those abbreviations, POSIX supported only alphabetic-only abbreviations. Also, I was naive about Russia: I thought that it kept time zones like the US does and that US-style alphabetic abbreviations therefore made sense for it. Nowadays, though, POSIX allows numeric abbreviations, and I know more about Russian practice. From an English-speaking point of view, abbreviations like VLAT are misleading because they imply that there is a time zone at a fixed offset from UTC called "VLAT", which is how abbreviations like "PST", "GMT", and "CET" work. However, abbreviations like "VLAT" do not correspond to fixed UTC offsets, and this is something that English-speakers are typically not expecting or accustomed to. So even if "VLAT" were widely used by Russian speakers, it would still be dubious as an abbreviation in English-language tzdata. I agree that the current situation could be improved, and that there could be a better way to localize time zone abbreviations. I expect this is an effort that should be under the CLDR umbrella, as they're the localization gurus. It may be that we need a better API for getting at localized abbreviations. Certainly the tzcode strftime.c is incomplete here, as it doesn't even support Russian month names, much less genitive-case Russian dates (does CLDR handle that correctly? if not, it should...).

6 10

Latest tzdata2016
by Raymond Kumar Nov. 3, 2016

Nov. 3, 2016

Hi I would like to have a latest patch for tzdata. There were some changes performed on Tonga time zone and we need this patch as Tonga DST is from this week 5th November and we would like to apply this patch on systems. Thanks, Raymond Kumar Head of Billing & Products +6797015315 ________________________________ Notice of Confidentiality: The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system.

2 1

[tz-announce] 2016i release of tz code and data available
by Paul Eggert Nov. 3, 2016

Nov. 3, 2016

The 2016i 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: Cyprus split into two time zones on 2016-10-30, and Tonga reintroduces DST on 2016-11-06. Changes to future time stamps Pacific/Tongatapu begins DST on 2016-11-06 at 02:00, ending on 2017-01-15 at 03:00. Assume future observances in Tonga will be from the first Sunday in November through the third Sunday in January, like Fiji. (Thanks to Pulu ʻAnau.) Switch to numeric time zone abbreviations for this zone. Changes to past and future time stamps Northern Cyprus is now +03 year round, causing a split in Cyprus time zones starting 2016-10-30 at 04:00. This creates a zone Asia/Famagusta. (Thanks to Even Scharning and Matt Johnson.) Antarctica/Casey switched from +08 to +11 on 2016-10-22. (Thanks to Steffen Thorsen.) Changes to past time stamps Several corrections were made for pre-1975 time stamps in Italy. These affect Europe/Malta, Europe/Rome, Europe/San_Marino, and Europe/Vatican. First, the 1893-11-01 00:00 transition in Italy used the new UT offset (+01), not the old (+00:49:56). (Thanks to Michael Deckers.) Second, rules for daylight saving in Italy were changed to agree with Italy's National Institute of Metrological Research (INRiM) except for 1944, as follows (thanks to Pierpaolo Bernardi, Brian Inglis, and Michael Deckers): The 1916-06-03 transition was at 24:00, not 00:00. The 1916-10-01, 1919-10-05, and 1920-09-19 transitions were at 00:00, not 01:00. The 1917-09-30 and 1918-10-06 transitions were at 24:00, not 01:00. The 1944-09-17 transition was at 03:00, not 01:00. This particular change is taken from Italian law as INRiM's table, (which says 02:00) appears to have a typo here. Also, keep the 1944-04-03 transition for Europe/Rome, as Rome was controlled by Germany then. The 1967-1970 and 1972-1974 fallback transitions were at 01:00, not 00:00. Changes to code The code should now be buildable on AmigaOS merely by setting the appropriate Makefile variables. (From a patch by Carsten Larsen.) Here are links to the release files: ftp://ftp.iana.org/tz/releases/tzcode2016i.tar.gz ftp://ftp.iana.org/tz/releases/tzdata2016i.tar.gz ftp://ftp.iana.org/tz/releases/tzdb-2016i.tar.lz The files are also available via HTTP as follows: http://www.iana.org/time-zones/repository/releases/tzcode2016i.tar.gz http://www.iana.org/time-zones/repository/releases/tzdata2016i.tar.gz http://www.iana.org/time-zones/repository/releases/tzdb-2016i.tar.lz As usual, links to the latest release files are here: http://www.iana.org/time-zones/repository/tzcode-latest.tar.gz http://www.iana.org/time-zones/repository/tzdata-latest.tar.gz http://www.iana.org/time-zones/repository/tzdb-latest.tar.lz ftp://ftp.iana.org/tz/tzcode-latest.tar.gz ftp://ftp.iana.org/tz/tzdata-latest.tar.gz ftp://ftp.iana.org/tz/tzdb-latest.tar.lz 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 9774c293b7ea6ec7be851cb0b2a0807840e6793e dated 2016-11-01 23:19:52 -0700 and tagged '2016i' in the experimental github repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 93be791491a76f9d489f4bce8b392b2af6bdfb9a21f7efb7c6948da5c27db9782f7a725dd53d755e9488de000a4af5b75de650e7dac8c01ef8fbbd2719f9cd07 tzcode2016i.tar.gz 801059f43c91798cf69fb2ae77c1ffab8d06987325081511d573febde19ae423e7432c2b65c7c256077bbdb1b359e010302955786e18f2697bb263c4e0f1cc91 tzdata2016i.tar.gz 7e71521ed61ae2aca941b88c6308f3e6f90dc3356fef323c15b6907aefb827c11d19e2516b07c205f0365be736fbce3023bb9717a6a6a50964584b3f7b3baa81 tzdb-2016i.tar.lz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJYGYaQAAoJEO2X6Q5iqn402R0P/3AMlJCx/gABznqJhidPNCph dQikzUgHZaYyMNHdUYmxVV8gxjopMrFhKdJPalnb2mUcekAthc6h13TpDFvo0xKJ plBDNvA1hFXuHgLBrEJbtABFEIWLplfSJREAlvu41/OdtmXKnKINcg9pVD9Xm2hT TRWQVTXEc3wOFxGctfefXfGmyGK4Fc1UI2dYM8sS22pJrXeFrHZmJOfxL7r06qtM TSyDlL2o43V1i3IQVhwgkTKE8Q8cxOZVGqFjUu4urWGYIyK4x2ap0ZYaEqLeYBgx qzdTrINYIiSG5Qr9g/Uf4hNQ0fH2Vif+GaJOVCAJet+DL3Rj32hKLJC0x3L4+xx3 KmlYGOGh869kWu8h2qu/2ac4b0657SchgCx9BrZZ5m/bVYQeqOKLU5b2g/WLILv8 Tj0UPQqB6Lj0wzdSwUZN8V20nUaaQmoDpMDrt8/oZ5pwGCUSigLPPINu4Po6Iiyk leHfnAZj28xEoeJI77O2DJ4HO9nz8XvtOQUMxvixLvcIiLhUpeKFwrF+B5TXtOzZ pQ3M/pON7DytxM36ykArTwj7Pct+uwOJbkIVUIAdVE/cXmtlLR2f1VC6DQhO8x4N aaeKIXEYVioWCDWETi+OUWUyd+A2Fn0ykls6oGwhCdeHAeTRINsTesoBoQbh6/i4 1f6Fg4z5hNUZZyYfwp/j =V12P -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJYGYaQAAoJEO2X6Q5iqn40uykQAIlYwx+ZXwTh7f5GncBFvbkB A+zrwU2qFqLqy2ikyccUcs6LXbdxw5q9xb1pT1AEt7nKGqK2n7EF4TtbnYTLPijr e/A9WWzDozBDl4ExyG8TH/Zz8KcwPhbX9oq6+he7KYN2FwLwj/JEKWfp7esAsjqa CvMFGElUQMnRtv6PGfjYifU+5BYf0K6VhJ+iPpfb7NHiAEMBztt0mIlWKNB/hxuD 4ucWsr+k32NdlKgfxTDwfcEq9hd4wMmYfaTmxi1JUYmZ2UUr/ofns5VNYn4LKYz4 l7tN5cITS01fbcb/lYMMdeKnurxpNXvhjFiYJvCUGo1/ZOxBrUSF76JvjqLhKECw tD69X4zWEuAdgFIJfnpK7PAquW9YpkYhyeGLGvYQxIQTZVTRnyxlVJGFMinD2XFT /yjDMZDsdGReN0oTkxJ/vTnh45lNezBs9JJ2Quuxe/ZvT6ujRqK0yGSReYhpiKzz 6CS9PS5Ojgo0mvKJszccKgxu8nYAL3Odfr8CuVnWPPbhHBzM2TKQU9aXeJa7Nd6t MZZD6fp2qEFUd9qGRdz3E8UYSGCIYJfm85lx/DjxHiLQWdglfvwdGx4b3fsbCoKy iOUChS+12qShRHreKcNOnkaRe18J+5/unN3uh6aJoXmoCGbjcYjSIl5kF5Mb/iaN Fb0MCCcov7527m9ZVHNp =O/rc -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJYGYaQAAoJEO2X6Q5iqn40P7YQALUKbftldhSEHGo7WcQFBqO4 oKF3KbnbxgU1kKS3sMPjM2WfFbPSGotBZwAmRiJSuAhCQuT7IOdzlnH0A+gNHv1F SOz/w7qJPDPOze9hxy9oVLHK7kz2NsIqLoCQUKb48Bo/6CakhQXf0Bh/OgsAYCUe DtXk7AEJvRRb3V5z448cUqjPCW55zIEdiG7hC23rRQr4ETnCU5rfMXDLGD176NQl wm8uWGClqqPIFG1T5G9I3yKUZemlTjPi6dCRFWtCzGM1yKhCXceAA2OBx//LG8K2 nOhDwUwNMXdh7hRPMQQq/tbP1etkeNopMCQU+z0+eNGPR26IsWL3ouEAKO0j6DKy 1NoykCXjEZV0V8dNxU0mPWZ+oESbxgSML3FDlMPsuDar40eTTLpz3kg7aAb+fxTB FgL+HD3LPalOfIu/BM494EwggCsM3waAjRvhASNguWCOxGQVDQTVQoASpyPlyw2X d3Sdpot0o0ed998lDEFAvBOILW19lTDxgHYBKMTK8McE/UW/UGFHliH1oxFz+H1g kyMlJ7LWYaFN+G1p4qo6+LHddUa4hl50x8QYv3FZe6q5UOGEB7qMQq/40mMtFQWU yuvL/bmPqeYgsp3slZM9t/trzxwIDYe+S4508tn+6zQ0Ddg37COXoLvozGFI8g7R cqjLOztN8+7qZcotVR88 =BqkM -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

[PROPOSED PATCH] Cyprus is splitting into two time zones
by Paul Eggert Nov. 2, 2016

Nov. 2, 2016

Add a zone Asia/North_Nicosia for North Cyprus. * NEWS: Document this. * asia, zone.tab, zone1970.tab (Asia/North_Nicosia): New zone. --- NEWS | 5 +++-- asia | 11 ++++++++++- zone.tab | 3 ++- zone1970.tab | 3 ++- 4 files changed, 17 insertions(+), 5 deletions(-) diff --git a/NEWS b/NEWS index a4af3b2..64233bf 100644 --- a/NEWS +++ b/NEWS @@ -5,8 +5,9 @@ Unreleased, experimental changes Changes to future time stamps Turkey switched from EET/EEST (+02/+03) to permanent +03, - effective 2016-09-07. (Thanks to Burak AYDIN.) Use "+03" rather - than an invented abbreviation for the new time. + effective 2016-09-07. (Thanks to Burak AYDIN.) Northern Cyprus + followed suit the next day, which creates a zone Asia/North_Nicosia. + Use "+03" rather than an invented abbreviation for the new time. New leap second 2016-12-31 23:59:60 UTC as per IERS Bulletin C 52. (Thanks to Tim Parenti.) diff --git a/asia b/asia index e285326..4462cd4 100644 --- a/asia +++ b/asia @@ -773,6 +773,12 @@ Zone Asia/Macau 7:34:20 - LMT 1912 Jan 1 # Cyprus # # Milne says the Eastern Telegraph Company used 2:14:00. Stick with LMT. +# IATA SSIM (1998-09) has Cyprus using EU rules for the first time. +# +# From Paul Eggert (2016-09-09): +# Yesterday's Cyprus Mail reports that Northern Cyprus followed Turkey's +# lead and switched from +02/+03 to +03 year-round. +# http://cyprus-mail.com/2016/09/08/two-time-zones-cyprus-turkey-will-not-tur… # # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Cyprus 1975 only - Apr 13 0:00 1:00 S @@ -788,7 +794,10 @@ Rule Cyprus 1981 1998 - Mar lastSun 0:00 1:00 S Zone Asia/Nicosia 2:13:28 - LMT 1921 Nov 14 2:00 Cyprus EE%sT 1998 Sep 2:00 EUAsia EE%sT -# IATA SSIM (1998-09) has Cyprus using EU rules for the first time. +Zone Asia/North_Nicosia 2:13:27 - LMT 1921 Nov 14 + 2:00 Cyprus EE%sT 1998 Sep + 2:00 EUAsia EE%sT 2016 Sep 8 + 3:00 - +03 # Classically, Cyprus belongs to Asia; e.g. see Herodotus, Histories, I.72. # However, for various reasons many users expect to find it under Europe. diff --git a/zone.tab b/zone.tab index bf1bb71..15989f4 100644 --- a/zone.tab +++ b/zone.tab @@ -152,7 +152,8 @@ CU +2308-08222 America/Havana CV +1455-02331 Atlantic/Cape_Verde CW +1211-06900 America/Curacao CX -1025+10543 Indian/Christmas -CY +3510+03322 Asia/Nicosia +CY +3510+03322 Asia/Nicosia Cyprus (most areas) +CY +3511+03322 Asia/North_Nicosia North Cyprus CZ +5005+01426 Europe/Prague DE +5230+01322 Europe/Berlin Germany (most areas) DE +4742+00841 Europe/Busingen Busingen diff --git a/zone1970.tab b/zone1970.tab index 49f0b0b..efe27b1 100644 --- a/zone1970.tab +++ b/zone1970.tab @@ -144,7 +144,8 @@ CU +2308-08222 America/Havana CV +1455-02331 Atlantic/Cape_Verde CW,AW,BQ,SX +1211-06900 America/Curacao CX -1025+10543 Indian/Christmas -CY +3510+03322 Asia/Nicosia +CY +3510+03322 Asia/Nicosia Cyprus (most areas) +CY +3511+03322 Asia/North_Nicosia North Cyprus CZ,SK +5005+01426 Europe/Prague DE +5230+01322 Europe/Berlin Germany (most areas) DK +5540+01235 Europe/Copenhagen -- 2.7.4

11 23

Re: [tz] Cyprus is splitting into two time zones
by Evan Siroky Nov. 2, 2016

Nov. 2, 2016

Regarding the buffer zone, according to this Wikipedia Article (https://en.wikipedia.org/wiki/United_Nations_Buffer_Zone_in_Cyprus) "Turkish forces built a barrier on the zone's northern side". So maybe everything north of the buffer zone would be considered Asia/Famagusta and the whole buffer zone plus south of the buffer zone would be Asia/Nicosia.

1 0

www.timeanddate.com provides different data
by Gintare Statkute Nov. 2, 2016

Nov. 2, 2016

Dear sir/madam On this website i find the following data: https://www.timeanddate.com/time/zone/uk/london 2015Sun, 29 Mar, 01:00GMT <https://www.timeanddate.com/time/zones/gmt> → BST <https://www.timeanddate.com/time/zones/bst>+1 hour (DST start)UTC+1h Sun, 25 Oct, 02:00BST <https://www.timeanddate.com/time/zones/bst> → GMT <https://www.timeanddate.com/time/zones/gmt>-1 hour (DST end) <https://www.timeanddate.com/news/time/europe-dst-end-2015.html>UTC 2016 Sun, 27 Mar, 01:00GMT <https://www.timeanddate.com/time/zones/gmt> → BST <https://www.timeanddate.com/time/zones/bst>+1 hour (DST start) <https://www.timeanddate.com/news/time/europe-starts-dst-2016.html>UTC+1h Sun, 30 Oct, 02:00BST <https://www.timeanddate.com/time/zones/bst> → GMT <https://www.timeanddate.com/time/zones/gmt>-1 hour (DST end) <https://www.timeanddate.com/news/time/eu-debate-dst.html>UTC 2017 Sun, 26 Mar, 01:00GMT <https://www.timeanddate.com/time/zones/gmt> → BST <https://www.timeanddate.com/time/zones/bst>+1 hour (DST start)UTC+1h Sun, 29 Oct, 02:00BST <https://www.timeanddate.com/time/zones/bst> → GMT <https://www.timeanddate.com/time/zones/gmt>-1 hour (DST end)UTC 2018 Sun, 25 Mar, 01:00GMT <https://www.timeanddate.com/time/zones/gmt> → BST <https://www.timeanddate.com/time/zones/bst>+1 hour (DST start)UTC+1h Sun, 28 Oct, 02:00BST <https://www.timeanddate.com/time/zones/bst> → GMT <https://www.timeanddate.com/time/zones/gmt>-1 hour (DST end)UTC 2019 Sun, 31 Mar, 01:00GMT <https://www.timeanddate.com/time/zones/gmt> → BST <https://www.timeanddate.com/time/zones/bst>+1 hour (DST start)UTC+1h Sun, 27 Oct, 02:00BST <https://www.timeanddate.com/time/zones/bst> → GMT <https://www.timeanddate.com/time/zones/gmt>-1 hour (DST end)UTC As you can see, the Europe/London time change rule is different every year . But i can not find this information on yor data distribution. https://www.iana.org/time-zones For europe, london you give: # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/London -0:01:15 - LMT 1847 Dec 1 0:00s 0:00 GB-Eire %s 1968 Oct 27 1:00 - BST 1971 Oct 31 2:00u 0:00 GB-Eire %s 1996 0:00 EU GMT/BST Maybe i do not understand how to use your data? I put the question on stackoverflow: http://stackoverflow.com/questions/40360032/iana-internet-assigned-numbers-… regards, -- *Gintare Statkute*

4 3

[PATCH] Minor web page updates
by Paul Eggert Nov. 2, 2016

Nov. 2, 2016

* tz-art.htm (Comics): Add xkcd 1179. * tz-link.htm: Remove link to gmane, which no longer works. Update other links. Mention RFC 5905. --- tz-art.htm | 3 ++- tz-link.htm | 10 ++++------ 2 files changed, 6 insertions(+), 7 deletions(-) diff --git a/tz-art.htm b/tz-art.htm index 0a2b427..8ec9e21 100644 --- a/tz-art.htm +++ b/tz-art.htm @@ -438,7 +438,8 @@ Supernaw.</td></tr> The webcomic xkcd has the strip "<a href='http://xkcd.com/673/'>The Sun</a>" (2009-12-09) and the panels "<a href='http://xkcd.com/1017/'>Backward in Time</a>" (2012-02-14), -"<a href='http://xkcd.com/1061/'>EST</a>" (2012-05-28), and +"<a href='http://xkcd.com/1061/'>EST</a>" (2012-05-28), +"<a href='http://xkcd.com/1179/'>ISO 8601</a>" (2013-02-27), "<a href='http://xkcd.com/1335/'>Now</a>" (2014-02-26), and "<a href='http://xkcd.com/1655/'>Doomsday Clock</a>" (2016-03-14). The related book What If? has an entry diff --git a/tz-link.htm b/tz-link.htm index 088ba2d..aec8a1c 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -10,7 +10,7 @@ content="Sources for time zone and daylight saving time data"> <meta name="DC.Creator" content="Eggert, Paul"> <meta name="DC.Contributor" content="Olson, Arthur David"> -<meta name="DC.Date" content="2016-10-21"> +<meta name="DC.Date" content="2016-11-01"> <meta name="DC.Description" content="Sources of information about time zones and daylight saving time"> <meta name="DC.Identifier" @@ -158,9 +158,7 @@ The <code><abbr>tz</abbr></code> code and data are by no means authoritative. If you find errors, please send changes to the <a href="mailto:tz@iana.org">time zone mailing list</a>. You can also <a -href="http://news.gmane.org/gmane.comp.time.tz">browse recent -messages</a> sent to the mailing list, <a -href="https://mm.icann.org/mailman/listinfo/tz">subscribe</a> to it, +href="https://mm.icann.org/mailman/listinfo/tz">subscribe</a> to it and browse the <a href="http://mm.icann.org/pipermail/tz/">archive of old messages</a>. @@ -736,7 +734,7 @@ href="https://www.polyomino.org.uk/british-time/">History of legal time in Britain</a> discusses in detail the country with perhaps the best-documented history of clock adjustments. The National Physical Laboratory also maintains an <a -href="http://www.npl.co.uk/educate-explore/what-is-time/archive-of-summer-time-da…">Archive +href="http://www.npl.co.uk/educate-explore/what-is-time/archive-of-summer-time-da…">Archive of Summer time dates</a>.</dd> <dt>United States</dt> <dd>The Department of Transportation's <a @@ -751,7 +749,7 @@ Science of Timekeeping</a> is a thorough introduction to the theory and practice of precision timekeeping.</li> <li><a href="http://www.ntp.org"><abbr title="Network Time Protocol">NTP</abbr>: The Network -Time Protocol</a> +Time Protocol</a> (Internet <abbr>RFC</abbr> 5905) discusses how to synchronize clocks of Internet hosts.</li> <li>The <a -- 2.7.4

1 0

Set up correct name to Zone Europe/Kyiv
by Alexey Furashev Oct. 31, 2016

Oct. 31, 2016

Hello All, In source file https://github.com/eggert/tz/blob/master/europe please change city name to correspondent standards ISO 3166-2:UA and UNGEGN. We have to write bug reports to software developers, because time zone entry names are incorrect. Incorrect name of time zone entries can't be used for our practical needs. ------------- str: 3663 from 'Zone Europe/Kiev' to 'Zone Europe/Kyiv' # ISO city code is UA-30 (https://www.iso.org/obp/ui/#iso:code:3166:UA ) ------------- str: 3691 from 'Zone Europe/Zaporozhye' to 'Zone Europe/Zaporizhzhia' ------------- Rules transliteraion from Ukranian to Latin see on site http://zakon4.rada.gov.ua/laws/show/55-2010-%D0%BF On-line service transliteration: https://dmsu.gov.ua/transliteration.html Oleksii. Kyiv.

2 1