Re: F29 System Wide Change: The tzdata transition to 'vanguard' format

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Just FTR, this is upstream response:


> Yes, tzinfo supports the vanguard format introduced in tzdata 2018d that became the main format in 2018e.

> Conversions to and from local time will be accurate with any release supporting system zoneinfo files.

> I would recommend using the latest v1.2.5 release though. This includes a fix to allow negative daylight savings time offsets to be derived from zoneinfo files. This sets the TimezonePeriod#std_offset and TimezonePeriod#utc_offset attributes correctly when loading zoneinfo time zones that contain negative DST offsets.


TL;DR rubygem-tzinfo should be compatible with the new tzdata, but I should probably update to the latest version.


Vít



Dne 25.5.2018 v 10:29 Vít Ondruch napsal(a):

Thx for the answer. I opened upstream ticket to doublecheck this:

https://github.com/tzinfo/tzinfo/issues/88


V.


Dne 24.5.2018 v 19:32 Patsy Franklin napsal(a):
Hi,

Thank you for your input on this!

The concern is that, in some cases, applications that parse the tzdata files were not expecting to find negative DST offsets (negative SAVE values in the data files) despite the fact that POSIX appears to support this. 

As this is now the default format for tzdata,  these applications should be fixed to recognize the negative DST offsets.

(NOTE: For f26, f27 and f28, we have provided the rearguard format to continue to support existing applications.  This proposal announces the transition to vanguard format, allowing time to update applications in f29.)

On Wed, May 23, 2018 at 4:51 AM, Vít Ondruch <vondruch@xxxxxxxxxx> wrote:
Is this going to be backward compatible or not? rubygem-tzinfo is using
tzdata as data source, so I wonder if any action is required.


Yes, it's backward compatible if your application recognizes that tzdata SAVE values/DST's can be negative. 
 
Thanks,
Patsy


_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/J3HHRXVANGROHRNHQ4UZ4DNWVYXH3Z2H/



_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/PCN57Q6P74RESICYD2HDF5BKGXDTNAX3/

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/QJD2APH2B4HGDGVKHTW2V22SU7Q2P52H/

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux