leap_second.list not updated after latest IERS Bulletin C
Dear IANA Timezone People, The latest leap_seconds.lst file you provide here: https://data.iana.org/time-zones/tzdb/leap-seconds.list and the other related files were last updated 2023-03-28. The leap second table has an expiry date of 2023-12-28, which is rapidly approaching. There is IERS Bulletin C from 2023-07-04 announcing no new leap second on 2023-12-31, so the expiry date of the list can be updated to 2023-06-28. Kind regards Maximilian Linhoff -- Dr. Maximilian Linhoff PostDoc Astroteilchenphysik Technische Universität Dortmund Fakultät Physik / Astroteilchenphysik Otto-Hahn-Str. 4a 44227 Dortmund Tel.: +49 231 755 8895 maximilian.linhoff@tu-dortmund.de https://app.tu-dortmund.de
On 2023-12-06 05:22, Maximilian Linhoff via tz wrote:
There is IERS Bulletin C from 2023-07-04 announcing no new leap second on 2023-12-31 That's been installed in the development repository here:
https://raw.githubusercontent.com/eggert/tz/main/leap-seconds.list Is there some reason we need a new TZDB release because of this? Do you use software that requires that this file come from a TZDB release, rather than from other sources such as the one mentioned above? I recall that traditionally ntpd needed leap-seconds.list and looked at the expiration but am not up to date with what its successor NTPsec is doing. chrony does not currently use leap-seconds.list - and although this has been proposed for a future release, that proposal does not look at the expiration; see: https://www.mail-archive.com/chrony-dev@chrony.tuxfamily.org/msg02727.html
Dear Paul, Astropy uses the file at the URL I mentioned as a fallback for obtaining leap second information: https://www.astropy.org/ Cheers Max On 07.12.23 20:52, Paul Eggert wrote:
On 2023-12-06 05:22, Maximilian Linhoff via tz wrote:
There is IERS Bulletin C from 2023-07-04 announcing no new leap second on 2023-12-31 That's been installed in the development repository here:
https://raw.githubusercontent.com/eggert/tz/main/leap-seconds.list
Is there some reason we need a new TZDB release because of this? Do you use software that requires that this file come from a TZDB release, rather than from other sources such as the one mentioned above?
I recall that traditionally ntpd needed leap-seconds.list and looked at the expiration but am not up to date with what its successor NTPsec is doing. chrony does not currently use leap-seconds.list - and although this has been proposed for a future release, that proposal does not look at the expiration; see:
https://www.mail-archive.com/chrony-dev@chrony.tuxfamily.org/msg02727.html
-- Dr. Maximilian Linhoff PostDoc Astroteilchenphysik Technische Universität Dortmund Fakultät Physik / Astroteilchenphysik Otto-Hahn-Str. 4a 44227 Dortmund Tel.: +49 231 755 8895 maximilian.linhoff@tu-dortmund.de https://app.tu-dortmund.de
participants (2)
-
Maximilian Linhoff -
Paul Eggert