On Tue, 12 Nov 2013 13:16:10 +0100 Ondřej Surý <ondrej@sury.org> wrote: > Hi, > > I am searching for a solution for this scenario: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621833 Generally, I avoid even trying to remove system users during package removal. Remove the files for that user but not the user itself. (What harm does it do to leave the user defined?) > 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? The old postinst sounds broken. Does the user removal succeed? If the user is currently active, it should fail - which could give you a way to prevent removal, assuming that the old postinst will handle that cleanly. Expected user intervention for this would be to reinstall the newer version of the package - the maintainer scrips should be able to cope in this situation by putting the system user back if the old package removed it. The application may need to also complain loudly if the required user does not exist, so that someone can tell what needs to be done to fix it. -- Neil Williams ============= http://www.linux.codehelp.co.uk/
Attachment:
signature.asc
Description: PGP signature