* Joachim Wiedorn <ad_debian@joonet.de> [Mon Dec 13, 2010 at 04:00:04PM +0100]: > Michael Prokop <mika@debian.org> wrote on 2010-12-13 11:11: > > Now version 1:22.8-9 introduces: > > Conflicts: grub-legacy, grub-pc > > I don't see any reason why this should be enforced, actually this > > avoids deployments of systems where users can choose between lilo > > and grub as bootloader as both can't be distributed at the same time > > with the conflicts mentioned above. > To manage newer kernel in Debian the system need hook scripts for kernel > and initrd which can be found in /etc/kernel and /etc/initramfs/. These > hook scripts will always be executed after kernel update or initrd update. > If more then one bootloader is installed, each bootloader (say: grub- > legacy, grub-pc or others) will try to install his code into MBR while > kernel or initrd will be updated. This is not usefull. update-grub just generates the grub.cfg, the lilo package doesn't execute lilo (and therefore doesn't touch MBR) as long as there's no /etc/lilo.conf. So both packages can and do co-exist. > > IMO this is a bug that shouldn't reach squeeze, therefore choosing > > severity serious. > I think these defined "Conflicts" does not break the regular functionality > of a Debian system, It breaks existing deployment environments. > but provide clarification, which bootloader make the work. So the > severity should be minor. Drop the conflicts in the lilo package and everything will continue to work as it used to? regards, -mika-
Attachment:
signature.asc
Description: Digital signature