How to figure out which, if any, update changed /etc/localtime from a link to a hard file?

David M. Karr davidmichaelkarr at gmail.com
Fri Apr 17 23:40:49 UTC 2009


Derek Broughton wrote:
> David M. Karr wrote:
> 
>> NoOp wrote:
> 
>>> The most recent updata for intrepid was:
>>>
>>> 2009f-0ubuntu0.8.10
>>> Published in intrepid-proposed on 2009-04-16
>>> tzdata (2009f-0ubuntu0.8.10) intrepid-proposed; urgency=low
>>>   * New timezone data 2009f: (LP: #358232):
>>>     - Fix DST rules for Jordan, Palestine, and Pakistan.
>>>  -- Martin Pitt <email address hidden>   Thu, 16 Apr 2009 12:41:46 +0200
>> That was, like, yesterday. :)
>>
>> I don't see that it matters, however.  It seems pretty clear the tzdata
>> for my timezone is perfectly fine, but the algorithm used to find the
>> data was broken by the fact that /etc/localtime wasn't a symlink. 
> 
> Except that it isn't _supposed_ to be a symlink, which leaves one to wonder
> what you've broken now (and fwiw I've never had a tz problem in Java
> with /etc/localtime being a real file).

 From what I understand, the problem this would create would be subtle. 
  Apparently if it's not a symlink to the specific timezone file, Java 
has to "guess" which one it corresponds to.  Apparently it usually 
guesses correctly for you.




More information about the ubuntu-users mailing list