- tz - lists.iana.org

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