- tz - lists.iana.org

tzdata repo at Google Code is gone
by Øyvind A. Holm Oct. 11, 2011

Oct. 11, 2011

There used to be an svn repo on http://code.google.com/p/tzdata/ containing the tz data in various formats (csv, json, xml, etc), but now it's gone. Does anyone know what happened to it? Anyway, on 2011-10-08 I converted it from Svn to Git, and this repo (with full history, newest version is tzdata2011j) is stored at https://gitorious.org/tz/tzdata . It can be cloned with git clone git://gitorious.org/tz/tzdata.git Regards, Øyvind

1 0

tzdata2011l.tar.gz
by Robert Elz Oct. 10, 2011

Oct. 10, 2011

The file ... ftp://munnari.oz.au/pub/tzdata2011l.tar.gz ...is now available; this reflects changes circulated last week on the time zone mailing list. There are just 2 changes that cause different generated tzdata files from zic, to Asia/Hebron and Pacific/Fiji - the possible change for Bahia, Brazil is included, but commented out. Compared with the diff I sent out last week, this version also includes attributions for the sources for the changes (in much the same format as ado used, but the html tags have not been checked, verified, or used in any way at all, so if there are errors there, please let me know.) Unfortunately, there are no signatures, it turns out that I have not used any form of PGP in so long that getting my keys into a form where they're usable by gpg is somewhat of a challenge - so most probably I'll just generate a new key (as was suggested, and which is obviously the sane approach) for tz distributions - the down side is that at least initially it isn't going to be signed (trusted) by anyone at all... To compensate for this lack of signatures, I'm appending (in this message) a list of digest values, crypto hash function digests generated by a number of different algorithms (all from the NetBSD pkgsrc "digest" program). Those ought to give a fair degree of confidence that the tarball has not been compromised, and by distributing them in this message, essentially no way for anyone to compromise the digest values (which is the one thing that a proper signature would ensure). Lastly, for now, because people seem to be mirroring ftp://munnari.oz.au/pub/oldtz/ I have included the current versions of the data & code files there, as well as their normal home in ftp://munnari.oz.au/pub - previously the oldtz directory contained only the obsolete tarballs. But thanks to Joseph S. Myers, the oldtz directory now includes a few extra archives that I had been missing, including the extremely elusive tzcode2003b which had been replaced before I even new it existed (and no, you don't really want it, it contained a fairly serious bug, which is why it was replaced so quickly...) kre MD5 (tzdata2011l.tar.gz) = bae1b93673e1aef80186c90dfd493f1c RMD160 (tzdata2011l.tar.gz) = b933711b06246c9d452d846a193b53295a966287 SHA1 (tzdata2011l.tar.gz) = c6740ec9645b78750e2109b6d42cd283e16988d7 SHA512 (tzdata2011l.tar.gz) = a1d2dd68ddd3822f94cd817a3e70277e6e9e347c12aa788533d36ad0ad03f0ec39d925301d64c6ab27825212dffd0ec03c3944096ef479318815a8e1f362c841 TIGER (tzdata2011l.tar.gz) = f0578e0cab5f39f13c49b076cc2955da95e9111b98ffe57c WHIRLPOOL (tzdata2011l.tar.gz) = aa6812740e077e064de7348f2deb15e1bfe8cbb93a336dde58e625b76f4832c8c6601bb06437ac04c05b232f142b1119841f5bab50656907b3a1459906c818a1

7 8

Update docs/comments regarding move from elsie to iana
by Kevin Lyda Oct. 10, 2011

Oct. 10, 2011

There are several places in the code that refer to the ftp server and mailing list on elsie. The following patch points people at the currently correct places. Kevin -- Kevin Lyda Dublin, Ireland US Citizen overseas? We can vote. Register now: http://www.votefromabroad.org/

1 0

Digital signing (was Re: Proposed time zone package changes ...)
by Bennett Todd Oct. 9, 2011

Oct. 9, 2011

For signing the data files, I'm fond of pgp, with gpg being the implementation I trust best. Sadly, standardization efforts seem to end up being used to add sponsorship for certificate signing authorities, we all have seen how well that has worked for SSL. Hope you can go with pgp; the current Certificate Authority fiasco follows as expected from the observation that trust doesn't scale. As for details, I don't know anything wrong with the default algorithms that gpg uses. But ideally you shouldn't be using your own key directly, but rather a new, project-specific key for the project's official contact email address. You can start it off by signing it with your key, and other folks can add signatures after verifying the fingerprint with you offline.

3 2

Another mirror + mirror shell script
by Sebastian Majstorovic Oct. 9, 2011

Oct. 9, 2011

I'd be glad to contribute another mirror, FTP and HTTP, based in Germany: ftp://tzmirror.appealingapps.de http://tzmirror.appealingapps.de If anyone else wants to setup a mirror, here's a one-line shell script which sets one up: /usr/bin/lftp -c 'open -e "mirror --parallel=5 -e -x ^[^t][^z] -i oldtz /pub /path/to/local/directory" munnari.oz.au' If you run it daily, e.g. as a cron, the files on the mirror are always kept up-to-date. Best Regards Sebastian

1 1

Re: [tz] A history maintaining repository for tzdata
by Kevin Lyda Oct. 8, 2011

Oct. 8, 2011

On Sat, Oct 8, 2011 at 08:43, Bill Sommerfeld <sommerfeld(a)alum.mit.edu> wrote: > An ancestor of the current tzdata was posted to the usenet mod.sources > newsgroup with a date of March 7, 1986; I found copies at: Fantastic. I got the idea that Usenet was the next place to go, but I had to catch a bus so I put the initial part up to let people know what I was working on. Annoyingly the reason I threw my work up on github in a hurry last night was because I was going to Galway last night. Now I'm here and while I have the CDROM *cases* of the first three volumes of the Walnut Creek Usenet Source Code archive, I suspect the CDROMs themselves are back in Dublin. Argh. Anyway, thanks for the links. Any additional early releases I find will have similar style commits - correct authors, timestamps and message ids. I'm downloading the comp.sources.unix archives now and will get the mod.sources archives next. Was settz posted on alt.sources prior to mod.sources? As for the points raised by other posters - US based hosts and preserving SCCS history... First, I chose github just for a quick place to push the repo. I obviously have the full copy (and more importantly the scripts used to generate it which I'll push up later today) and I'm in Ireland. It lives in a VM on my laptop and I've pushed out all the materials I used to build the repo to a few other machines in other countries. I have two thoughts on US based servers. First, there are a host of other projects on github that have these files in some form so I'm not really concerned. Second, this repository is a work in progress that folks here can evaluate in terms of its structure (see the README for the issues I'd like feedback on). It's my belief that I should send my repo generation scripts and supporting metadata to kre (or ado or eggert) and have them generate the repo that people actually use. Lastly I completely agree that the SCCS history should be preserved if possible. However I don't think I can get access to it without cause ado or eggert a lot of problems. I think I know how to weave in SCCS commits into the resulting git tree. Essentially the algorithm will go something like this (in shell/pythony pseudo code): for commit, next_commit in list_of_tags; do start_date=# get date of this commit end_date=# get date of next commit # get list of changes in sccs repository between those dates # for each change, get the date, commit message and diff # apply diff to repo, commit with correct date and metadata git rebase next_commit done How to do this will depend on what ado actually uses - SCCS or RCS or if he migrated from one to the other at some point. I also suspect there are some tweaks that will be required (I'm not sure how rebase deals with empty commits for instance and if everything is working correctly every rebase will cause an empty commit). And obviously when that happens everyone would need to resync their tree. But I'm happy to help make it happen. In the meantime I'll get the scripts and data kre needs to generate a repo that he can make a "blessed" repository for his own use (and wherever he chooses to publish it - if anywhere). Well, first I'll get the pre-93 sources and the tzcode in there first. Kevin

1 0

Re: [tz] Source material used by ACS atlas book editions
by Alois Treindl Oct. 7, 2011

Oct. 7, 2011

Stephen I don't quite understand why you fear this, but I am not a lawyer and not familiar with US law. I will use other channels for such contributions, if there should be any. As material for Olson's and Eggert's defense I think these quotes of Shanks's sources are relevant. Later (current) editions of the books do no longer mention any sources, only the old editions do. They confirm in writing that Shanks copied most of his data from other published sources. Knowledge of the sources will make it rather easy to clean up TZ files from quotes of Shanks. I think personally that no such cleanup should happen. The lawsuit should be fought and will be won by Olson and Eggert, as their use they make of Shanks' data is fully legitimate. Stephen Colebourne wrote: > Please don't send more information like this. You may contaminate the > new list and expand the lawsuit. > Stephen > >

1 0

(no subject)
by Paw Boel Nielsen Oct. 7, 2011

Oct. 7, 2011

I suggest you let your opinion known here: http://www.facebook.com/pages/Astrolabe-Astrology-Software-and-Services/525…

4 3

Source material used by ACS atlas book editions
by Alois Treindl Oct. 7, 2011

Oct. 7, 2011

I have taken some snapshots to review the sources used for the data collection in ACS American Atlas and International Atlas. The sources are referenced well in the bibliography of the 1st edition of International Atlas. Later editions do not give such information anymore. For American Atlas, the sources are mentioned to some extent in prefaces, acknowledgments, notes and in an advertising found in International Atlas. I think this material can be of relevance to form an opinion about the solidity of the Astrolabe lawsuit against Olson and Eggert.

1 0

mailing list archives
by Zefram Oct. 7, 2011

Oct. 7, 2011

I see the webbified tz(a)iana.org mailing list archive has been prepopulated with tzarchive.gz from elsie. ++ to whoever did that. But tzarchive.gz is incomplete: it bizarrely stopped being updated in May. In light of recent revelations, it's now notable that the last update coincides approximately with Astrolabe sending a takedown notice (2011-05-12 according to the legal complaint). Anyway, it would be nice if the missing five months could be imported too. It's available at <http://news.gmane.org/gmane.comp.time.tz>. -zefram

1 0