On Fri, Dec 04, 2009 at 10:09:02PM +0400, Stepan Golosunov wrote: > 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.
Since it doesn't "Replace" the grub-pc/grub-common packages, I won't remove the package without confirmation - but it indeed will prompt the user for removal. In other words: - apt-get upgrade/dist-upgrade won't select the new memtest86+ version - but an explicit "apt-get install memtest86+" will prompt for removal of grub-pc The policy says that “A Conflicts entry should almost never have an "earlier than" version clause”, and recommends ‘Breaks’ instead, but breaks doesn't work here properly. And we can't depend either on a newer grub version, since memtest86+ technically doesn't "depend" on grub. This is the only possibilty that I see if we want to just modify package relationships; the other option would be to modify the grub script provided by memtest86+ to not do anything if we don't find the required files (which works for /usr/lib/grub/grub-mkconfig_lib, but it's harder to do for the linux16 support). So, I don't see a clear way to make this all work nicely. Any suggestions? thanks! iustin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
