Your message dated Sat, 8 Sep 2018 00:44:36 +0200
with message-id <[email protected]>
and subject line Closing
has caused the Debian Bug report #680979,
regarding ntpdate doesn't deal well with the future
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 [email protected]
immediately.)
--
680979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680979
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ntpdate
Version: 1:4.2.6.p5+dfsg-2
Severity: normal
Dear Maintainer,
consider this session:
# date -s "jul 9, 2131"
Mo 9. Jul 00:00:00 EDT 2131
# ntpdate ntp1.ptb.de
15 Aug 20:01:08 ntpdate[31400]: step time server 192.53.103.108 offset
539812826.581089 sec
After this, the current system time is in the year 2148, which is not
quite the desired effect. :)
Andreas
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.4-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages ntpdate depends on:
ii dpkg 1.16.4.3
ii libc6 2.13-33
ii libssl1.0.0 1.0.1c-3
ii netbase 5.0
Versions of packages ntpdate recommends:
pn lockfile-progs <none>
ntpdate suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
As explained, it's a protocol limitation, not a bug in ntpdate. Closing.
--- End Message ---
