[pkg-ntp-maintainers] Bug#478655: Bug#478655: ntp: other solution

Kurt Roeckx kurt at roeckx.be
Thu May 1 15:23:03 UTC 2008


On Thu, May 01, 2008 at 06:52:00PM +0400, Vladimir Stavrinov wrote:
> 
> On Thu, May 01, 2008 at 02:47:45PM +0200, Kurt Roeckx wrote:
> 
> > It's a conffile, so if you make changes to it, it will be asked what you
> > want to do.
> 
> I know this. But if upgrade is automated (as it is in my case)
> this cause creation lot of *.dpkg-dist files that should be then
> revised to edit old conf files. There is good practice used by
> many honor package maintainers to separate config supplied by
> package from user config.
> 
> > Which has nothing to do with his problem.
> 
> With -u option ntpdate-debian return zero and script
> /etc/network/if-up.d/ntpdate will not be interrupted.

Even with the -u option it can return a non-zero state.  Even if it
fixes the problem in some case, it's just a workaround for the real
problem that the lock file doesn't get removed in the error case.

> There was no problem with port for me never before as soon as I
> am using -u option. But if You want to solve some problem You
> should not do this by replacing old problem with new problem.
> This is wrong way of upgrade.

I have no idea what you mean with "new problem".  On the next upgrade
the script should be fixed.  The problem is that the lockfile doesn't
get removed in the error case while it should.  With his change it
should properly remove it.

So that would only leave the files left that dpkg might have created
because the conffile was changed, which I really don't consider a
problem.  


Kurt






More information about the pkg-ntp-maintainers mailing list