On Sat, 2010-09-18 at 17:57 +0200, Bastian Blank wrote: > reopen 593683 > thanks > > On Sat, Sep 18, 2010 at 04:38:36PM +0100, Ben Hutchings wrote: > > On Thu, 2010-09-16 at 23:16 -0700, Steve Langasek wrote: > > > s390-tools, lilo, and elilo are the only bootloaders for which Breaks: > > > were > > > added in the recent upload. However, there are reports[1],[2] of serious > > > upgrade failures resulting from not upgrading grub before trying to > > > upgrade > > > the kernel; and the grub in lenny definitely does not comply with the new > > > kernel hooks policy (/etc/kernel/postinst.d/zz-update-grub only exists in > > > the squeeze versions). Is this an oversight, or is there some other > > > explanation for why grub was being left in an inconsistent state for these > > > users? > > > > Official kernel packages have never invoked GRUB except by running hook > > commands. > > Still they are incompatible. This is what breaks is for.
GRUB would always 'break' when a new kernel package was installed if the user or installer didn't set the hook command. There has been no incompatible change. > Also the other architectures are missing. No other architectures have an historical default boot loader that used to be run automatically. Ben. > > I think the release notes should encourage people to update their boot > > loader first. > > This is no replacement. > > Bastian > -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
signature.asc
Description: This is a digitally signed message part
