Hi! On Thu, 2010-02-25 at 13:27:42 -0500, Stephen Powell wrote: > Package: dpkg > Version: 1.15.5.6
> Thus, symlink_hook is executed third and last. The script appears to work > correctly and to exit with a return status of 0. However, I still get > an error from dpkg when I purge the package. > I found three other bug reports with this search: 560181, 534648, and 541275. > All these bug reports were against other packages (wwwoffle, wicd, and > ca-certificates, respectively). However, in each case the respective package > had a postrm script that was returning a non-zero exit status. In my case, > I am certain that my script is returning a zero exit status. > Therefore, I am filing this bug report against dpkg itself. > debian3:~# dpkg --purge linux-image-2.6.32-trunk-s390x > (Reading database ... 25193 files and directories currently installed.) > Removing linux-image-2.6.32-trunk-s390x ... > Purging configuration files for linux-image-2.6.32-trunk-s390x ... > Examining /etc/kernel/postrm.d . > run-parts: executing /etc/kernel/postrm.d/initramfs 2.6.32-trunk-s390x > /boot/vmlinuz-2.6.32-trunk-s390x > Cannot delete /boot/initrd.img-2.6.32-trunk-s390x, doesn't exist. > run-parts: executing /etc/kernel/postrm.d/initramfs-tools 2.6.32-trunk-s390x > /boot/vmlinuz-2.6.32-trunk-s390x > run-parts: executing /etc/kernel/postrm.d/symlink_hook 2.6.32-trunk-s390x > /boot/vmlinuz-2.6.32-trunk-s390x [...] > + exit 0 > dpkg: error processing linux-image-2.6.32-trunk-s390x (--purge): > subprocess installed post-removal script returned error exit status 128 > Errors were encountered while processing: > linux-image-2.6.32-trunk-s390x > debian3:~# The fact that the hook returns with 0 does not mean that the maintainer script or any of its childs is returning with 0, which is what's happening here, try using 'set -x' on the maintainer script itself and see what happens. Anyway, I doubt this is a problem in dpkg itself, but let's see. thanks, guillem -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
