Bug#400544: Found in 2.6.18-7, again

[Adam Majer <adamm@zombino.com>]

found 400544 2.6.18-7
thanks

Was fixed in -6, but broken again in -7!


polaris:~# dpkg -i linux-image-2.6.18-3-vserver-k7_2.6.18-7_i386.deb
(Reading database ... 55452 files and directories currently installed.)
Preparing to replace linux-image-2.6.18-3-vserver-k7 2.6.18-6 (using
linux-image-2.6.18-3-vserver-k7_2.6.18-7_i386.deb) ...
The directory /lib/modules/2.6.18-3-vserver-k7 still exists. Continuing
as directed.
Done.
Unpacking replacement linux-image-2.6.18-3-vserver-k7 ...
Setting up linux-image-2.6.18-3-vserver-k7 (2.6.18-7) ...

 Hmm. The package shipped with a symbolic link
/lib/modules/2.6.18-3-vserver-k7/source
 However, I can not read the target: No such file or directory
 Therefore, I am deleting /lib/modules/2.6.18-3-vserver-k7/source

Running depmod.
Finding valid ramdisk creators.
Using mkinitrd.yaird to build the ramdisk.
yaird warning: consider upgrading to mdadm 2.2 or newer to support
changes in device boot ordering
readlink: invalid option -- m
Try `readlink --help' for more information.
readlink: invalid option -- m
Try `readlink --help' for more information.
Failed to symbolic-link initrd.img-2.6.18-3-vserver-k7 to initrd.img.
dpkg: error processing linux-image-2.6.18-3-vserver-k7 (--install):
 subprocess post-installation script returned error exit status 17
Errors were encountered while processing:
 linux-image-2.6.18-3-vserver-k7