Package: spikeproxy Version: 1.4.7-9 Severity: important spikeproxy postrm script fails if the CACHEDIR=/var/cache/spikeproxy is already removed.This behavior can be reproduced by apt-get remove spikeproxy and then do dpkg --purge spikeproxy or simply deleting or renaming /var/cache/spikeproxy directory.
The users would be able to remove the package but I guess can't purge it. $ apt-get remove spikeproxy Reading package lists... Done Building dependency tree... Done The following packages will be REMOVED: spikeproxy 0 upgraded, 0 newly installed, 1 to remove and 9 not upgraded. Need to get 0B of archives. After unpacking 14.5MB disk space will be freed. Do you want to continue [Y/n]? y (Reading database ... 102038 files and directories currently installed.) Removing spikeproxy ... $ dpkg --purge spikeproxy (Reading database ... 98779 files and directories currently installed.) Removing spikeproxy ... Purging configuration files for spikeproxy ... dpkg: error processing spikeproxy (--purge): subprocess post-removal script returned error exit status 1 Errors were encountered while processing: spikeproxy NB:Please fix this minor thing, I thinks its not worth filing a bug against it. WARNING: The following packages cannot be authenticated! spikeproxy Install these packages without verification [y/N]? y -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i586) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.18-1-k6 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages spikeproxy depends on: ii python 2.3.5-3 An interactive high-level object-o ii python-pyopenssl 0.6-2 Python wrapper around the OpenSSL spikeproxy recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
