June 2018 - tz - lists.iana.org

Re: [tz] [PROPOSED] Use "PST/PDT" for Philippine time
by Paul Eggert June 25, 2018

June 25, 2018

Michael H Deckers wrote: > Fine if this were a generally applied guideline -- but it is not, > see eg America/Adak, Indonesia, and many others. When is this guideline > applied, and when not? The guideline is supposed to be applied reasonably consistently for clear-cut cases such as the Philippines. Alaska and Indonesia are more complicated, since they are not merely a question of what's the name of a time zone; they are also a question of time zone boundaries moving, and where it's not so clear what is being named. For example, a historian today would be unlikely to write "Sitka observed Alaska Standard Time in 1984" because in 1984 the Alaska time zone boundaries were quite different and Sitka was then in the geographically small part of Alaska that was in the same time zone as the Yukon. Unfortunately I don't see a good solution for these more-complicated cases, and am reluctant to change the data if it's likely this would introduce as much or more confusion than it would alleviate. > And all that does not justify the resurrection of an invented abbreviation. First, for the Phillippines it's no longer an abbreviation that exists only because we invented it. It's taken on a life of its own in reliable sources and in national law. And second, I doubt whether these sources got "PST" from tzdb, since tzdb has been using "PHST" for over two decades and used "PST" only briefly before that. Most likely it was independent reinvention.

3 2

Re: [tz] [IANA #985615] Sudan Time Zone change
by ahmed.atyya＠ntc.gov.sd June 25, 2018

June 25, 2018

Dear Sir/ Madam we would like to inform you that the Republic of Sudan is going to change the time zone from (GMT + 3:00) to (GMT+ 2:00) starting from Wednesday 1 November 2017. this is for your information and action if required. Best Regards Dear Mr. Paul We would like to inform you as TZ coordinator that the Republic of Sudan is planning to change its time zone from GMT+ 3:00 to GMT +2:00 ( The original time zone ) starting from 1 November 2017 Please if you can update time zone data base Or you you can tell us what action is needed from Sudan government Best Regards Ahmed Atyya Head of Numbering Section National Telecomm. Corporation – Sudan Phone: +249123499988 Email: ahmed.atyya@ ----- Original Message ----- From: Sabrina Tanamal via RT <iana-questions(a)iana.org> To: ahmed atyya <ahmed.atyya(a)ntc.gov.sd> Sent: Tue, 17 Oct 2017 01:33:06 +0300 (EAT) Subject: [IANA #985615] Sudan Time Zone change Dear Ahmed, Thank you for contacting us. We host the Time Zone Database, but updates are made by the Time Zone Coordinator in consultation with the Time Zone mailing list, in accordance with RFC 6557. Questions about the contents of the database should be sent to the mailing list. For mailing list archives and subscription information, please see http://www.iana.org/time-zones Best regards, Sabrina Tanamal IANA Services Specialist On Mon Oct 16 09:55:06 2017, ahmed.atyya(a)ntc.gov.sd wrote: > Dear Sir/ Madam > > > > > > we would like to inform you that the Republic of Sudan is going to > change the time zone from (GMT + 3:00) to (GMT+ 2:00) starting from > Wednesday 1 November 2017. > > > this is for your information and action if required. > > > > > > Best Regards > > > > > > Ahmed Atyya > > > Head of Numbering Section > > National Telecomm. Corporation – Sudan > > Phone: +249123499988 > > Email: ahmed.atyya(a)ntc.gov.sd

6 19

Re: [tz] [PROPOSED] Use "PST/PDT" for Philippine time
by Paul Eggert June 24, 2018

June 24, 2018

Michael H Deckers wrote: > My second point was about the abbreviation "PDT", as proposed > for Manila summer time (which you have called "invented"), > not the abbreviation "PST" (which you have not called > "invented" in your proposal). Ah, sorry, I misunderstood. With "PDT" I was attempting to follow this guideline in theory.html: > Use a consistent style in a tz region's history. > For example, if history tends to use numeric > abbreviations and a particular entry could go either way, use a > numeric abbreviation. Since most Philippine history used an alphabetic abbreviation, I thought it better to do so with daylight-saving time too. This is consistent with Hong Kong, Taiwan and Korea, all of which have "JST" for time during Japanese occupation because they use alphabetic abbreviations now, and it is in contrast to other locations that use "+09" for timestamps under Japanese occupation. We have competing guidelines here: "be consistent" and "don't invent abbreviations", and it's a judgment call as to which is more important. PS. Many of those "+09"s are sheer guesswork by Shanks, but that's a different story....

1 0

Philippine Standard Time
by Paul Goyette June 23, 2018

June 23, 2018

In the Philippines, there is a national law, Republic Act No. 10535 which declares the official time here as "Philippine Standard Time". The act [1] even specifies use of PST as the abbreviation, although the FAQ provided by PAGASA [2] uses the "acronym PhST to distinguish it from the Pacific Standard Time (PST)." (Interestingly, the act does nothing to define the actual value of Philippine Standard Time; there is no UTC offset or other reference. It simply declares what the time is called, and instructs government agencies to coordinate with PAGASA for synchronization. :) There are references to "Section 6 of Batas Pambansa Bilang 8" [3] (which directs the adoption of the Metric System), but Section 6 merely delegates the task of establishing the definition of "second" to PAGASA. I've been unable so far to find any specific implementing regulation that establishes an official 8-hour offset from GMT.) Not long ago, the TZ database clean-up of "invented" abbreviations removed the PST abbreviation for Asia/Manila, leaving us with no abbreviation. Based on the existence of national law declaring Philippine Standard Time, and formally establishing the abbreviation/acronym, could we please get "PST" (or, if you prefer, "PhST") re-included into the next update of the TZDB? Thanks! References: [1] http://www.officialgazette.gov.ph/2013/05/15/republic-act-no-10535/ [2] https://www1.pagasa.dost.gov.ph/index.php/astronomy/philippine-standard-tim… [3] http://www.chanrobles.com/bataspambansabilang8.htm +------------------+--------------------------+----------------------------+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | paul at whooppee dot com | | Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd dot org | +------------------+--------------------------+----------------------------+

6 8

US daylight saving proposals in Texas, California, and Louisiana
by Paul Eggert June 19, 2018

June 19, 2018

This week the Republican Party of Texas is writing its official platform, which contains new planks that call for "abolishing daylight saving time and Texas Child Protective Services". (This quote is from McGaughy's report cited below.) The California State Senate approved a proposal Thursday to move California toward Mountain Standard Time all year (or permanent PDT, if you prefer). The measure would require voter approval in November, plus a second bill and federal approval. The basic idea is similar to the proposal in Florida that Arthur noted in March. Last month the Louisiana legislature overwhelmingly approved a resolution to study a proposal that presumably would also be similar to Florida's, in that Louisiana would move to Eastern Standard Time all year (or permanent CDT, if you prefer). Sources: Bacon-Blood L. Should Louisiana use Daylight Saving Time? State task force will evaluate the options. Times-Picayune. 2018-05-24. https://www.nola.com/politics/index.ssf/2018/05/la_task_force_will_study_me… Luna T. End of daylight saving time inches closer in California. Sacramento Bee. 2018-06-14. https://www.sacbee.com/news/politics-government/capitol-alert/article213187… McGaughy L. New Texas GOP platform calls for abolishing daylight saving, protecting Confederate monuments. Dallas Morning News. 2018-06-18. https://www.dallasnews.com/news/texas-politics/2018/06/16/vote-count-underw…

1 0

[PROPOSED] Merge some changes from man-pages project
by Paul Eggert June 19, 2018

June 19, 2018

Make some minor formatting changes to be more like man-pages. * tzfile.5: Break a line the same place that man-pages does. * zdump.8, zic.8: Use bold, not italics, for command and function names. Do not capitalize command names. Add a section header OPTIONS. Document --help. Fix some problems with fonts. Don’t quote "SEE ALSO", and don’t mention newctime(3). Put FILES before NOTES, and format a la man-pages. * zic.8: Also, do some fixes of our own, noticed while merging the above. Use real life US Rule, not an invented one. Write “UTOFF”, not “GMTOFF” (man-pages used “UTCOFF” but it’s not necessarily UTC either). Quote more carefully. --- tzfile.5 | 3 +- zdump.8 | 22 ++++++++------ zic.8 | 88 ++++++++++++++++++++++++++++++++------------------------ 3 files changed, 66 insertions(+), 47 deletions(-) diff --git a/tzfile.5 b/tzfile.5 index 13213d2..2e6c3aa 100644 --- a/tzfile.5 +++ b/tzfile.5 @@ -181,7 +181,8 @@ use two minor extensions to the POSIX TZ format, as described in .BR newtzset (3). First, the hours part of its transition times may be signed and range from \*-167 through 167 instead of the POSIX-required unsigned values -from 0 through 24. Second, DST is in effect all year if it starts +from 0 through 24. +Second, DST is in effect all year if it starts January 1 at 00:00 and ends December 31 at 24:00 plus the difference between daylight saving and standard time. .PP diff --git a/zdump.8 b/zdump.8 index 833dd54..92e9e62 100644 --- a/zdump.8 +++ b/zdump.8 @@ -18,16 +18,19 @@ zdump \- time zone dumper .. .ie \n(.g .ds - \f(CW-\fP .el ds - \- -.I Zdump -prints the current time in each +The +.B zdump +program prints the current time in each .I zonename named on the command line. -.PP -These options are available: +.SH OPTIONS .TP -.BI "\*-\*-version" +.B \*-\*-version Output version information and exit. .TP +.B \*-\*-help +Output short usage message and exit. +.TP .B \*-i .I "(This option is experimental: its behavior may change in future versions.)" Output a description of time intervals. For each @@ -68,7 +71,7 @@ except omit the times relative to the extreme time values. This generates output that is easier to compare to that of implementations with different time representations. .TP -.BI "\*-c " [loyear,]hiyear +.BI "\*-c " \fR[\fIloyear , \fR]\fIhiyear Cut off interval output at the given year(s). Cutoff times are computed using the proleptic Gregorian calendar with year 0 and with Universal Time (UT) ignoring leap seconds. @@ -80,7 +83,7 @@ of 1970 includes the transition. The default cutoff is .BR \*-500,2500 . .TP -.BI "\*-t " [lotime,]hitime +.BI "\*-t " \fR[\fIlotime , \fR]\fIhitime Cut off interval output at the given time(s), given in decimal seconds since 1970-01-01 00:00:00 Coordinated Universal Time (UTC). @@ -220,7 +223,8 @@ for newer and .q "UT" for older timestamps, partly because the exact date of the introduction of UTC is problematic. -.SH "SEE ALSO" -newctime(3), tzfile(5), zic(8) +.SH SEE ALSO +.BR tzfile (5), +.BR zic (8) .\" This file is in the public domain, so clarified as of .\" 2009-05-17 by Arthur David Olson. diff --git a/zic.8 b/zic.8 index 00d4267..3e33618 100644 --- a/zic.8 +++ b/zic.8 @@ -28,27 +28,30 @@ zic \- time zone compiler . ds : . ds - \- .\} -.I Zic -reads text from the file(s) named on the command line +The +.B zic +program reads text from the file(s) named on the command line and creates the time conversion information files specified in this input. If a .I filename is .q "\*-" , -the standard input is read. -.PP -These options are available: +standard input is read. +.SH OPTIONS .TP -.BI "\*-\*-version" +.B "\*-\*-version" Output version information and exit. .TP +.B \*-\*-help +Output short usage message and exit. +.TP .BI "\*-d " directory Create time conversion information files in the named directory rather than in the standard directory named below. .TP .BI "\*-l " timezone Use the given time zone as local time. -.I Zic +.B zic will act as if the input contained a link line of the form .sp .ti +.5i @@ -57,7 +60,7 @@ Link \fItimezone\fP localtime .BI "\*-p " timezone Use the given time zone's rules when handling POSIX-format time zone environment variables. -.I Zic +.B zic will act as if the input contained a link line of the form .sp .ti +.5i @@ -80,17 +83,17 @@ The input specifies a link to a link. .PP A year that appears in a data file is outside the range of years representable by -.IR time (2) +.BR time (2) values. .PP A time of 24:00 or more appears in the input. Pre-1998 versions of -.I zic +.B zic prohibit 24:00, and pre-2007 versions prohibit times greater than 24:00. .PP A rule goes past the start or end of the month. Pre-2004 versions of -.I zic +.B zic prohibit this. .PP The output file does not contain all the information about the @@ -102,7 +105,7 @@ represented. .PP The output contains data that may not be handled properly by client code designed for older -.I zic +.B zic output formats. These compatibility issues affect only timestamps before 1970 or after the start of 2038. .PP @@ -148,7 +151,7 @@ to the end of the line the sharp character appears on. White space characters and sharp characters may be enclosed in double quotes (") if they're to be used as part of a field. Any line that is blank (after comment stripping) is ignored. -Non-blank lines are expected to be of one of three types: +Nonblank lines are expected to be of one of three types: rule lines, zone lines, and link lines. .PP Names must be in English and are case insensitive. @@ -165,14 +168,14 @@ abbreviation must be unambiguous in context. A rule line has the form .nf .ti +.5i -.ta \w'Rule\0\0'u +\w'NAME\0\0'u +\w'FROM\0\0'u +\w'1973\0\0'u +\w'TYPE\0\0'u +\w'Apr\0\0'u +\w'lastSun\0\0'u +\w'2:00s\0\0'u +\w'1:00d\0\0'u +.ta \w'Rule\0\0'u +\w'NAME\0\0'u +\w'FROM\0\0'u +\w'1973\0\0'u +\w'TYPE\0\0'u +\w'Apr\0\0'u +\w'lastSun\0\0'u +\w'2:00w\0\0'u +\w'1:00d\0\0'u .sp Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S .sp For example: .ti +.5i .sp -Rule US 1967 1973 \*- Apr lastSun 2:00s 1:00d D +Rule US 1967 1973 \*- Apr lastSun 2:00w 1:00d D .sp .fi The fields that make up a rule line are: @@ -220,7 +223,7 @@ field. should be .q \*- and is present for compatibility with older versions of -.I zic +.B zic in which it could contain year types. .TP .B IN @@ -274,7 +277,7 @@ Recognized forms include: where hour 0 is midnight at the start of the day, and hour 24 is midnight at the end of the day. Although -.I zic +.B zic rounds times to the nearest integer second (breaking ties to the even integer), the fractions may be useful to other applications requiring greater precision. @@ -321,7 +324,7 @@ Negative offsets are allowed; in Ireland, for example, daylight saving time is observed in winter and has a negative offset relative to Irish Standard Time. The offset is merely added to standard time; for example, -.I zic +.B zic does not distinguish a 10:30 standard time plus an 0:30 .B SAVE from a 10:00 standard time plus a 1:00 @@ -347,8 +350,8 @@ A zone line has the form .sp .nf .ti +.5i -.ta \w'Zone\0\0'u +\w'Asia/Amman\0\0'u +\w'GMTOFF\0\0'u +\w'Jordan\0\0'u +\w'FORMAT\0\0'u -Zone NAME GMTOFF RULES FORMAT [UNTIL] +.ta \w'Zone\0\0'u +\w'Asia/Amman\0\0'u +\w'UTOFF\0\0'u +\w'Jordan\0\0'u +\w'FORMAT\0\0'u +Zone NAME UTOFF RULES FORMAT [UNTIL] .sp For example: .sp @@ -357,7 +360,7 @@ Zone Asia/Amman 2:00 Jordan EE%sT 2017 Oct 27 01:00 .sp .fi The fields that make up a zone line are: -.TP "\w'GMTOFF'u" +.TP "\w'UTOFF'u" .B NAME The name of the time zone. This is the name used in creating the time conversion information file for the @@ -369,7 +372,7 @@ or a file name component is a maximal substring that does not contain .q "/" . .TP -.B GMTOFF +.B UTOFF The amount of time to add to UT to get standard time in this zone. This field has the same format as the .B AT @@ -413,7 +416,10 @@ Alternatively, a slash (/) separates standard and daylight abbreviations. To conform to POSIX, a time zone abbreviation should contain only -alphanumeric ASCII characters, "+" and "\*-". +alphanumeric ASCII characters, +.q "+" +and +.q "\*-". .TP .B UNTIL The time at which the UT offset or the rule(s) change for a location. @@ -518,7 +524,7 @@ if the leap second time given by the other fields should be interpreted as local wall clock time. .SH "EXTENDED EXAMPLE" Here is an extended example of -.I zic +.B zic input, intended to illustrate many of its features. In this example, the EU rules are for the European Union and for its predecessor organization, the European Communities. @@ -539,8 +545,8 @@ Rule EU 1979 1995 \*- Sep lastSun 1:00u 0 \*- Rule EU 1981 max \*- Mar lastSun 1:00u 1:00 S Rule EU 1996 max \*- Oct lastSun 1:00u 0 \*- .sp -.ta \w'# Zone\0\0'u +\w'Europe/Zurich\0\0'u +\w'GMTOFF\0\0'u +\w'0:34:08\0\0'u +\w'FORMAT\0\0'u -# Zone NAME GMTOFF RULES FORMAT [UNTIL] +.ta \w'# Zone\0\0'u +\w'Europe/Zurich\0\0'u +\w'0:34:08\0\0'u +\w'RULES\0\0'u +\w'FORMAT\0\0'u +# Zone NAME UTOFF RULES FORMAT [UNTIL] Zone Europe/Zurich 0:34:08 \*- LMT 1853 Jul 16 0:29:46 \*- BMT 1894 Jun 1:00 Swiss CE%sT 1981 @@ -556,8 +562,9 @@ seconds east of UT until 1853-07-16 at 00:00, when the legal offset was changed to 7\(de\|26\(fm\|22.50\(sd; although this works out to 0:29:45.50, the input format cannot represent fractional seconds so it is rounded here. After 1894-06-01 at 00:00 the UT offset became one hour -and Swiss daylight saving rules (defined with lines beginning with "Rule -Swiss") apply. From 1981 to the present, EU daylight saving rules have +and Swiss daylight saving rules (defined with lines beginning with +.q "Rule Swiss") +apply. From 1981 to the present, EU daylight saving rules have applied, and the UTC offset has remained at one hour. .PP In 1941 and 1942, daylight saving time applied from the first Monday @@ -568,11 +575,21 @@ saving has begun on the last Sunday in March at 01:00 UTC. Until 1995 it ended the last Sunday in September at 01:00 UTC, but this changed to the last Sunday in October starting in 1996. .PP -For purposes of -display, "LMT" and "BMT" were initially used, respectively. Since +For purposes of display, +.q "LMT" +and +.q "BMT" +were initially used, respectively. Since Swiss rules and later EU rules were applied, the display name for the time zone has been CET for standard time and CEST for daylight saving time. +.SH FILES +.TP +.I /etc/localtime +Default local time zone file. +.TP +.I /usr/share/zoneinfo +Default time zone information directory. .SH NOTES For areas with more than two types of local time, you may need to use local standard time in the @@ -585,17 +602,14 @@ for a particular zone, a clock advance caused by the start of daylight saving coincides with and is equal to a clock retreat caused by a change in UT offset, -.IR zic +.B zic produces a single transition to daylight saving at the new UT offset (without any change in wall clock time). To get separate transitions use multiple zone continuation lines specifying transition instants using universal time. -.SH FILES -.ta \w'/usr/share/zoneinfo\0\0'u -/etc/localtime default local time zone file -/usr/share/zoneinfo default time zone information directory -.SH "SEE ALSO" -newctime(3), tzfile(5), zdump(8) +.SH SEE ALSO +.BR tzfile (5), +.BR zdump (8) .\" This file is in the public domain, so clarified as of .\" 2009-05-17 by Arthur David Olson. -- 2.17.1

1 0

[PROPOSED] Remove Big Bang hack
by Paul Eggert June 13, 2018

June 13, 2018

The Big Bang hack introduced in 2013d should no longer be needed, now that type 0 is the default type and types are reordered to make this happen. I.e., since we now have a better fix for the Macquarie Island problem reported by Alan Gutierrez in <https://mm.icann.org/pipermail/tz/2013-May/019368.html>, we can revert much of the 2013-05-23 12:19:13 -0700 change “Rework to avoid problem with Australia/Macquarie on 32-bit hosts” and the 2014-05-01 16:32:16 -0700 followup change “zic: improve handling of low-valued time stamps” which caused zic to insert a dummy transition. As a result, zic now generates TZif files that are typically a few bytes shorter, as they were in 2013c and earlier. * Makefile, zic.8: Remove mention of Big Bang. * NEWS: Mention. * zic.c (BIG_BANG, WORK_AROUND_CLIENT_OVERFLOW_BUGS, early_time): Remove. All uses removed. (writezone): New arg DEFAULTTYPE. All callers changed. Simplify by not inserting a dummy transition before the Big Bang. (outzone): Compute default type for use by writezone. (addtt): Don’t second-guess type 0. --- Makefile | 1 - NEWS | 6 +++ zic.8 | 6 --- zic.c | 151 ++++++++++++++++----------------------------------------------- 4 files changed, 44 insertions(+), 120 deletions(-) diff --git a/Makefile b/Makefile index 3705fc0..2289dff 100644 --- a/Makefile +++ b/Makefile @@ -173,7 +173,6 @@ LDLIBS= # Add the following to the end of the "CFLAGS=" line as needed to override # defaults specified in the source code. "-DFOO" is equivalent to "-DFOO=1". -# -DBIG_BANG=-9999999LL if the Big Bang occurred at time -9999999 (see zic.c) # -DDEPRECATE_TWO_DIGIT_YEARS for optional runtime warnings about strftime # formats that generate only the last two digits of year numbers # -DEPOCH_LOCAL if the 'time' function returns local time not UT diff --git a/NEWS b/NEWS index b90e68c..87f675e 100644 --- a/NEWS +++ b/NEWS @@ -27,6 +27,12 @@ Unreleased, experimental changes legacy zones EST5EDT, CST6CDT, MST7MDT, PST8PDT, CET, MET, and EET, which previously used nonzero types for these timestamps. + Because of the type 0 change, zic no longer outputs a dummy + transition at time -2**59 (before the Big Bang), as clients should + no longer need this to handle historical timestamps correctly. + This reverts a change introduced in 2013d and shrinks most TZif + files by a few bytes. + localtime.c no longer requires at least one time type in TZif files that lack transitions or have a POSIX-style TZ string. This future-proofs the code against possible future extensions to the diff --git a/zic.8 b/zic.8 index ba4796e..00d4267 100644 --- a/zic.8 +++ b/zic.8 @@ -591,12 +591,6 @@ produces a single transition to daylight saving at the new UT offset To get separate transitions use multiple zone continuation lines specifying transition instants using universal time. -.PP -timestamps well before the Big Bang are silently omitted from the output. -This works around bugs in software that mishandles large negative time -stamps. Call it sour grapes, but pre-Big-Bang timestamps are -physically suspect anyway. The pre-Big-Bang cutoff time is -approximate and may change in future versions. .SH FILES .ta \w'/usr/share/zoneinfo\0\0'u /etc/localtime default local time zone file diff --git a/zic.c b/zic.c index fd73f66..88153db 100644 --- a/zic.c +++ b/zic.c @@ -948,48 +948,6 @@ dolink(char const *fromfield, char const *tofield, bool staysymlink) static zic_t const min_time = MINVAL(zic_t, TIME_T_BITS_IN_FILE); static zic_t const max_time = MAXVAL(zic_t, TIME_T_BITS_IN_FILE); -/* Estimated time of the Big Bang, in seconds since the POSIX epoch. - rounded downward to the negation of a power of two that is - comfortably outside the error bounds. - - For the time of the Big Bang, see: - - Ade PAR, Aghanim N, Armitage-Caplan C et al. Planck 2013 results. - I. Overview of products and scientific results. - arXiv:1303.5062 2013-03-20 20:10:01 UTC - <https://arxiv.org/pdf/1303.5062v1> [PDF] - - Page 36, Table 9, row Age/Gyr, column Planck+WP+highL+BAO 68% limits - gives the value 13.798 plus-or-minus 0.037 billion years. - Multiplying this by 1000000000 and then by 31557600 (the number of - seconds in an astronomical year) gives a value that is comfortably - less than 2**59, so BIG_BANG is - 2**59. - - BIG_BANG is approximate, and may change in future versions. - Please do not rely on its exact value. */ - -#ifndef BIG_BANG -#define BIG_BANG (- (1LL << 59)) -#endif - -/* If true, work around GNOME glib bug 878 - <https://gitlab.gnome.org/GNOME/glib/issues/878> - by refusing to output timestamps before BIG_BANG. - Such timestamps are physically suspect anyway. - The glib bug is scheduled to be fixed in glib 2.58. - There is a similar bug in 32-bit glibc 2.27 and earlier - <https://sourceware.org/bugzilla/show_bug.cgi?id=19738> - that is scheduled to be fixed in glibc 2.28; - unfortunately a similar bug might persist in 64-bit glibc - though this has not been verified. With all this in mind, - let's hope that the workaround will no longer be needed - in the year 2025. */ -enum { WORK_AROUND_CLIENT_OVERFLOW_BUGS = true }; - -static const zic_t early_time = (WORK_AROUND_CLIENT_OVERFLOW_BUGS - ? BIG_BANG - : MINVAL(zic_t, TIME_T_BITS_IN_FILE)); - /* Return true if NAME is a directory. */ static bool itsdir(char const *name) @@ -1775,7 +1733,8 @@ swaptypes(int i, int j) } static void -writezone(const char *const name, const char *const string, char version) +writezone(const char *const name, const char *const string, char version, + int defaulttype) { register FILE * fp; register ptrdiff_t i, j; @@ -1805,13 +1764,11 @@ writezone(const char *const name, const char *const string, char version) toi = 0; fromi = 0; - while (fromi < timecnt && attypes[fromi].at < early_time) - ++fromi; for ( ; fromi < timecnt; ++fromi) { - if (toi > 1 && ((attypes[fromi].at + + if (toi != 0 && ((attypes[fromi].at + gmtoffs[attypes[toi - 1].type]) <= - (attypes[toi - 1].at + - gmtoffs[attypes[toi - 2].type]))) { + (attypes[toi - 1].at + gmtoffs[toi == 1 ? 0 + : attypes[toi - 2].type]))) { attypes[toi - 1].type = attypes[fromi].type; continue; @@ -1919,8 +1876,8 @@ writezone(const char *const name, const char *const string, char version) for (pass = 1; pass <= 2; ++pass) { register ptrdiff_t thistimei, thistimecnt, thistimelim; register int thisleapi, thisleapcnt, thisleaplim; - int old0, new0; - char omittype[TZ_MAX_TYPES + 1]; + int old0; + char omittype[TZ_MAX_TYPES]; int typemap[TZ_MAX_TYPES]; register int thistypecnt; char thischars[TZ_MAX_CHARS]; @@ -1945,45 +1902,17 @@ writezone(const char *const name, const char *const string, char version) error(_("too many transition times")); thistimelim = thistimei + thistimecnt; thisleaplim = thisleapi + thisleapcnt; - memset(omittype, thistimecnt != timecnt, typecnt); - if (thistimecnt == 0) { - /* - ** No transition times fall in the current - ** (32- or 64-bit) window. - */ - if (typecnt != 0) - omittype[typecnt - 1] = false; - } else { - for (i = thistimei - 1; i < thistimelim; ++i) - if (i >= 0) - omittype[types[i]] = false; - /* - ** For America/Godthab and Antarctica/Palmer - */ - if (thistimei == 0) - omittype[0] = false; - } - - /* Reorder types to make type 0 the first-used standard type - if one is used, otherwise the first-used DST type if one - is used, otherwise no reordering. Use TYPEMAP to swap - OLD0 and NEW0 so that NEW0 appears as type 0 in the output - instead of OLD0. TYPEMAP also omits unused types. */ - omittype[typecnt] = false; /* strlen sentinel */ + memset(omittype, true, typecnt); + omittype[defaulttype] = false; + for (i = thistimei; i < thistimelim; i++) + omittype[types[i]] = false; + + /* Reorder types to make DEFAULTTYPE type 0. + Use TYPEMAP to swap OLD0 and DEFAULTTYPE so that + DEFAULTTYPE appears as type 0 in the output instead + of OLD0. TYPEMAP also omits unused types. */ old0 = strlen(omittype); - new0 = -1; - for (i = 0; i < timecnt; i++) - if (!omittype[types[i]]) { - if (! isdsts[types[i]]) { - new0 = types[i]; - break; - } - if (new0 < 0) - new0 = types[i]; - } - if (new0 < 0) - new0 = old0; - swaptypes(old0, new0); + swaptypes(old0, defaulttype); #ifndef LEAVE_SOME_PRE_2011_SYSTEMS_IN_THE_LURCH /* @@ -2035,7 +1964,8 @@ writezone(const char *const name, const char *const string, char version) thistypecnt = 0; for (i = old0; i < typecnt; i++) if (!omittype[i]) - typemap[i == old0 ? new0 : i == new0 ? old0 : i] + typemap[i == old0 ? defaulttype + : i == defaulttype ? old0 : i] = thistypecnt++; for (i = 0; i < sizeof indmap / sizeof indmap[0]; ++i) @@ -2133,7 +2063,7 @@ writezone(const char *const name, const char *const string, char version) for (i = old0; i < typecnt; i++) if (!omittype[i]) putc(ttisgmts[i], fp); - swaptypes(old0, new0); + swaptypes(old0, defaulttype); } fprintf(fp, "\n%s\n", string); close_file(fp, directory, name); @@ -2487,6 +2417,7 @@ outzone(const struct zone *zpfirst, ptrdiff_t zonecount) zic_t one = 1; zic_t y2038_boundary = one << 31; zic_t max_year0; + int defaulttype = -1; max_abbr_len = 2 + max_format_len + max_abbrvar_len; max_envvar_len = 2 * max_abbr_len + 5 * 9; @@ -2595,9 +2526,9 @@ outzone(const struct zone *zpfirst, ptrdiff_t zonecount) */ stdoff = 0; zp = &zpfirst[i]; - usestart = i > 0 && (zp - 1)->z_untiltime > early_time; + usestart = i > 0 && (zp - 1)->z_untiltime > min_time; useuntil = i < (zonecount - 1); - if (useuntil && zp->z_untiltime <= early_time) + if (useuntil && zp->z_untiltime <= min_time) continue; gmtoff = zp->z_gmtoff; eat(zp->z_filename, zp->z_linenum); @@ -2612,7 +2543,8 @@ outzone(const struct zone *zpfirst, ptrdiff_t zonecount) if (usestart) { addtt(starttime, type); usestart = false; - } else addtt(early_time, type); + } else + defaulttype = type; } else for (year = min_year; year <= max_year; ++year) { if (useuntil && year > zp->z_untilrule.r_hiyear) break; @@ -2726,6 +2658,8 @@ outzone(const struct zone *zpfirst, ptrdiff_t zonecount) offset = oadd(zp->z_gmtoff, rp->r_stdoff); type = addtype(offset, ab, rp->r_isdst, rp->r_todisstd, rp->r_todisgmt); + if (defaulttype < 0 && !rp->r_isdst) + defaulttype = type; if (rp->r_hiyear == ZIC_MAX && ! (0 <= lastatmax && ktime < attypes[lastatmax].at)) @@ -2742,11 +2676,14 @@ outzone(const struct zone *zpfirst, ptrdiff_t zonecount) eat(zp->z_filename, zp->z_linenum); if (*startbuf == '\0') error(_("can't determine time zone abbreviation to use just after until time")); - else addtt(starttime, - addtype(startoff, startbuf, - startoff != zp->z_gmtoff, - startttisstd, - startttisgmt)); + else { + bool isdst = startoff != zp->z_gmtoff; + type = addtype(startoff, startbuf, isdst, + startttisstd, startttisgmt); + if (defaulttype < 0 && !isdst) + defaulttype = type; + addtt(starttime, type); + } } /* ** Now we may get to set starttime for the next zone line. @@ -2761,6 +2698,8 @@ error(_("can't determine time zone abbreviation to use just after until time")); starttime = tadd(starttime, -gmtoff); } } + if (defaulttype < 0) + defaulttype = 0; if (0 <= lastatmax) attypes[lastatmax].dontmerge = true; if (do_extend) { @@ -2788,7 +2727,7 @@ error(_("can't determine time zone abbreviation to use just after until time")); attypes[timecnt - 1].dontmerge = true; } } - writezone(zpfirst->z_name, envvar, version); + writezone(zpfirst->z_name, envvar, version, defaulttype); free(startbuf); free(ab); free(envvar); @@ -2797,20 +2736,6 @@ error(_("can't determine time zone abbreviation to use just after until time")); static void addtt(zic_t starttime, int type) { - if (starttime <= early_time - || (timecnt == 1 && attypes[0].at < early_time)) { - gmtoffs[0] = gmtoffs[type]; - isdsts[0] = isdsts[type]; - ttisstds[0] = ttisstds[type]; - ttisgmts[0] = ttisgmts[type]; - if (abbrinds[type] != 0) - strcpy(chars, &chars[abbrinds[type]]); - abbrinds[0] = 0; - charcnt = strlen(chars) + 1; - typecnt = 1; - timecnt = 0; - type = 0; - } attypes = growalloc(attypes, sizeof *attypes, timecnt, &timecnt_alloc); attypes[timecnt].at = starttime; attypes[timecnt].dontmerge = false; -- 2.7.4

1 0

[PROPOSED] GNOME glib bug fix installed
by Paul Eggert June 13, 2018

June 13, 2018

The bug fix was merged into glib master today. Since it’s four years after the fix was proposed (!), push back an estimate of when we can remove the workaround. Also, adjust to GNOME bug renumbering. * NEWS: Adjust bug number in history. * zic.c (WORK_AROUND_GLIB_BUG_878): Rename from WORK_AROUND_GNOME_BUG_730332. All uses changed. --- NEWS | 4 ++-- zic.c | 14 +++++++------- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/NEWS b/NEWS index 34f7810..b90e68c 100644 --- a/NEWS +++ b/NEWS @@ -2106,8 +2106,8 @@ Release 2014d - 2014-05-27 21:34:40 -0700 Changes affecting code zic no longer generates files containing timestamps before the Big Bang. - This works around GNOME bug 730332 - <https://bugzilla.gnome.org/show_bug.cgi?id=730332>. + This works around GNOME glib bug 878 + <https://gitlab.gnome.org/GNOME/glib/issues/878> (Thanks to Leonardo Chiquitto for reporting the bug, and to Arthur David Olson and James Cloos for suggesting improvements to the fix.) diff --git a/zic.c b/zic.c index ce9ccaf..9e25b02 100644 --- a/zic.c +++ b/zic.c @@ -972,17 +972,17 @@ static zic_t const max_time = MAXVAL(zic_t, TIME_T_BITS_IN_FILE); #define BIG_BANG (- (1LL << 59)) #endif -/* If true, work around GNOME bug 730332 - <https://bugzilla.gnome.org/show_bug.cgi?id=730332> +/* If true, work around GNOME glib bug 878 + <https://gitlab.gnome.org/GNOME/glib/issues/878> by refusing to output timestamps before BIG_BANG. Such timestamps are physically suspect anyway. - The GNOME bug is scheduled to be fixed in GNOME 3.22, and if so - this workaround will no longer be needed when GNOME 3.21 and - earlier are obsolete, say in the year 2021. */ -enum { WORK_AROUND_GNOME_BUG_730332 = true }; + The glib bug is scheduled to be fixed in glib 2.58, and if so + this workaround will no longer be needed when glib 2.57 and + earlier are obsolete, say in the year 2025. */ +enum { WORK_AROUND_GLIB_BUG_878 = true }; -static const zic_t early_time = (WORK_AROUND_GNOME_BUG_730332 +static const zic_t early_time = (WORK_AROUND_GLIB_BUG_878 ? BIG_BANG : MINVAL(zic_t, TIME_T_BITS_IN_FILE)); -- 2.17.1

2 2

Clarification on LMT entries
by Matt Johnson June 8, 2018

June 8, 2018

Quick question. The entry for Europe/Kiev has two solar mean time entries: Zone Europe/Kiev 2:02:04 - LMT 1880 2:02:04 - KMT 1924 May 2 # Kiev Mean Time While I know how to read this, I'm not sure why the abbreviation KMT exists. Is this another invented abbreviation, or is there a source? Also, why 1880 on the LMT line? What is special about 1880? Thanks, Matt

4 3

Secure FTP support for IANA downloads
by pbassey＠ups.com June 6, 2018

June 6, 2018

Hello, I am writing to inquire about your site's use of FTP and the possibility of migrating over to Secure FTP in order to comply with our company's security compliance requirements. Does your site offer Secure FTP for your IANA downloads and if not, what would it take to enable this protocol so our company could securely download your files? Currently, we use this URL to download the IANA time zone files which is not secure: ftp://ftp.iana.org/tz/ Thank you in advance for your help. Regards, Peter Bassey Peter A. Bassey Enterprise Business Intelligence UPS 340 MacArthur Blvd Mahwah, NJ 07430 Phone: 201-828-7847 Mobile: 845-662-3743 pbassey(a)ups.com<mailto:pbassey@ups.com>

6 6