- tz - lists.iana.org

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

Re: [tz] temporary timezone database home ...
by Zefram Oct. 7, 2011

Oct. 7, 2011

If we're going the git route (which is a good idea), I suggest *not* using github. Github has terms of service that can change without notice in problematic ways. The tz collective is large enough that there should be no problem in hosting our own git server, such as the one that Yann Droneaud has provided as a prototype. Ideally we'd have a git server hosted at munnari. I think a single repository covering both code and data files would be better than separate code and data repositories. The two parts are too interconnected to work with separately. Btw, I was one of the unlucky sods (maybe the only unlucky sod?) who, having joined tz@elsie only a week ago, was omitted from the initial subscriber list for tz@iana. Good work getting things going so quickly. -zefram

1 0

Fwd: temporary timezone database home ...
by Alex Mayorga Adame Oct. 7, 2011

Oct. 7, 2011

---------- Forwarded message ---------- From: Alex Mayorga Adame <alex.mayorga(a)gmail.com> Date: Fri, 7 Oct 2011 00:48:50 -0500 Subject: Re: [tz] temporary timezone database home ... To: Robert Elz <kre(a)munnari.oz.au> Hope this nonsense won't grow into to much of a burden for "Olson et al" =( Thanks on your efforts Robert! Can this be made into a .torrent? I do not have permanent hosting other than DynDNS to my laptop in .mx but would gladly contribute some bandwidht if that would help in any way. Alex Mayorga Adame On 10/6/11, Robert Elz <kre(a)munnari.oz.au> wrote: > First, I am assuming this copy of the list is actually functioning, > (and I've just received jhawk's message which demonstrates that it is) > I don't believe it has been used for actual messages before that one, > but as ado has indicated that the list at elsie has been (for now > anyway) terminated - and given the plan was to migrate from it eventually > anyway, may never return, we can but hope this version of the list > is functional. > > Some of you who receive this message may have been removed from the > elsie version of the list recently, or altered your subscription details > - if that applies to you, use the iana.org message sent on the 1st of > this month to all subscribers to their list for instructions on how to > modify or delete your subscription. > > Don't send requests to me (or anyone else on the list) there's nothing I > (or we) can do about it - and most certainly, do not send requests to the > list itself asking to be removed. > > Unfortunately, there are probably a few people who were added to the elsie > list since it was cloned at iana.org but there's nothing much we can do > about that - if anyone is contacted by anyone who believes they should be > on the list, but is no longer receiving messages, direct them to the iana > website for list subscriptions. > > Next, while elsie's ftp server is shut down, munnari.oz.au isn't, and the > tz database & code remains available from here. Further, I will not > respond to requests from (almost) anyone to cease making those files > available (including Arthur and Paul - but by all means feel free to try > if you need to to satisfy some obligation to cease making the data > available - I'll ignore you, but you will at least have used every > reasonable > effort...) > > Second, regardless of this, the world's governments continue to adjust > their view of their local timezones & summer time adjustments, so we > need to continue updating the database (at least). There are several > updates that will be needed soon. > > For now, until someone else volunteers, I'm prepared to make the updates, > in much the same way that Arthur did, and then make new releases available > from munnari's ftp server. I suspect that it is unlikely that either Arthur > or Paul will be able to assist much with this in the coming months, so > I'm hoping that others will assist where possible. > > For now, I'm aware of changes needed for Armenia, Fiji, Bolivia, Brazil, > and of course, the changes that (might be) needed for Russia. If there's > anything else I missed, please let me know. > > Unfortunately, I don't have the sccs (or is it rcs or something these days) > master files, so I won't be able to do quite the same job that Arthur did, > but I can keep all versions so they can be checked into a version control > system later. > > It would be good if a few others, especially people in jurisdictions that > tend not to simply bow down to US court rulings, would keep copies of the > code and data, and make them publicly available via ftp or http (this > is not of huge public interest, the resources needed to provide this > service should not be very noticeable). > > All I know of the lawsuit is what jhawk's message indicated - eventually > I assume we'll find out what trademark or patent that someone believes is > being infringed (a little hard to believe either, but who knows...) > > The URL's of the current versions of the files from munnari.oz.au are ... > > ftp://munnari.oz.au/pub/tzcode2011i.tar.gz > ftp://munnari.oz.au/pub/tzdata2011k.tar.gz > > and of course, the historical files (most versions that were ever previously > released) are in ftp://munnari.oz.au/pub/oldtz/ > > kre > > > -- Enviado desde mi dispositivo móvil

1 0