ref: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559663
Hi Juhapekka, thanks for the bug report. gworldclock just uses the system timezones, so the proper place for this bug is in tzdata. But I'm interested in the nature of the bug so I'll discuss it before passing it over to tzdata (well, I could insert special cases in gworldclock, but it would be better to have it handled for everyone in tzdata). tzdata places known timezones into /usr/share/zoneinfo. You can see GMT and UTC both there alongside geographical locations. Notice how none of Loran-C, GPS or TAI can be found there. So these timezones are not known to Debian. I'm not familiar with them, would you be able to explain why you'd expect the TZ variable to know about them? Do other operating systems usually include them? It's because these timezones "don't exist" that you're seeing the behaviour you report. When the TZ variable is set to some unknown value then time/date is set to GMT as default (or maybe it's UTC, I'm not sure). You can test it by entering some completely random value. Thanks, Drew -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
