Bug#436995: Incorrect values for root delay and dispersion

On -10/01/37 16:59, Juliusz Chroboczek wrote: > Package: openntpd > Version: 3.9p1-4 > Severity: important > > When acting as a server, OpenNTP sends replies with incorrect root > delay and dispersion values. Since both of these values are smaller > then they should be, this has the potential of c

Processing of ncpfs_2.2.6-8_amd64.changes

ncpfs_2.2.6-8_amd64.changes uploaded successfully to localhost along with the files: ncpfs_2.2.6-8.dsc ncpfs_2.2.6-8.debian.tar.bz2 ncpfs_2.2.6-8_amd64.deb ipx_2.2.6-8_amd64.deb libncp_2.2.6-8_amd64.deb libncp-dev_2.2.6-8_amd64.deb libpam-ncp_2.2.6-8_amd64.deb Greetings, You

ncpfs_2.2.6-8_amd64.changes ACCEPTED

Accepted: ipx_2.2.6-8_amd64.deb to main/n/ncpfs/ipx_2.2.6-8_amd64.deb libncp-dev_2.2.6-8_amd64.deb to main/n/ncpfs/libncp-dev_2.2.6-8_amd64.deb libncp_2.2.6-8_amd64.deb to main/n/ncpfs/libncp_2.2.6-8_amd64.deb libpam-ncp_2.2.6-8_amd64.deb to main/n/ncpfs/libpam-ncp_2.2.6-8_amd64.deb ncpf

Bug#580015: marked as done (ncpfs: FTBFS on ia64: sutil/ncpumount.c:353: undefined reference to `clone')

Your message dated Tue, 08 Jun 2010 09:40:34 + with message-id and subject line Bug#580015: fixed in ncpfs 2.2.6-8 has caused the Debian Bug report #580015, regarding ncpfs: FTBFS on ia64: sutil/ncpumount.c:353: undefined reference to `clone' to be marked as done. This means that you claim t

Processing of offlineimap_6.2.0.1_amd64.changes

offlineimap_6.2.0.1_amd64.changes uploaded successfully to localhost along with the files: offlineimap_6.2.0.1.dsc offlineimap_6.2.0.1.tar.gz offlineimap_6.2.0.1_all.deb Greetings, Your Debian queue daemon (running on host ries.debian.org) -- To UNSUBSCRIBE, email to debian-qa-pa

offlineimap_6.2.0.1_amd64.changes ACCEPTED

Accepted: offlineimap_6.2.0.1.dsc to main/o/offlineimap/offlineimap_6.2.0.1.dsc offlineimap_6.2.0.1.tar.gz to main/o/offlineimap/offlineimap_6.2.0.1.tar.gz offlineimap_6.2.0.1_all.deb to main/o/offlineimap/offlineimap_6.2.0.1_all.deb Override entries for your package: offlineimap_6.2.0.1

Processing of timidity_2.13.2-39_amd64.changes

timidity_2.13.2-39_amd64.changes uploaded successfully to localhost along with the files: timidity_2.13.2-39.dsc timidity_2.13.2-39.debian.tar.gz timidity-el_2.13.2-39_all.deb timidity-daemon_2.13.2-39_all.deb timidity_2.13.2-39_amd64.deb timidity-interfaces-extra_2.13.2-39_amd64.deb G

tepache 1.1-9 MIGRATED to testing

FYI: The status of the tepache source package in Debian's testing distribution has changed. Previous version: 1.1-8 Current version: 1.1-9 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive lat

timidity_2.13.2-39_amd64.changes ACCEPTED

Accepted: timidity-daemon_2.13.2-39_all.deb to main/t/timidity/timidity-daemon_2.13.2-39_all.deb timidity-el_2.13.2-39_all.deb to main/t/timidity/timidity-el_2.13.2-39_all.deb timidity-interfaces-extra_2.13.2-39_amd64.deb to main/t/timidity/timidity-interfaces-extra_2.13.2-39_amd64.deb tim

Bug#388301: marked as done (Sarge's openntpd includes /etc/openntpd/ntpd.conf but claims to include /etc/ntpd.conf)

Your message dated Tue, 08 Jun 2010 15:36:57 -0300 with message-id <4c0e8dc9.80...@debian.org> and subject line No longer on support has caused the Debian Bug report #388301, regarding Sarge's openntpd includes /etc/openntpd/ntpd.conf but claims to include /etc/ntpd.conf to be marked as done. Thi

Bug#468391: openntpd: can conflict with ntpdate

merge 330587 468391 thanks Hi Chris! I'm afraid what you see is not caused by any ntpdate conflict with openntpd, it's related to #330587. Basically, this is because ntpdate and openntpd uses different methods to achieve their goals, none of them collision or changes each other's behaviour. I'm

Processed: Re: openntpd: can conflict with ntpdate

Processing commands for cont...@bugs.debian.org: > merge 330587 468391 Bug#330587: openntpd: "adjtime failed: Invalid argument" Bug#468391: openntpd: can conflict with ntpdate Merged 330587 468391. > thanks Stopping processing here. Please contact me if you need assistance. -- 330587: http://bu

Bug#330587: bug still there

On -10/01/37 16:59, A Mennucc wrote: > Version: 3.9p1+debian-3 > > hi, > > a quick note to tell you that the bug is still there: > > Dec 30 13:59:04 frivolo ntpd[1321]: adjusting local clock by 5139.822192s > Dec 30 13:59:04 frivolo ntpd[1321]: adjtime failed: Invalid argument > Which kernel ar

Bug#521085: marked as done (openntpd: init.d-script should use pid file)

Your message dated Tue, 08 Jun 2010 21:42:42 + with message-id and subject line Bug#354825: fixed in openntpd 3.9p1+debian-4 has caused the Debian Bug report #354825, regarding openntpd: init.d-script should use pid file to be marked as done. This means that you claim that the problem has bee

Bug#554416: marked as done (openntpd: -p option refused by ntpd)

Your message dated Tue, 08 Jun 2010 21:42:42 + with message-id and subject line Bug#354825: fixed in openntpd 3.9p1+debian-4 has caused the Debian Bug report #354825, regarding openntpd: -p option refused by ntpd to be marked as done. This means that you claim that the problem has been dealt

Bug#354825: marked as done (Openntpd init script returns an error on shutdown.)

Your message dated Tue, 08 Jun 2010 21:42:42 + with message-id and subject line Bug#354825: fixed in openntpd 3.9p1+debian-4 has caused the Debian Bug report #354825, regarding Openntpd init script returns an error on shutdown. to be marked as done. This means that you claim that the problem

Bug#456661: marked as done (openntpd: No error message if servername is invalid)

Your message dated Tue, 08 Jun 2010 21:42:42 + with message-id and subject line Bug#456661: fixed in openntpd 3.9p1+debian-4 has caused the Debian Bug report #456661, regarding openntpd: No error message if servername is invalid to be marked as done. This means that you claim that the problem

Bug#437691: marked as done (openntpd: not handling nostrip build option (policy 10.1))

Your message dated Tue, 08 Jun 2010 21:42:42 + with message-id and subject line Bug#437691: fixed in openntpd 3.9p1+debian-4 has caused the Debian Bug report #437691, regarding openntpd: not handling nostrip build option (policy 10.1) to be marked as done. This means that you claim that the p

Bug#495528: marked as done (openntpd complains "invoke-rc.d called during shutdown sequence" during startup)

Your message dated Tue, 08 Jun 2010 21:42:42 + with message-id and subject line Bug#495528: fixed in openntpd 3.9p1+debian-4 has caused the Debian Bug report #495528, regarding openntpd complains "invoke-rc.d called during shutdown sequence" during startup to be marked as done. This means th

Bug#507586: marked as done (openntpd: ntpd starts before network is available)

Your message dated Tue, 08 Jun 2010 21:42:42 + with message-id and subject line Bug#507586: fixed in openntpd 3.9p1+debian-4 has caused the Debian Bug report #507586, regarding openntpd: ntpd starts before network is available to be marked as done. This means that you claim that the problem h

Bug#529984: marked as done (openntpd is restarted by /etc/network/if-up.d/openntpd even if not enabled)

Your message dated Tue, 08 Jun 2010 21:42:42 + with message-id and subject line Bug#529984: fixed in openntpd 3.9p1+debian-4 has caused the Debian Bug report #529984, regarding openntpd is restarted by /etc/network/if-up.d/openntpd even if not enabled to be marked as done. This means that yo

Bug#570253: marked as done (Server doesn't sync time when it is started)

Your message dated Tue, 08 Jun 2010 21:42:42 + with message-id and subject line Bug#570253: fixed in openntpd 3.9p1+debian-4 has caused the Debian Bug report #570253, regarding Server doesn't sync time when it is started to be marked as done. This means that you claim that the problem has bee

Bug#575705: marked as done (openntpd: ntpd.conf and its man page should be more explicit about the "listen" configuration)

Your message dated Tue, 08 Jun 2010 21:42:42 + with message-id and subject line Bug#575705: fixed in openntpd 3.9p1+debian-4 has caused the Debian Bug report #575705, regarding openntpd: ntpd.conf and its man page should be more explicit about the "listen" configuration to be marked as done.