Subject: | |
From: | |
Reply To: | |
Date: | Fri, 9 Mar 2007 09:58:21 -0800 |
Content-Type: | TEXT/PLAIN |
Parts/Attachments: |
|
|
On Fri, 9 Mar 2007, Troy Dawson wrote:
> Hello,
> Many thanks to those who have tested.
> My greatest thanks go to Art Kraymer who correctly pointed out that this
> update was *not needed*. The j2sdk that we pushed out in the errata's last
> time (j2sdk-1.4.2_12) actually has the correct time zone changes.
but not for some Canadians; it contains date set 2006a; for
America/Vancouver we need 2006g. Thus for our systems I applied the patch
via tzupdater a few days ago to the Tier1 centre; here is example output
showing that the patch goes from set 2006a to 2007a:
# java -jar ~deatrich/tz/tzupdater2007a/tzupdater.jar -v -u
java.home: /usr/java/j2sdk1.4.2_12/jre
java.vendor: Sun Microsystems Inc.
java.version: 1.4.2_12
JRE time zone data version: tzdata2006a
Embedded time zone data version: tzdata2007a
Extracting files... done.
Renaming directories... done.
Validating the new time zone data... done.
Time zone data update is complete.
and diff-ing the orig. and the patched java tree:
# diff -r j2sdk1.4.2_12 j2sdk1.4.2_12.sv
...
Binary files j2sdk1.4.2_12/jre/lib/zi/America/Vancouver and j2sdk1.4.2_12.sv/jre/lib/zi/America/Vancouver differ
...
In other words, it is often the small regional differences that matter..
cheers,
denice
--
deatrich @ triumf.ca, Science/Atlas PH: +1 604-222-7665
<*> This moment's fortune cookie:
They're only trying to make me LOOK paranoid!
|
|
|