Vào 11:01, Th 6, 22 thg 2, 2019 <tz-request@iana.org đã viết:

Send tz mailing list submissions to
tz@iana.org

To subscribe or unsubscribe via the World Wide Web, visit
https://mm.icann.org/mailman/listinfo/tz
or, via email, send a message with subject or body 'help' to
tz-request@iana.org

You can reach the person managing the list at
tz-owner@iana.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of tz digest..."

Today's Topics:

1. Re: Please remove tzdata2018f (Paul Eggert)
2. Re: Please remove tzdata2018f (Philip Paeps)
3. Re: Please remove tzdata2018f (Marcos Passos)
4. Re: Please remove tzdata2018f (Marcos Passos)
5. Re: Please remove tzdata2018f (Philip Paeps)
6. Re: Please remove tzdata2018f (Brian Inglis)

----------------------------------------------------------------------

Message: 1
Date: Thu, 21 Feb 2019 11:03:25 -0800
From: Paul Eggert <eggert@cs.ucla.edu>
To: Ankur Rana <ankur.rana@ericsson.com>, "tz@iana.org" <tz@iana.org>
Cc: "Sunil A. K." <sunil.a.k@ericsson.com>, Nishit Khosla
<Nishit.Khosla@ericsson.com>, Jaspreet Singh D
<jaspreet.d.singh@ericsson.com>
Subject: Re: [tz] Please remove tzdata2018f
Message-ID: <1a71a103-df7c-858c-eb96-ef07221760f1@cs.ucla.edu>
Content-Type: text/plain; charset=utf-8; format=flowed

On 2/20/19 11:31 PM, Ankur Rana wrote:
> would it be possible to prevent the tzdata version 2018f from
> downloading on iana site?

Although it would be possible I doubt whether it would be a good idea.
2018f does work for many downstream users, and these users wouldn't
benefit by its withdrawal from publication. Besides, standard practice
should be to use the latest version, falling back on a previous version
only if there's trouble.

------------------------------

Message: 2
Date: Fri, 22 Feb 2019 09:55:05 +0900
From: "Philip Paeps" <philip@trouble.is>
To: "Ankur Rana" <ankur.rana@ericsson.com>
Cc: "Sunil A. K." <sunil.a.k@ericsson.com>, tz@iana.org, Nishit Khosla
<Nishit.Khosla@ericsson.com>, Jaspreet Singh D
<jaspreet.d.singh@ericsson.com>
Subject: Re: [tz] Please remove tzdata2018f
Message-ID: <68869755-39C8-4978-A0FF-C5209A05E76A@trouble.is>
Content-Type: text/plain; format=flowed

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.

Paul also helpfully provides rearguard tarballs on his webpage
https://web.cs.ucla.edu/~eggert/tz/release/.

You can easily generate those yourself by running make
rearguard_tarballs on the distribution from iana.org.

> To avoid any reoccurrence of same, would it be possible to prevent the
> tzdata version 2018f from downloading on iana site?

It seems silly to pull one release from an archive going back to 1993
because one third-party implementation (even if it's a popular one)
cannot cope with the data format.

Philip

--
Philip Paeps
Senior Reality Engineer
Ministry of Information

------------------------------

Message: 3
Date: Thu, 21 Feb 2019 22:14:52 -0300
From: Marcos Passos <marcospassos.com@gmail.com>
To: Philip Paeps <philip@trouble.is>, Stephen Colebourne
<scolebourne@joda.org>
Cc: Nishit Khosla <Nishit.Khosla@ericsson.com>, "Sunil A. K."
<sunil.a.k@ericsson.com>, tz@iana.org, Ankur Rana
<ankur.rana@ericsson.com>, Jaspreet Singh D
<jaspreet.d.singh@ericsson.com>
Subject: Re: [tz] Please remove tzdata2018f
Message-ID:
<CANA3Des+0ZG=p33EndxeWhYAsysriW+2y9=Dr6rZJE2EYzEbyQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

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

On Thu, Feb 21, 2019 at 21:55 Philip Paeps <philip@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.
>
> Paul also helpfully provides rearguard tarballs on his webpage
> https://web.cs.ucla.edu/~eggert/tz/release/.
>
> You can easily generate those yourself by running make
> rearguard_tarballs on the distribution from iana.org.
>
> > To avoid any reoccurrence of same, would it be possible to prevent the
> > tzdata version 2018f from downloading on iana site?
>
> It seems silly to pull one release from an archive going back to 1993
> because one third-party implementation (even if it's a popular one)
> cannot cope with the data format.
>
> Philip
>
> --
> Philip Paeps
> Senior Reality Engineer
> Ministry of Information
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/tz/attachments/20190221/1167878e/attachment-0001.html>

------------------------------

Message: 4
Date: Thu, 21 Feb 2019 22:17:11 -0300
From: Marcos Passos <marcospassos.com@gmail.com>
To: Philip Paeps <philip@trouble.is>, Stephen Colebourne
<scolebourne@joda.org>
Cc: Nishit Khosla <Nishit.Khosla@ericsson.com>, "Sunil A. K."
<sunil.a.k@ericsson.com>, tz@iana.org, Ankur Rana
<ankur.rana@ericsson.com>, Jaspreet Singh D
<jaspreet.d.singh@ericsson.com>
Subject: Re: [tz] Please remove tzdata2018f
Message-ID:
<CANA3DesboGcZaarSX-pw46KdnSk-LHwVx3NmBnt-jo5hC-MRnw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

*a few months ago

On Thu, Feb 21, 2019 at 22:14 Marcos Passos <marcospassos.com@gmail.com>
wrote:

> Stephen can confirm it, but I built all versions since 2018 using JSR-310
> a few months and the result was correct.
>
> On Thu, Feb 21, 2019 at 21:55 Philip Paeps <philip@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.
>>
>> Paul also helpfully provides rearguard tarballs on his webpage
>> https://web.cs.ucla.edu/~eggert/tz/release/.
>>
>> You can easily generate those yourself by running make
>> rearguard_tarballs on the distribution from iana.org.
>>
>> > To avoid any reoccurrence of same, would it be possible to prevent the
>> > tzdata version 2018f from downloading on iana site?
>>
>> It seems silly to pull one release from an archive going back to 1993
>> because one third-party implementation (even if it's a popular one)
>> cannot cope with the data format.
>>
>> Philip
>>
>> --
>> Philip Paeps
>> Senior Reality Engineer
>> Ministry of Information
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/tz/attachments/20190221/27740b6a/attachment-0001.html>

------------------------------

Message: 5
Date: Fri, 22 Feb 2019 10:19:26 +0900
From: "Philip Paeps" <philip@trouble.is>
To: "Marcos Passos" <marcospassos.com@gmail.com>
Cc: tz@iana.org, "Sunil A. K." <sunil.a.k@ericsson.com>, Stephen
Colebourne <scolebourne@joda.org>, Nishit Khosla
<Nishit.Khosla@ericsson.com>, Ankur Rana <ankur.rana@ericsson.com>,
Jaspreet Singh D <jaspreet.d.singh@ericsson.com>
Subject: Re: [tz] Please remove tzdata2018f
Message-ID: <B8BF5DED-EF44-4FD7-A5C9-F6A4101AFF8B@trouble.is>
Content-Type: text/plain; format=flowed

On 2019-02-22 10:14:52 (+0900), Marcos Passos wrote:
> On Thu, Feb 21, 2019 at 21:55 Philip Paeps <philip@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.

Good to know!

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.

Philip

--
Philip Paeps
Senior Reality Engineer
Ministry of Information

------------------------------

Message: 6
Date: Thu, 21 Feb 2019 21:00:39 -0700
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: tz@iana.org
Subject: Re: [tz] Please remove tzdata2018f
Message-ID: <380de863-14a6-43fb-8505-7c7ec9990d6a@SystematicSw.ab.ca>
Content-Type: text/plain; charset=utf-8

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@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.

------------------------------

Subject: Digest Footer

_______________________________________________
tz mailing list
tz@iana.org
https://mm.icann.org/mailman/listinfo/tz

------------------------------

End of tz Digest, Vol 89, Issue 38
**********************************