Dear Ken,
> Dear Maintainer,
>
> I have started to receive errors such as the following:
>
> Jun 10 14:08:24 blackab3 ntpd[592]: leapsecond file
> ('/usr/share/zoneinfo/leap-seconds.list'): will expire in less than 18 days
>
> I tried to run update-leap to update the file, but received the following
> error:
>
> No leapfile directive in /etc/ntp.conf; leapfile location not known
>
> Looking in ntp.conf, I see the following:
>
> # Leap seconds definition provided by tzdata
> leapfile /usr/share/zoneinfo/leap-seconds.list
>
> I hand edited a test ntp.conf with just the setting (incase the file was
> corrupt), but it gave the error.
>
> Running the command with the direct option worked:
>
> update-leap -L /usr/share/zoneinfo/leap-seconds.list
>
> This is strange, the ntp.conf file appears correct - but it is not being read
> by update-leap.
update-leap is quite buggy, which is why we opted not to use it by
default and instead are using the leap-seconds.list definition shipped
by tzdata.
https://tracker.debian.org/pkg/tzdata
tzdata 2020a-1 containing a leap-seconds.list valid until End of
December is already in sid, bullseye and buster-proposed /
stretch-proposed. As soon as the next stable release happens ntp will
automatically use the updated leap seconds file.
Bernhard
