[tz] Getting close to new release: testing, testing, ...

Paul Eggert eggert at cs.ucla.edu
Wed Sep 11 09:55:08 UTC 2013


We need to release a new version soon, because of Fiji.

I did further testing and it appears that the recent changes
to add meta-information to the zic output won't fly, because
they're incompatible with the GNU C library on Ubuntu 12.04.
So we need to rethink that feature.  There's no rush to introduce
it, so let's omit it from the next release.

Also, the -t option recently added to tzselect seems like it
will be superseded by the tzwinnow approach, whenever we get
that working and stable, so for now I think I'd rather omit
this.

There are a few other problems found by "make public",
mostly links that were in the wrong files.

I'll post proposed changes soon.  If other people could
do some testing that'd be nice.  You can run "make public".
The output should contain the following diagnostics:

warning: "antarctica", line 318: Antarctica/Palmer: pre-2013 clients may mishandle distant timestamps
warning: "asia", line 1412: 24:00 not handled by pre-1998 versions of zic
warning: "asia", line 2332: 24:00 not handled by pre-1998 versions of zic
warning: "asia", line 1026: Asia/Jerusalem: pre-2013 clients may mishandle distant timestamps (rule from "asia", line 1021)
warning: "asia", line 1315: Asia/Amman: pre-1994 clients may mishandle distant timestamps
warning: "asia", line 2016: Asia/Gaza: pre-2013 clients may mishandle distant timestamps
warning: "asia", line 2347: Asia/Hebron: pre-2013 clients may mishandle distant timestamps
warning: "australasia", line 269: Pacific/Fiji: pre-2013 clients may mishandle distant timestamps
warning: "europe", line 998: America/Godthab: pre-2013 clients may mishandle distant timestamps
warning: "southamerica", line 1141: America/Santiago: pre-2013 clients may mishandle distant timestamps
warning: "southamerica", line 1313: Pacific/Easter: pre-2013 clients may mishandle distant timestamps

along with a very long section that starts as follows, which shows that
the tz code is still broken on platforms with unsigned 32-bit time_t
(this is a longstanding problem).

checking uint32_t zones ...
--- tzpublic/int64_t.out	2013-09-11 02:43:50.871343089 -0700
+++ tzpublic/uint32_t.out	2013-09-11 02:43:55.907343185 -0700
@@ -210,278 +210,6 @@
 Europe/Andorra                  Sun Mar 29 01:00:00 2037 UT = Sun Mar 29 03:00:00 2037 CEST isdst=1
 Europe/Andorra                  Sun Oct 25 00:59:59 2037 UT = Sun Oct 25 02:59:59 2037 CEST isdst=1
 Europe/Andorra                  Sun Oct 25 01:00:00 2037 UT = Sun Oct 25 02:00:00 2037 CET isdst=0
-Europe/Andorra                  Sun Mar 28 00:59:59 2038 UT = Sun Mar 28 01:59:59 2038 CET isdst=0
-Europe/Andorra                  Sun Mar 28 01:00:00 2038 UT = Sun Mar 28 03:00:00 2038 CEST isdst=1
-Europe/Andorra                  Sun Oct 31 00:59:59 2038 UT = Sun Oct 31 02:59:59 2038 CEST isdst=1



More information about the tz mailing list