Package: afterstep Version: 2.1.1-2 afterstep's postrm script calls ucf when purging. Unfortunately, Policy (section 7.2, "Binary Dependencies...") forbids relying on non-essential tools. Others have been bitten with this, too, and have used ucf when available, falling back on plain rm when not.
The relevant piuparts[1] log snippet: 0m41.2s DEBUG: Starting command: chroot ./tmp43c21l dpkg --purge afterstep 0m41.2s DUMP: (Reading database ... 7432 files and directories currently installed.) 0m41.2s DUMP: Removing afterstep ... 0m41.2s DUMP: Purging configuration files for afterstep ... 0m41.2s DUMP: /var/lib/dpkg/info/afterstep.postrm: line 14: ucf: command not found 0m41.2s DUMP: dpkg: error processing afterstep (--purge): 0m41.2s DUMP: subprocess post-removal script returned error exit status 127 0m41.2s DUMP: Errors were encountered while processing: 0m41.2s DUMP: afterstep 0m41.2s DEBUG: Command failed (status=256), but ignoring error: 'chroot ./tmp43c21l dpkg --purge afterstep' [1] See http://packages.debian.org/unstable/devel/piuparts -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
