[Piuparts-commits] [SCM] piuparts git repository branch, piatti, updated. 0.44-632-gd048446

[Andreas Beckmann]

The following commit has been merged in the piatti branch:
commit a142fd9a7167877627323c6e30d567b8948f5c19
Author: Andreas Beckmann <debian at abeckmann.de>
Date:   Wed Apr 4 21:32:57 2012 +0200

    deluser-not-found: add more details to description
    
    add link to the discussion about not removing system users on
    package removal
    
    Signed-off-by: Andreas Beckmann <debian at abeckmann.de>

diff --git a/org/piuparts.debian.org/htdocs/templates/mail/fails_to_purge_-_command_deluser_adduser_in_postrm_not_found.mail b/org/piuparts.debian.org/htdocs/templates/mail/fails_to_purge_-_command_deluser_adduser_in_postrm_not_found.mail
index 620f640..f52f61a 100644
--- a/org/piuparts.debian.org/htdocs/templates/mail/fails_to_purge_-_command_deluser_adduser_in_postrm_not_found.mail
+++ b/org/piuparts.debian.org/htdocs/templates/mail/fails_to_purge_-_command_deluser_adduser_in_postrm_not_found.mail
@@ -16,7 +16,17 @@ available for sure.
 
 The fix should be easy: your package is using adduser or deluser from
 the adduser package, which is only priority important. Using useradd or
-userdel from the passwd package should fix this problem.
+userdel from the passwd package (priority required) should fix this
+problem.
+
+There is ongoing discussion how to handle system users on package
+removal, see http://bugs.debian.org/621833
+Consensus seems to be not to remove system users (to avoid reusing UIDs
+which could grant access to the wrong files) but to "lock" them (where
+"locking"/"unlocking" is not yet precisely defined). Until that has
+been decided it should be sufficient to have the postrm script ignore
+any errors from deluser:
+  deluser ... || true
 
 Filing this as important because a.) it's a clear policy violation (to
 not clean up at purge) b.) having a piuparts clean archive is a release

-- 
piuparts git repository