Bug#345934: Can not be installed: postinst fails

Package: linux-image-2.6.15-1-686 Version: 2.6.15-1 Severity: grave Setting up linux-image-2.6.15-1-686 (2.6.15-1) ... Running depmod. Finding valid ramdisk creators. Using mkinitrd.yaird to build the ramdisk. initrd.img(/boot/initrd.img-2.6.15-1-686) points to /boot/initrd.img-2.6.15-1-686 (/b

Bug#343093: Can't be purged

Package: linux-image-2.6.14-2-686 Version: 2.6.14-5 Severity: important # dpkg --purge linux-image-2.6.14-2-686 (Reading database ... 272041 files and directories currently installed.) Removing linux-image-2.6.14-2-686 ... Purging configuration files for linux-image-2.6.14-2-686 ... Searching for

Bug#343092: Do not configure

Package: linux-image-2.6.14-2-686 Version: 2.6.14-5 Severity: serious Reading package lists... Done Building dependency tree... Done Calculating upgrade... Done The following packages have been kept back: adplay dar extract gnome-cups-manager pstoedit sidplay 0 upgraded, 0 newly installed, 0 to

Bug#319357: Device 'vesafb0' does not have a release() function, it is broken and must be fixed.

Package: kernel-image-2.6.11-1-686 Version: 2.6.11-7 Severity: normal I get this same error message in every fscking boot and it looks this in kern.log: Jul 21 14:27:39 heresy kernel: Device 'vesafb0' does not have a release() function, it is broken and must be fixed. Jul 21 14:27:39 heresy ke