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

Bug#514799: marked as done (release-notes: check grub's hooks in /etc/kernel-img.conf before upgrade)

Your message dated Tue, 11 Jan 2011 22:39:06 +0100
with message-id <20110111213906.GA8269@radis.liafa.jussieu.fr>
and subject line Re: Bug#514799: release-notes: check grub's hooks in /etc/kernel-img.conf before upgrade
has caused the Debian Bug report #514799,
regarding release-notes: check grub's hooks in /etc/kernel-img.conf before upgrade
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.)


-- 
514799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514799
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release-notes
Severity: normal

After upgrading from sarge to etch, users were invited to manually
update some entries in /etc/kernel-img.conf (specifically, the
postinst_hook and postrm_hook) as described
in etch's /usr/share/doc/grub-doc/NEWS.Debian.

However, this was not totally obvious, and because the compatibility
wrapper ensured that everything worked, I imagine there are quite a few
systems where this was not done.

It seems possible that such systems would break after the upgrade to lenny
(although I haven't tested this). If it is known that they will not break,
then please close this bug! (and accept my apologies).

Otherwise, it might be helpful to add something like the following to the
release notes, possibly at 4.1.1.2 (straight after 4.1.1.1 makes sure that
you are on a suitable kernel) or 4.1.6 (straight after LILO issues).

4.1.1.2 Check grub's kernel installation hooks
If you use GRUB as bootloader and previously upgraded to etch from an older
release of debian, please verify that the hooks in /etc/kernel-img.conf have
been updated from /sbin/update-grub to /usr/sbin/update-grub. The older path
will cease to work after the upgrade to lenny. For more details, see
/usr/share/doc/grub-doc/NEWS.Debian from the grub-doc package.

I hope this helps! Best wishes and thanks for all your work on debian...

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-k7
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)

--- End Message ---
--- Begin Message --- 
On Sat, Sep  4, 2010 at 02:25:41 +0200, Michael Prokop wrote:

> * W. Martin Borgert [Die Feb 10, 2009 at 11:49:01 +0000]:
> > On 2009-02-10 22:54, J S Bygott wrote:
> > > 4.1.1.2 Check grub's kernel installation hooks
> > > If you use GRUB as bootloader and previously upgraded to etch from an older
> > > release of debian, please verify that the hooks in /etc/kernel-img.conf have
> > > been updated from /sbin/update-grub to /usr/sbin/update-grub. The older path
> > > will cease to work after the upgrade to lenny. For more details, see
> > > /usr/share/doc/grub-doc/NEWS.Debian from the grub-doc package.
> 
> > Any comments? Shall we add this to the lenny release notes?
> 
> Nowadays usage of do_bootloader, postinst_hook and postrm_hook in
> /etc/kernel-img.conf is expected to differ, as documented in
> http://kernel-handbook.alioth.debian.org/ch-update-hooks.html#s-init-config
> and discussed in "Policy for Linux kernel, initramfs, boot loader
> update process", see
> http://lists.debian.org/debian-devel/2010/06/msg00538.html & ff.
> 
> So AFAICT this bugreport isn't valid for squeeze anymore and could
> be closed if there aren't any objections.
> 
Actually there's still a chance that update-grub doesn't run on a
partial upgrade to squeeze (upgrading the kernel but not grub), see
#690330.  I've added a note in r8066; closing this bug.

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: