Bug#535331: 2.6.26-17lenny2 => 2.6.26-19 OK, 2.6.26-19 => 2.6.26-19lenny1 NOT OK

[Bjørn Mork <bjorn@mork.no>]

Just to add another data point, lilo failed to run again for me too on
the 2.6.26-19lenny1 upgrade.  Even after working on the previous kernel
upgrade!  

I'm now totally lost wrt what triggers this bug...


To summarize:

2.6.26-17lenny2 =>  2.6.26-19  
  lilo OK

2.6.26-19 => 2.6.26-19lenny1
  lilo not running


There were no changes to neither initramfs-tools nor /etc/kernel-img.conf 
between these upgrades.  My /etc/kernel-img.conf is still

 adler:/tmp# cat /etc/kernel-img.conf 
 # Kernel Image management overrides
 # See kernel-img.conf(5) for details
 do_symlinks = Yes
 do_initrd = Yes
 do_bootloader = yes


The upgrade log is shorter, and the shortage is of course the problem:

 Setting up linux-image-2.6.26-2-686 (2.6.26-19lenny1) ...
 Running depmod.
 Running mkinitramfs-kpkg.
 Not updating initrd symbolic links since we are being updated/reinstalled 
 (2.6.26-19 was configured last, according to dpkg)
 Not updating image symbolic links since we are being updated/reinstalled 
 (2.6.26-19 was configured last, according to dpkg)
 Setting up linux-libc-dev (2.6.26-19lenny1) ...

(nothing more)

At this point, the previous upgrade continued with 
"update-initramfs: deferring update (trigger activated)"
so maybe this is some trigger-related problem?  I do however note that
the initrd.img is updated, even though the message
"update-initramfs: Generating /boot/initrd.img-2.6.26-2-686"
also is missing.

Any clues are appreciated.  It's a real hassle to have to log in to each
and every server and manually run lilo after each kernel security
update, or risk dead servers on the next reboot.


Bjørn