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.
iustin
diff -urN memtest86+-4.00.old/debian/control memtest86+-4.00/debian/control
--- memtest86+-4.00.old/debian/control 2009-12-04 16:22:11.000000000 +0100
+++ memtest86+-4.00/debian/control 2009-12-04 16:22:59.330820451 +0100
@@ -9,7 +9,8 @@
Package: memtest86+
Architecture: i386 amd64 kfreebsd-i386 kfreebsd-amd64 lpia hurd-i386
Depends: ${misc:Depends}
-Suggests: hwtools, memtester, kernel-patch-badram, memtest86, grub2 (>=1.95+20070515-1) | grub (>= 0.95+cvs20040624), mtools
+Suggests: hwtools, memtester, kernel-patch-badram, memtest86, grub2 (>=1.96+20090523-1) | grub (>= 0.95+cvs20040624), mtools
+Conflicts: grub-pc (<< 1.96+20090523-1), grub-common (<< 1.96+20090523-1)
Description: thorough real-mode memory tester
Memtest86+ scans your RAM for errors.
.
