[tz] Please remove tzdata2018f

Brian Inglis Brian.Inglis at SystematicSw.ab.ca
Fri Feb 22 04:00:39 UTC 2019

On 2019-02-21 18:19, Philip Paeps wrote:
> On 2019-02-22 10:14:52 (+0900), Marcos Passos wrote:
>> On Thu, Feb 21, 2019 at 21:55 Philip Paeps <philip at trouble.is> wrote:
>>> On 2019-02-21 16:31:39 (+0900), Ankur Rana wrote:
>>>> While doing tzdata upgrade to version 2018f

>>> Note that you should really be upgrading to 2018i, which is the latest version.

>>>> java.lang.Exception: Failed while parsing file '/tmp/tz.tmp/asia' on
>>>> line 1842 'Rule      Japan 1948  1951  -     Sep   Sat>=8      25:00 0     S'

>>> Java is known to be broken with respect to the last ten years or so of
>>> changes to the tzdb data format.  You'll need to generate "rearguard" format
>>> data to feed to the Java updater.

>> Stephen can confirm it,  but I built all versions since 2018 using JSR-310 a
>> few months and the result was correct.

> Last I read on the tz mailing list, the Java tzdb parser doesn't like negative
> SAVE rules or more than 24 hours in a day.  Happy to hear that was fixed at last.
> Thank you for pointing that out.

Marcos didn't say whether it was vanguard, standard, or rearguard format data
that was used for 2018. As JSR 310 appears to be unchanged since 2014, until
Marcos or Stephen explicitly states otherwise, it would be safer to continue to
assume that rearguard format data is required.

Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

More information about the tz mailing list