Package: tcpcryptd Version: 0.5-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts
Hi, during a test with piuparts I noticed your package failed to purge due to a command not found. According to policy 7.2 you cannot rely on the depends being available during purge, only the essential packages are 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 (priority required) should fix this problem. There is ongoing discussion how to handle system users on package removal, see https://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 >From the attached log (scroll to the bottom...): 0m17.5s DEBUG: Starting command: ['chroot', '/srv/piuparts.debian.org/tmp/tmp8wigy40m', 'dpkg', '--purge', 'tcpcryptd'] 0m17.5s DUMP: (Reading database ... 8066 files and directories currently installed.) Purging configuration files for tcpcryptd (0.5-1+b3) ... /var/lib/dpkg/info/tcpcryptd.postrm: 9: deluser: not found dpkg: error processing package tcpcryptd (--purge): installed tcpcryptd package post-removal script subprocess returned error exit status 127 Errors were encountered while processing: tcpcryptd 0m17.5s ERROR: Command failed (status=1): ['chroot', '/srv/piuparts.debian.org/tmp/tmp8wigy40m', 'dpkg', '--purge', 'tcpcryptd'] cheers, Andreas
tcpcryptd_0.5-1+b3.log.gz
Description: application/gzip