- tz - lists.iana.org

[PATCH] Shorten an overlong abbrevation in 'backzone'
by Paul Eggert May 26, 2017

May 26, 2017

* backzone (Africa/Luanda): Use 'LMT' for what was apparently Luanda Mean Time. '+005204' is so long that it now provokes a zic warning. --- backzone | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/backzone b/backzone index 9ce7831..a630129 100644 --- a/backzone +++ b/backzone @@ -181,7 +181,7 @@ Zone Africa/Lome 0:04:52 - LMT 1893 # with the date that it took effect, namely 1912-01-01. # Zone Africa/Luanda 0:52:56 - LMT 1892 - 0:52:04 - +005204 1912 Jan 1 + 0:52:04 - LMT 1912 Jan 1 # Luanda Mean Time? 1:00 - WAT # Democratic Republic of the Congo (east) -- 2.9.4

1 0

U.S. DST causes an estimated 30 traffic-accident deaths/year
by Paul Eggert May 25, 2017

May 25, 2017

Austin Smith of Miami University analyzed data from the U.S. Fatality Analysis Reporting System both before and after the 2007 daylight-saving rule change, and found that the spring-forward transition increased fatal crash risk by 5% to 6.5%, with four statistical tests suggesting that the increase is explained by sleep deprivation. Smith concludes, "Back-of-the-envelope calculations suggest that the spring transition into DST caused over 30 deaths annually at a social cost of $275 million." I assume this estimate is for just the U.S. Smith AC. Spring forward at your own risk: daylight saving time and fatal vehicle crashes. Am Econ J: Appl Econ. 2016;8(2):65-91. http://dx.doi.org/10.1257/app.20140100

1 0

[PATCH] Clarify LICENSE file
by Paul Eggert May 25, 2017

May 25, 2017

* LICENSE: Reword LICENSE so that it makes sense when only data files are distributed. --- LICENSE | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/LICENSE b/LICENSE index 148eb23..8ba4399 100644 --- a/LICENSE +++ b/LICENSE @@ -1,4 +1,5 @@ -With a few exceptions, all files in the tz code and data (including -this one) are in the public domain. The exceptions are date.c, -newstrftime.3, and strftime.c, which contain material derived from BSD -and which use the BSD 3-clause license. +Unless specified below, all files in the tz code and data (including +this LICENSE file) are in the public domain. + +If the files date.c, newstrftime.3, and strftime.c are present, they +contain material derived from BSD and use the BSD 3-clause license. -- 2.9.4

1 0

input needed on creation of a new sub-package for raw zone data
by Patsy Franklin May 24, 2017

May 24, 2017

Hi, I'd appreciate community input on this plan. Ideally if others decide to also ship a similar subpackage we can use a common naming convention and install directory. We are planning to ship a new subpackage for users who want to have access to the raw zone data files e.g. leapseconds, and in a pre-determined install location e.g. /usr/share/zoneinfo/zonedata/. The raw zone data is useful for users designing their own interfaces on top of this data. The broadest flexibility is offered by the raw zone data, and while the compiled binary data is versioned and more stable, some users have expressed a request for the raw zone data. The understanding is that the raw zone data format may change. In summary: Our current plan is to use -zonedata in naming the subpackage, For example, tzdata-zonedata-2017b-1.el7. We plan to install the files in this subpackage under /usr/share/zoneinfo/zonedata/. Just as an example we would ship the following files: LICENSE version africa antarctica asia australasia europe northamerica southamerica pacificnew etcetera backward systemv factory backzone iso3166.tab leapseconds leap-seconds.list zone1970.tab zone.tab Thank you! Patsy

5 11

[PROPOSED 1/5] New Makefile macro BACKWARD
by Paul Eggert May 24, 2017

May 24, 2017

* NEWS: Document this. * Makefile (BACKWARD): New macro. (YDATA, INSTALLARGS): Use it. --- Makefile | 10 +++++++++- NEWS | 4 ++++ 2 files changed, 13 insertions(+), 1 deletion(-) diff --git a/Makefile b/Makefile index c62d46f..6373920 100644 --- a/Makefile +++ b/Makefile @@ -92,6 +92,13 @@ LIBDIR= $(TOPDIR)/lib REDO= posix_right +# For backward-compatibility links for old zone names, use +# BACKWARD= backward pacificnew +# To omit these links, use +# BACKWARD= + +BACKWARD= backward pacificnew + # If you want out-of-scope and often-wrong data from the file 'backzone', use # PACKRATDATA= backzone # To omit this data, use @@ -384,7 +391,7 @@ WEB_PAGES= tz-art.htm tz-how-to.html tz-link.htm DOCS= $(MANS) date.1 $(MANTXTS) $(WEB_PAGES) PRIMARY_YDATA= africa antarctica asia australasia \ europe northamerica southamerica -YDATA= $(PRIMARY_YDATA) pacificnew etcetera backward +YDATA= $(PRIMARY_YDATA) etcetera $(BACKWARD) NDATA= systemv factory TDATA= $(YDATA) $(NDATA) ZONETABLES= zone1970.tab zone.tab @@ -482,6 +489,7 @@ leapseconds: $(LEAP_DEPS) # Arguments to pass to submakes of install_data. # They can be overridden by later submake arguments. INSTALLARGS = \ + BACKWARD=$(BACKWARD) \ DESTDIR=$(DESTDIR) \ LEAPSECONDS='$(LEAPSECONDS)' \ PACKRATDATA='$(PACKRATDATA)' \ diff --git a/NEWS b/NEWS index 4e8091b..dcd49eb 100644 --- a/NEWS +++ b/NEWS @@ -20,6 +20,10 @@ Unreleased, experimental changes in civil timekeeping. (Thanks to Robert Elz and Bradley White for noticing glitches in the code that uncovered this problem.) + 'make BACKWARD=' now suppresses backward-compatibility names + like 'US/Pacific' that are defined in the 'backward' and + 'pacificnew' files. + Several minor changes have been made to the code to make it a bit easier to port to MS-Windows. (Thanks to Kees Dekker for reporting the problems.) -- 2.9.4

1 4

Fwd: input needed on creation of a new sub-package for raw zone data
by Patsy Franklin May 23, 2017

May 23, 2017

Sorry, should have replied to all on this one. ---------- Forwarded message ---------- From: Patsy Franklin <pfrankli(a)redhat.com> Date: Tue, May 23, 2017 at 9:26 AM Subject: Re: [tz] input needed on creation of a new sub-package for raw zone data To: Brian.Inglis(a)systematicsw.ab.ca Hi Brian, Thanks for the feedback! On Mon, May 22, 2017 at 1:54 PM, Brian Inglis <Brian.Inglis(a)systematicsw.ab. ca> wrote: > On 2017-05-22 07:03, Patsy Franklin wrote: > > I'd appreciate community input on this plan. Ideally if others decide > > to also ship a similar subpackage we can use a common naming > > convention and install directory. > > > > We are planning to ship a new subpackage for users who want to have > > access to the raw zone data files e.g. leapseconds, and in a > > pre-determined install location e.g. /usr/share/zoneinfo/zonedata/. > > How about using /usr/share/tzdata{,-src}/ maybe with subdirectories > tzdata-2017b, etc. > > We really want to avoid using src to prevent any confusion between the full src rpm that we ship and this subset of the zone data. > > The raw zone data is useful for users designing their own interfaces > > on top of this data. The broadest flexibility is offered by the raw > > zone data, and while the compiled binary data is versioned and more > > stable, some users have expressed a request for the raw zone data. > > The understanding is that the raw zone data format may change. > > > > In summary: > > Our current plan is to use -zonedata in naming the subpackage, For > > example, tzdata-zonedata-2017b-1.el7. > > How about tzdata-src-2017b...? > > We already provide tzdata-2017b-1.el7.src.rpm which contains the full set of sources. The location of these sources is defined by the installer. > We plan to install the files in this subpackage under > > /usr/share/zoneinfo/zonedata/. > > Adding zonedata does not add any useful information about the contents > and storing under /usr/share/zoneinfo/ could be confusing as there are > already subdirectories posix and right holding copies of standard and > leapsecond compensated binary data files, so TZ=posix/... and > TZ=right/... are valid zones, and users may expect something similar to > happen using TZ=zonedata/... which would be unfortunate. > > That's a good point. I hadn't considered that case. We chose zonedata to clarify that it was only the zone data - not zic, zdump, binaries, etc. It was requested that we provide this subset of files in a consistent location at install time which is why we grouped it under the zoneinfo directory. Is there a more appropriate place to install it? Do you have any other suggestions for a name since I think src is ambiguous for our purposes? > Just as an example we would ship the following files: > > LICENSE > > version > > africa > > antarctica > > asia > > australasia > > europe > > northamerica > > southamerica > > pacificnew > > etcetera > > backward > > systemv > > factory > > backzone > > iso3166.tab > > leapseconds > > leap-seconds.list > > zone1970.tab > > zone.tab > > README, CONTRIBUTING, NEWS, and Theory should be included, also > tz-how-to.html which documents how to define and use the sources. > leap-seconds.list should be a (symbolic?) link to the canonical file > version leap-seconds.<timestamp> e.g. leap-seconds.3692908800. > We ship README and Theory with the base package. CONTRIBUTING, NEWS and tz-how-to.html is shipped with our src package. Do we still need to duplicate these in the optional subpackages? BTW, I forgot to mention that our spec file will not allow the new subpackage to be installed without the corresponding version of the base package. The base package does not require the optional new subpackage but will check to insure that it is in sync if it is installed. Do we still need to version the leap-seconds file if it is tied to a specific tzdata version? Thanks! Patsy > > -- > Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada >

2 1

Looking for a way to cut down binary zoneinfo size. Does anyone have the way to?
by Viktor Sergiienko May 19, 2017

May 19, 2017

Hello, I'm developing for a pretty small-sized embedded system, and 2.9M of binaries is a bit too much for us. The system never uses a date before 2007. I estimate I can slim it down too 500K by cutting down the old data. 1. I made a script to cut down the source data: all the rules and all the zonelines before 2001. Compiling this data, I get a lot of errors like: > "northamerica", line 2537: %s in ruleless zone > "northamerica", line 2618: unruly zone because some zones are left without rules, but with %s format in them. 2. I tried to modify zic itself, but apparently understanding it will take me days. Just setting min_year to 2001 results in bunch of > can't determine time zone abbreviation to use just after until time Does anyone have a ready solution? Thanks!

7 11

[PROPOSED 1/2] Rename ‘lint’ to ‘GCC_LINT’
by Paul Eggert May 18, 2017

May 18, 2017

* Makefile (GCC_DEBUG_FLAGS): * private.h (INITIALIZE): Rename ‘lint’ to ‘GCC_LINT’, as the macro is intended for GCC, not for traditional ‘lint’. --- Makefile | 2 +- private.h | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Makefile b/Makefile index e7c6ac0..bcfdcb2 100644 --- a/Makefile +++ b/Makefile @@ -159,7 +159,7 @@ LDLIBS= # (or some other number) to set the maximum time zone abbreviation length # that zic will accept without a warning (the default is 6) # $(GCC_DEBUG_FLAGS) if you are using recent GCC and want lots of checking -GCC_DEBUG_FLAGS = -Dlint -g3 -O3 -fno-common -fstrict-aliasing \ +GCC_DEBUG_FLAGS = -DGCC_LINT -g3 -O3 -fno-common -fstrict-aliasing \ -Wall -Wextra \ -Wbad-function-cast -Wcast-align -Wdate-time \ -Wdeclaration-after-statement \ diff --git a/private.h b/private.h index e9eb211..6886185 100644 --- a/private.h +++ b/private.h @@ -566,7 +566,7 @@ static time_t const time_t_max = MAXVAL(time_t, TYPE_BIT(time_t)); ** INITIALIZE(x) */ -#ifdef lint +#ifdef GCC_LINT # define INITIALIZE(x) ((x) = 0) #else # define INITIALIZE(x) -- 2.9.4

1 1

Morocco changes May 27th 2017 instead of May 21th
by Info - avisched.com May 17, 2017

May 17, 2017

Morocco is about to switch on May 27th back to UTC from +1. The current release doesn't reflect that (May 21st). Is there any update planned before the actual transition? Many thanks! Martin

5 5

Asia/Harbin, Asia/Chongqing and Asia/Kashgar
by Phake Nick May 13, 2017

May 13, 2017

iirc, according to past conversation on the mailing list, the reason why these timezones that are not in use for many years already still exists in tz database is because of legacy reason, however given that Asia/Ishigaki were deleted from this database in 1999 when it's found to be not in use, is there any reason preventing the same to be done to Asia/Harbin, Asia/Chongqing, and Asia/Kashgar?

2 1