Package: pagure Version: 5.11.3+dfsg-1 Severity: serious https://piuparts.debian.org/sid/fail/pagure_5.11.3+dfsg-2.log
... Purging configuration files for pagure (5.11.3+dfsg-2) ... /var/lib/dpkg/info/pagure.postrm: 22: deluser: not found dpkg: error processing package pagure (--purge): installed pagure package post-removal script subprocess returned error exit status 127 Errors were encountered while processing: pagure 0m58.6s ERROR: Command failed (status=1): ['chroot', '/srv/piuparts.debian.org/tmp/tmpemwrio1i', 'dpkg', '--purge', 'pagure'] (Reading database ... 8052 files and directories currently installed.) Purging configuration files for pagure (5.11.3+dfsg-2) ... /var/lib/dpkg/info/pagure.postrm: 22: deluser: not found dpkg: error processing package pagure (--purge): installed pagure package post-removal script subprocess returned error exit status 127 Errors were encountered while processing: pagure https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#summary-of-ways-maintainer-scripts-are-called The postrm script is called after the package’s files have been removed or replaced. The package whose postrm is being called may have previously been deconfigured and only be “Unpacked”, at which point subsequent package changes do not consider its dependencies. Therefore, all postrm actions must only rely on essential packages and must gracefully skip any actions that require the package’s dependencies if those dependencies are unavailable.
