Hello, I am using https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list, which looked like it is still working just now. Kind regards, PoolMUC "vom513" vom...@gmail.com – 29. October 2023 16:05
> * Sorry for the Subject: gore... > Hello all, > So last night cron.weekly ran on all my boxes, and update-leap failed on > most of them. I’m using the distro package on all of these. > Here is what I discovered: > Older machine - Ubuntu 16.04. update-leap script is 1.003. This > version uses File::Fetch and thus supports FTP. My LEAPSRC URI on this > machine is: > >> ftp://ftp.boulder.nist.gov/pub/time/leap-seconds.list > > This machine worked fine, pulled a new version. > My newer machines (ex: Debian 11) - they all failed. They have > update-leap version 1.004 which seems to have dropped File::Fetch in > favor of an HTTP(S) only module/transport. LEAPSRC on these is: > >> https://www.ietf.org/timezones/data/leap-seconds.list > > Hah ! As I was typing this message, it looks like the output changed > from a 404 to: > >> ietf.org is no longer serving this file. > > So, what’s an HTTP(S) URI I can use now since the newer version of this > script doesn’t support FTP ? > And yes I know I can manually update this file etc. Just wanting to get > things fixed properly so they run smoothly in an automatic fashion as > they have for quite some time… > Thanks.
