July 2016 - tz - lists.iana.org

why does mktime binary search?
by enh July 29, 2016

July 29, 2016

is there a more detailed explanation of why mktime does binary search? ** Adapted from code provided by Robert Elz, who writes: ** The "best" way to do mktime I think is based on an idea of Bob ** Kridle's (so its said...) from a long time ago. ** It does a binary search of the time_t space. Since time_t's are ** just 32 bits, its a max of 32 iterations (even at 64 bits it ** would still be very reasonable). this came up on Android because we had some code that did "errno = 0; mktime(...); if (errno == EOVERFLOW) ..." rather than checking the return value of mktime. this failed for us because the tzcode mktime sets errno even on non-failure. obviously i can fix this by saving errno around the call to mktime_tzname in mktime, but i'm curious to know why there's a binary search at all. i also notice that, of the BSDs, NetBSD seems to have fixed this locally, FreeBSD has an old enough copy of tzcode that it's not setting errno at all, and OpenBSD is in the same boat as Android. here's the NetBSD change, which is does the errno save-restore in time1 instead: revision 1.90 date: 2014-10-16 10:53:32 -0700; author: christos; state: Exp; lines: +24 -36; commitid: 4woGqYWkKe0i6sUx; - don't leak errno in mktime() - when we load a new timezone, don't change anything unless the load succeeded. http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libc/time/localtime.c.diff?r1=1…

4 3

Public Key Wanted
by Peter Remmers July 29, 2016

July 29, 2016

Hello, I've been trying to find the public key that was used to sign the tzdata and tzcode files on ftp.iana.org/tz. I found this: https://mm.icann.org/pipermail/tz/2014-June/020967.html which says the key ID is 62AA7E34, but it's not. gpg -vv tzdata-latest.tar.gz.asc says the files were signed using key ID 043DB63744AD418C (or short 44AD418C), but this key isn't to be found on any keyserver I tried. I kindly request a pointer to the public key that was used for the current files on the ftp server, so we can verify the signatures. Regards, Peter Remmers

3 2

Request regarding IANA update for Novosibirsk Time Zone
by Shruthi Venkataramanan -X (shruthve - WIPRO LIMITED at Cisco) July 28, 2016

July 28, 2016

Hi, Novosibirsk Oblast moved forward one hour from UTC+06:00 to UTC+07:00 (from Omsk to Krasnoyarsk time). This time zone change occurred on 24 July 2016. When can we expect the updated version of IANA Time Zone Data. Thanks & Regards, Shruthi.

3 2

Blog Post: On the Timing of Time Zone Changes
by Matt Johnson July 26, 2016

July 26, 2016

I've written a blog post describing the chaos that ensues when governments don't provide enough notice of their changes to time zones. http://codeofmatt.com/2016/04/23/on-the-timing-of-time-zone-changes/ <http://aka.ms/weboutlook> Enjoy! -Matt

11 15

ICANN contacts Egyptian government about recent last-minute clock change
by Paul Eggert July 24, 2016

July 24, 2016

Baher Esmat of ICANN contacted the Egyptian government asking it to give us more notice about clock changes next time. This found its way into the popular press earlier this month; here's the English-language version: Al-Youm A-M. ICANN thrown into confusion by cancelation of Daylight Saving Time. Egypt Independent 2016-07-08. http://www.egyptindependent.com/news/icann-thrown-confusion-cancelation-day…

7 8

Re: [tz] Joda-Time, Time4J, and Java SE 8
by Paul Eggert July 19, 2016

July 19, 2016

On 07/08/2016 06:23 AM, Meno Hochschild wrote: > it is not quite correct to say that Joda-Times "functionality is a > standard part of Java 8". It has rather inspired the development of > java.time-package in Java-8. Thanks for the correction. Sorry, I don't know Joda-Time vs Java SE 8 vs Time4J well. I'm trying to future-proof tz-link.htm. As I understand it from the Joda-Time web page, Joda-Time-using apps are expected to migrate to the Java SE 8 API, so future readers of tz-link.htm will mostly be using the Java API, with more-specialized uses (leap seconds? sorry, don't know the details) possibly using Time4J, and Joda-Time being a historical footnote. I installed the attached further patch into the experimental tz version on GitHub; I hope it addresses this point well enough. I'll CC: Stephen Colebourne to give him a heads-up, as I do want tz-link.htm to be accurate.

4 5

Positive leap second on 2016-12-31.
by Tim Parenti July 19, 2016

July 19, 2016

Per IERS Bulletin C52 (2016-07-06), a positive leap second will be observed on 2016-12-31. The attached patch updates leap-seconds.list from NIST, retrieved from <ftp://time.nist.gov/pub/leap-seconds.list>. -- Tim Parenti

2 1

Fwd: tzcode: system-dependent default time zone file
by Paul Eggert July 7, 2016

July 7, 2016

-------- Forwarded Message -------- Subject: tzcode: system-dependent default time zone file Date: Wed, 06 Jul 2016 21:11:19 -0400 From: Steve Summit <scs(a)eskimo.com> To: Paul Eggert <eggert(a)cs.ucla.edu> [Belated reply to an earlier thread. Feel free to post this to the tz list, or not, your choice. Other than Guy Harris, I don't know how interested the rest of the list is in these lower-level coding and build details.] Back in January, in the "tzcode test suite" thread, Paul and I had this exchange: >> I'm not sure what that warning about "no nontrivial tz offset tested" >> means, but I hope we can fix the testsuite to set TZ itself if that's >> what it needs to do. > > Setting TZ is what I needed to do, although I'm surprised that you > had the same problem, so this will bear further investigation. I believe the problem is simply some variation across systems in the location of the tz file that sets a machine's local time zone in the absence of a TZ environment variable. As compiled out of the box, tzcode expects to find this in TZDIR/localtime, that is, in /usr/share/zoneinfo/localtime. But on my Mac it's /etc/localtime, and I suspect it's probably there on Paul's Fedora machine, too. The fix is simple: I'm now setting TZDEFAULT = "/etc/localtime" in the Makefile, and then passing it down to the compilations: CC = $(cc) -DTZDIR=\"$(TZDIR)\" -DTZDEFAULT=\"$(TZDEFAULT)\" With these changes, I no longer need to explicitly set TZ to keep tzcode's copy of localtime happy. I was going to propose adding this comment to the Makefile in the tz distribution: # By default, the local time zone is taken from the file # "localtime" in TZDIR. Or you can set TZDEFAULT to something # else (for example, it's typically "/etc/localtime" for MacOS, # BSD, and some versions of Linux). But I believe TZDEFAULT in the same Makefile is also used when *installing* a set of zoneinfo files built from tzdata, and I'm uncertain of the repercussions for tzdata builds if I encourage people to tinker with TZDEFAULT to match their OS. This is probably a symptom of a deeper issue: if someone downloads and builds tzdata and/or tzcode, is it assumed that they'll be installing and referencing the zoneinfo files in the tzdata/tzcode default location, or in their OS's preferred location, or what? And the answer gets more complicated depending on whether people are actually using tzcode, or their OS's possibly different tz code -- glibc or whatever -- instead.

1 0

Egypt cancelled DST
by Mina Samuel July 5, 2016

July 5, 2016

Dears, Egyptian government took the decision to cancel the DST, Can you please help to provide the updated package as to be able to apply the new/cancelled rules. https://translate.google.com/translate?sl=ar&tl=en&js=y&prev=_t&hl=en&ie=UT… http://www.youm7.com/story/2016/7/4/%D8%A7%D9%84%D8%AD%D9%83%D9%88%D9%85%D8…

8 9

[tz-announce] 2016f release of tz code and data available
by Paul Eggert July 5, 2016

July 5, 2016

The 2016f 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: Changes affecting future time stamps The Egyptian government changed its mind on short notice, and Africa/Cairo will not introduce DST starting 2016-07-07 after all. (Thanks to Mina Samuel.) Asia/Novosibirsk switches from +06 to +07 on 2016-07-24 at 02:00. (Thanks to Stepan Golosunov.) Changes to past and future time stamps Asia/Novokuznetsk and Asia/Novosibirsk now use numeric time zone abbreviations instead of invented ones. Changes affecting past time stamps Europe/Minsk's 1992-03-29 spring-forward transition was at 02:00 not 00:00. (Thanks to Stepan Golosunov.) Here are links to the release files: ftp://ftp.iana.org/tz/releases/tzcode2016f.tar.gz ftp://ftp.iana.org/tz/releases/tzdata2016f.tar.gz The files are also available via HTTP as follows: http://www.iana.org/time-zones/repository/releases/tzcode2016f.tar.gz http://www.iana.org/time-zones/repository/releases/tzdata2016f.tar.gz 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 ftp://ftp.iana.org/tz/tzcode-latest.tar.gz ftp://ftp.iana.org/tz/tzdata-latest.tar.gz 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 baba36e3b5ec93c462c27a28a697119df9e94783 dated 2016-07-05 16:26:51 +0200 and tagged '2016f' in the experimental github repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 97d084f4b0a688fef097dca256083ca9948393848d77c8ee637bdd26f859150cce7d2b26fc1165a3b44b28cc1c9075e10192332261ed68990b4b21a85438b023 tzcode2016f.tar.gz 0472f9516b6c3d83c0a5d0953a5535f4c48d9b9171e125f528188dac512f3556bc1805b7029c4f467a122cbce1beb4e804dd4ae63b259952de3bb217f8e8941d tzdata2016f.tar.gz Here are the GPG checksums for the release files (note I am using a new GPG key): -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAABAgAGBQJXe8puAAoJEAQ9tjdErUGMYo8IAKif54YlyHHNdLSWzAseY1jf 80hiZG4bIDVNXD5qNAN5sIf7FexBNS9h/KB3H2xJ+47UZHfBqEIRSdNM3+1cFhPg EZShIc8PKPkjS3/pxdR+7Sz/JWGDq1FyNCnBNoyRhKAcDWH3rsa2L7Q3hvkZ7Xcg 8DlhCcixLSX/rhJEs7k61FcGXivUkrht8trrvoTTBkoFpGUqt+x+cNan0z0qyiqF PLQq7YJAjstGRsli97+P72WdJDRY6JL716slICKO5IYDki9xmpcBuj4l0bAxR+6c PiZWlePe1TTyT0+shefy0eZmq1F7seTmkpAL7bhPR3E4ATYZfJfsMm6b/5seBFs= =62wb -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAABAgAGBQJXe8p1AAoJEAQ9tjdErUGMmc0H/i837mGKBIJLmS1xtr64uaT+ LLLvI1gFTGJsqTaCya7aAVFlN/STM07otvYdkBDwQ6uIgjm8qAL33lGdi9IpTPp2 YOj03QkWpyPRFtM1A9EcsVkKOfezGSiY7WQiOEk7R05lH1SRBlZ+eXVQl9fhadrj qCRkcCasVIDQWMKCOhSch1HyUuR+Z1Ujomi7Z4d0AyQbMKhB1yGxYKCVGzN8KaOK AFr0Dd44p72dqgPdC/V7G0xjTNOpuM1zt8SdJuOE2EASRraIvnnQctmKlbYI8l8L ANvy9xl+p8VkuZi7yuSoqVSLYTQDE8pAMsfg0DZpAbnjV1G07FxekBMdNzdr5/E= =7jGR -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0