Bug#395223: leaves .bak files around after kernel purge, and chokes on them

[maximilian attems <maks@sternwelten.at>]

retitle 395223 add a postrm hook to specific linux-image for initrd sha1sum
severity 395223 minor
stop

On Wed, 25 Oct 2006, martin f krafft wrote:

> I had just purged linux-image-2.6.17-2-686 from the system. First,
> the initrd.bak file was left over, and second: initramfs-tools
> apparently honours that file when I say -k all:

newer kernel-package removes the .bak file on postrm of linux-image.

> mdadmp:~# update-initramfs -u -k all
> update-initramfs: Generating /boot/initrd.img-2.6.18-1-686
> I: mdadm: using configuration file: /etc/mdadm/mdadm.conf
> I: mdadm: will start all available MD arrays from the initial ramdisk.
> I: mdadm: use `dpkg-reconfigure --priority=low mdadm` to change this.
> sha1sum: /boot/initrd.img-2.6.17-2-686: No such file or directory
> /boot/initrd.img-2.6.17-2-686 has been altered.  Cannot update.

the warning is meaningless as update-initramfs will try the other images
anyway.
this is due to the existence of a sha1sum in /var/lib/initramfs-tools
corresponding to 2.6.17-2-686 and has nothing to do with the .bak.
postetch there will be the possibility to record a postremoval hook
for it in kernel-package for now that's admin work.

best regards

-- 
maks