Your message dated Fri, 20 Nov 2020 16:16:53 +0100
with message-id <20201120151653.gi2...@aurel32.net>
and subject line Re: Bug#975311: tzdata: /usr/share/zoneinfo/leap-seconds.list
[ IERS Bulletin C59 ] expires on 28 December 2020
has caused the Debian Bug report #975311,
regarding tzdata: /usr/share/zoneinfo/leap-seconds.list [ IERS Bulletin C59 ]
expires on 28 December 2020
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
975311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tzdata
Version: 2020a-0+deb10u1
Severity: normal
Tags: upstream
Dear Maintainer,
* What led up to the situation?
Checking the out of systemctl status ntp.service after restart of an
Debian 10 system with NTPd running
* What exactly did you do (or not do) that was effective (or
ineffective)?
systemctl stop ntp.service
systemctl start ntp.service
systemctl status ntp.service
view /usr/share/zoneinfo/leap-seconds.list
* What was the outcome of this action?
Nov 11 20:18:05 myhostname ntpd[11542]: leapsecond file
('/usr/share/zoneinfo/leap-seconds.list'): good hash signature
Nov 11 20:18:05 myhostname ntpd[11542]: leapsecond file
('/usr/share/zoneinfo/leap-seconds.list'): loaded,
expire=2020-12-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=3
/usr/share/zoneinfo/leap-seconds.list [ IERS Bulletin C59 ] expires on
28 December 2020
[...]
# Updated through IERS Bulletin C59
# File expires on: 28 December 2020
[...]
* What outcome did you expect instead?
Please refer to the new version C60:
https://www.iers.org/IERS/EN/Publications/Bulletins/bulletins.html
The leap second file is recommended to be used in a valid version:
See for example
https://kb.meinbergglobal.com/kb/time_sync/ntp/configuration/ntp_leap_second_file#expiration_date
/usr/share/zoneinfo/leap-seconds.list refering to IERS Bulletin C Number
60
If the impact of an invalid leap-seconds.list on ntp clients and server
is known as more severe
please change the severity to level 3 (serious).
Thank you in adance.
Best Regards
Jens
-- System Information:
Debian Release: 10.6
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-12-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages tzdata depends on:
ii debconf [debconf-2.0] 1.5.71
tzdata recommends no packages.
tzdata suggests no packages.
-- debconf information:
tzdata/Zones/Africa:
tzdata/Zones/SystemV:
tzdata/Zones/America:
* tzdata/Areas: Europe
* tzdata/Zones/Europe: Berlin
tzdata/Zones/Australia:
tzdata/Zones/Asia:
tzdata/Zones/Atlantic:
tzdata/Zones/US:
tzdata/Zones/Antarctica:
tzdata/Zones/Pacific:
tzdata/Zones/Arctic:
tzdata/Zones/Indian:
* tzdata/Zones/Etc: UTC
--- End Message ---
--- Begin Message ---
Version: 2020b-0+deb10u1
Hi,
On 2020-11-20 11:41, j...@abromeit.info wrote:
> Package: tzdata
> Version: 2020a-0+deb10u1
> Severity: normal
> Tags: upstream
>
> Dear Maintainer,
>
> * What led up to the situation?
>
> Checking the out of systemctl status ntp.service after restart of an Debian
> 10 system with NTPd running
>
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
>
> systemctl stop ntp.service
> systemctl start ntp.service
> systemctl status ntp.service
> view /usr/share/zoneinfo/leap-seconds.list
>
> * What was the outcome of this action?
>
> Nov 11 20:18:05 myhostname ntpd[11542]: leapsecond file
> ('/usr/share/zoneinfo/leap-seconds.list'): good hash signature
> Nov 11 20:18:05 myhostname ntpd[11542]: leapsecond file
> ('/usr/share/zoneinfo/leap-seconds.list'): loaded,
> expire=2020-12-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=3
>
> /usr/share/zoneinfo/leap-seconds.list [ IERS Bulletin C59 ] expires on 28
> December 2020
> [...]
> # Updated through IERS Bulletin C59
> # File expires on: 28 December 2020
> [...]
>
> * What outcome did you expect instead?
>
> Please refer to the new version C60:
> https://www.iers.org/IERS/EN/Publications/Bulletins/bulletins.html
>
> The leap second file is recommended to be used in a valid version:
> See for example
> https://kb.meinbergglobal.com/kb/time_sync/ntp/configuration/ntp_leap_second_file#expiration_date
>
> /usr/share/zoneinfo/leap-seconds.list refering to IERS Bulletin C Number 60
>
> If the impact of an invalid leap-seconds.list on ntp clients and server is
> known as more severe
> please change the severity to level 3 (serious).
Please upgrade to tzdata 2020b-0+deb10u1 or later, available through
stable-updates. It already contains a leap second list updated to IERS
Bulletin C Number 60.
Regards,
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
--- End Message ---
