[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#593683: marked as done (linux-2.6 - images does not conflict with pre-policy versions of bootloaders)

Your message dated Sat, 18 Sep 2010 16:38:36 +0100
with message-id <1284824317.5879.251.camel@localhost>
and subject line Re: Bug#593683: linux-2.6 - images does not conflict with pre-policy versions of bootloaders
has caused the Debian Bug report #593683,
regarding linux-2.6 - images does not conflict with pre-policy versions of bootloaders
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
593683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593683
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-2.6
Version: 2.6.32-18
Severity: grave

The images have to conflict against versions of the bootloaders not
supporting installation on its own.

Bastian

-- 
Violence in reality is quite different from theory.
		-- Spock, "The Cloud Minders", stardate 5818.4

--- End Message ---
--- Begin Message --- 
On Thu, 2010-09-16 at 23:16 -0700, Steve Langasek wrote:
> reopen 593683
> thanks
> 
> Hi guys,
> 
> 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.  The installer used to set postinst_hook and postrm_hook in
/etc/kernel-img.conf to run update-grub, and the official kernel
packages still call those hooks.  I can only assume that these users
installed grub later and did not set the hooks, so their GRUB menus were
*never* updated.

> (Reopening the bug out of an abundance of caution; if lenny grub really
> doesn't need to be added to the Breaks, please close again - but please also
> let me know why, so we can write the release notes appropriately.)

I think the release notes should encourage people to update their boot
loader first.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: