04.12.2009 в 16:27:03 +0100 Iustin Pop написал(а): > On Wed, Oct 07, 2009 at 08:44:39PM +0500, Stepan Golosunov wrote: > > Package: memtest86+ > > Version: 4.00-2 > > Severity: serious > > > > Upgrade to memtest86+ 4.00-2 fails: > > > > Preparing to replace memtest86+ 2.11-3 (using > > .../memtest86+_4.00-2_i386.deb) ... > > Unpacking replacement memtest86+ ... > > Updating /boot/grub/grub.cfg ... > > Found Debian background: moreblue-orbit-grub.png > > Found linux image: /boot/vmlinuz-2.6.26-2-amd64 > > Found initrd image: /boot/initrd.img-2.6.26-2-amd64 > > Found linux image: /boot/vmlinuz-2.6.26-1-amd64 > > Found initrd image: /boot/initrd.img-2.6.26-1-amd64 > > Found memtest86 image: /boot/memtest86.bin > > Found memtest86+ image: /boot/memtest86+.bin > > .: 4: Can't open /usr/lib/grub/grub-mkconfig_lib > > This is because you memtest86+ doesn't declare conflicts as it should, > and you have an older grub-pc: > > > ii grub-pc [grub] 1.96+20080724-16 GRand Unified Bootloader, > > version > > Basically the new file has been introduced into a newer version of > grub-pc. Patch adding conflicts attached.
> +Conflicts: grub-pc (<< 1.96+20090523-1), grub-common (<< 1.96+20090523-1) Won't it lead to accidental removal of bootloader? That would be a critical bug. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
