Bug#606107: [pkg-ntp-maintainers] Bug#606107: ntp: handle empty ntp.conf gracefully (working around system-tools-backends bug)

2010-12-09 Thread Peter Eisentraut
On ons, 2010-12-08 at 22:02 +, Colin Watson wrote: Can't system-tools-backends clean up the file that it had erroneously placed? It would have to be done in a system-tools-backends maintainer script. I'm not really sure why it's any better to do that in system-tools-backends vs. in

Bug#606107: [pkg-ntp-maintainers] Bug#606107: ntp: handle empty ntp.conf gracefully (working around system-tools-backends bug)

2010-12-09 Thread Colin Watson
On Thu, Dec 09, 2010 at 07:29:11PM +0200, Peter Eisentraut wrote: On ons, 2010-12-08 at 22:02 +, Colin Watson wrote: It would have to be done in a system-tools-backends maintainer script. I'm not really sure why it's any better to do that in system-tools-backends vs. in ntp;

Bug#606107: [pkg-ntp-maintainers] Bug#606107: ntp: handle empty ntp.conf gracefully (working around system-tools-backends bug)

2010-12-09 Thread Peter Eisentraut
On tor, 2010-12-09 at 17:55 +, Colin Watson wrote: I have no idea whether system-tools-backends is the only thing that might create an empty /etc/ntp.conf. I don't see how you can have any idea of that either? Well, if you want to account for that, then almost every package will have to

Bug#606107: [pkg-ntp-maintainers] Bug#606107: ntp: handle empty ntp.conf gracefully (working around system-tools-backends bug)

2010-12-08 Thread Colin Watson
On Tue, Dec 07, 2010 at 09:31:32PM +0200, Peter Eisentraut wrote: On mån, 2010-12-06 at 12:35 +, Colin Watson wrote: I entirely agree that this should be fixed in system-tools-backends, and I've sent a patch upstream (I'll copy this to the Debian bug shortly too). However, there are a

Bug#606107: [pkg-ntp-maintainers] Bug#606107: ntp: handle empty ntp.conf gracefully (working around system-tools-backends bug)

2010-12-08 Thread Peter Eisentraut
On ons, 2010-12-08 at 13:40 +, Colin Watson wrote: I don't really agree with these changes. An empty ntp.conf is an error and should not be masked. What useful information can this state possibly convey? That state that something is broken. Why not just fix the GNOME side and let

Bug#606107: [pkg-ntp-maintainers] Bug#606107: ntp: handle empty ntp.conf gracefully (working around system-tools-backends bug)

2010-12-08 Thread Colin Watson
On Wed, Dec 08, 2010 at 11:46:31PM +0200, Peter Eisentraut wrote: On ons, 2010-12-08 at 13:40 +, Colin Watson wrote: I don't really agree with these changes. An empty ntp.conf is an error and should not be masked. What useful information can this state possibly convey? That

Bug#606107: [pkg-ntp-maintainers] Bug#606107: ntp: handle empty ntp.conf gracefully (working around system-tools-backends bug)

2010-12-07 Thread Peter Eisentraut
On mån, 2010-12-06 at 12:35 +, Colin Watson wrote: I entirely agree that this should be fixed in system-tools-backends, and I've sent a patch upstream (I'll copy this to the Debian bug shortly too). However, there are a couple of fairly unintrusive things that could be changed in ntp to