[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Dead-lock in replaced package scripts



Hi,

On Tue, 12 Nov 2013, Ondřej Surý wrote:
> On Tue, Nov 12, 2013, at 13:55, Peter Palfrader wrote:
> > On Tue, 12 Nov 2013, Ondřej Surý wrote:
> > 
> > > Now the "nsd" user has been removed in nsd3.postinst, but it is still
> > > needed by nsd (>= 4.0.0) package. Any ideas how to fix that? Or should I
> > > just cross the fingers and hope nobody would do such thing?
> > 
> > You probably shouldn't ever remove users.
> 
> That's very nice answer, but not very helpful, since it doesn't address
> my question.

You don't have many options.

You can check the status of the nsd3 package when you install/upgrade nsd
and emit a warning pointing to some README.Debian that explains how to
clean up the situation (or you can do it automatically, it's not very
clean but should be rather straightforward).

Or you can add a dependency on nsd3 (>= 4) to nsd for the time of a
release cycle, thus forcing the user to keep a dummy package around.

In any case, I would still fix the nsd package to not remove the user on
postrm...

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Discover the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/


Reply to: