1 Feb 2007 06:54
Bug#409240: Kernel and initrd image symlinks aren't updated properly
Dennis Vshivkov <walrus <at> amur.ru>
2007-02-01 05:54:04 GMT
2007-02-01 05:54:04 GMT
Package: linux-2.6 Version: 2.6.18-7, 2.6.18.dfsg.1-9 Severity: important Attempting to install (ignore the fact that the .deb is from www.backports.org: the problem is clearly present in the latest versions in testing and unstable): # dpkg -i linux-image-2.6.18-3-k7_2.6.18-8~bpo.1_i386.deb Selecting previously deselected package linux-image-2.6.18-3-k7. (Reading database ... 118793 files and directories currently installed.) Unpacking linux-image-2.6.18-3-k7 (from .../linux-image-2.6.18-3-k7_2.6.18-8~bpo.1_i386.deb) ... Done. Setting up linux-image-2.6.18-3-k7 (2.6.18-8~bpo.1) ... Hmm. The package shipped with a symbolic link /lib/modules/2.6.18-3-k7/source However, I can not read the target: No such file or directory Therefore, I am deleting /lib/modules/2.6.18-3-k7/source Running depmod. Finding valid ramdisk creators. Using mkinitramfs-kpkg to build the ramdisk. initrd.img() points to (/boot/initrd.img-2.6.16-2-k7) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.18-3-k7.postinst line 585. vmlinuz() points to (/boot/vmlinuz-2.6.16-2-k7) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.18-3-k7.postinst line 585. Huh? I need symlinks properly updated, but they are not: # cat /etc/kernel-img.conf(Continue reading)
RSS Feed