On 2026-10-16 15:32, Paul Eggert via tz wrote:
In addition to the ntp bug report I mentioned previously, I also filed bug
reports about leap-second table expiry against chrony[1], linuxptp[2],
SuperNOVAS[3], Astropy[4], and ntpsec[5]. I did not file one against
leapseconddata as that project seems to be defunct.
The fact that all this software wants expiration dates indicates that the leap-
second table should still have one, at least during a transition period.
[1]: https://gitlab.com/chrony/chrony/-/work_items/49
[2]: https://lists.nwtime.org/sympa/arc/linuxptp-users/2026-10/msg00001.html
[3]: https://github.com/Sigmyne/SuperNOVAS/issues/392
[4]: https://github.com/astropy/astropy/issues/20632
[5]: https://gitlab.com/NTPsec/ntpsec/-/work_items/901
Should not be an issue if expiry is set to 2999-12-31 or 9999-12-31, if the
resolution to drop leap seconds ever passes:
2999 Dec 31 Tue 23:59:59+0000 NTP 34712668799 Unix 32503679999
JD 2816787.49999 MJD 416786.99999
9999 Dec 31 Fri 23:59:59+0000 NTP 255611289599 Unix 253402300799
JD 5373484.49999 MJD 2973483.99999
Someone is going to non-concur and if there is any opposition group, it may
never be dropped, as in all previous attempts to do so!
It is likely the USA and China may support Russia on Glonass issues to bolster
their own objectives, possibly also some EU dissenters with that alignment?
Non-solar timekeeping is a legal quagmire in English common-law jurisdictions,
and may also be with religious regimes, so is likely to become a political
issue, making it remotely possible that tzdb may have to track jurisdictions
that have dropped/still use leap seconds, similar to DST, just as some are
starting to drop that!
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher but when there is no more to cut
-- Antoine de Saint-Exupéry