Uploaded ntp 4.0.98f-1 (sparc) to master
-----BEGIN PGP SIGNED MESSAGE-----
Format: 1.6
Date: Sat, 20 Nov 1999 23:51:34 -0700
Source: ntp
Binary: ntp-doc ntpdate ntp
Architecture: sparc
Version: 4.0.98f-1
Distribution: unstable
Urgency: low
Maintainer: Debian SPARC Build Daemon <buildd@marcus.debian.net>
Description:
ntp - Daemon and utilities for full NTP v4 timekeeping participation.
ntpdate - The ntpdate client for setting system time from NTP servers.
Closes: 12181 18723 26062 49877 50329 50462
Changes:
ntp (4.0.98f-1) unstable; urgency=low
.
* new upstream source, closes: #49877
* upstream maintainer uninterested in changing /tmp file usage, since there
is no clear problem with what is there, so no point in our keeping the
bug open... closes: #26062
* hardware clock handling is different in v4, and even more different if the
nanosecond timing patches are in use in the kernel. I think what ntp is
doing now is correct. closes: #12181
* I have never been able to reproduce the sigint failure during name
resolution reported ages ago, even when I worked hard to get slow name
service. I see no point in keeping the bug open. closes: #18723
* include ntpdate manpage from Fabrizio Polacco, closes: #50329
* include ntpd manpage from Peter Breuer, closes: #50462
* quick hack to see if we can fix the ntptimeval lossage in glibc2.0,
closes: 50433
Files:
9fa03a12d71b315e569a2efd83d5de19 265306 net optional ntp_4.0.98f-1_sparc.deb
c7134776993e2a0223bc2a73647bb574 56602 net optional ntpdate_4.0.98f-1_sparc.deb
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a
Charset: noconv
iQCVAwUBODqhLSo9WkFm9rsJAQEcFQP/R6K8b1DVByBMJUioLmjoEO1w663uoENX
In45AqJ3YqeoLBpLdkSrwUI1RD9O900nAamgeCdLqfvH+EQsFs3BPlD9udF2+Xqp
X3Cx9Vs45nTmVFqLMahp5N/laa37bPIL1UdrqM4isJNZ2zFQaw58R8N0o+X9pnGv
VX1aNuH6kUA=
=9gH1
-----END PGP SIGNATURE-----
Reply to: