The sole purpose of this thread is to bring attention to
https://bugzilla.redhat.com/show_bug.cgi?id=1646930
No doubt some of the delay is due to compatibility issues with other packages
that consume timezone data. Upstream changed the data format:
=====
$ rpm -q --changelog tzdata-2018e-1.fc*.noarch
* Wed May 16 2018 [tzdata-ow...@fedoraproject.org] - 2018e-1
- Rebase to tzdata-2018e
- North Korea changed from UTC+8:30 to UTC+9 on May 5, 2018.
- In this update, the upstream project now defaults to using
the "vanguard" data implementation which includes negative DST offsets.
However, we are continuing to provide the "rearguard" format
for data which does not use negative DST offsets to provide
better compatibility with existing tools. We intend to transition
to the "vanguard" data implementation in the future.
=====
Unreliable time on the system is a daily annoyance that will be easily fixed by aligning the Fedora version with the upstream's.
Aligning with upstream would update tzdata itself, but dealing with the
compatibility issues
requires work that contradicts the claim of "easily fixed."
It is reasonable to infer that the untimeliness of tzdata-2018g-1 affects you
personally;
so why not fix it for yourself? rpmbuild is not that hard to grok.
Then you could report on the compatibility issues. You might even become a
maintainer :-)
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
