Control: severity 683061 serious First of all something clearly is broken. The immediately visible symptom is that ntp does not synchronize time at all. If you believe that ntp is not the cause, then the course to take is not to downgrade the severity, but to ask for further information or reassign the problem report to the package causing the breakage. Hiding issues like you tried to do harms the Debian project.
On Sun, Aug 26, 2012 at 10:20:16PM +0200, Kurt Roeckx wrote: > Ntp should work correctly if nothing else is broken about > the dns setup. Please clarify this. If the DNS server does not respond to queries, because it is only started after ntp, does that constitute a breakage in the DNS server? If ntp then fails to resolve debian.pool.ntp.org and fails to repeat that atfer the DNS server is started thus failing to synchronize time at all, is that a bug in ntp? Another way to resolve this issue would be adding $named to Should-Start (instead of Required-Start). Would that be something you can live with? Helmut -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
