On Sat, 2011-01-08 at 18:38 +0100, Julien Cristau wrote: > On Sat, Jan 8, 2011 at 17:37:30 +0100, Philipp Kern wrote: > > > Package: release-notes > > Severity: normal > > > > Hi, > > > > I just tried to upgrade a system following the release notes to the > > letter. This means doing first "apt-get upgrade", then installing a new > > kernel and udev, reboot, then doing a full "dist-upgrade". > > > > After reboot only the *old* kernel was present in the grub menu, not the > > new one. grub2 (to replace the installed grub1) was only installed > > *after* the reboot during the dist-upgrade. (So I did upgrade, install > > linux and udev, reboot, update-grub, reboot, dist-upgrade instead.) > > > > After the installation of grub2 I properly get a hook in > > /etc/kernel/postinst.d to call update-grub. Is it possible that you > > should either update grub2 more early in the process or run update-grub > > manually after the kernel installation and before the reboot? > > > > It's not entirely clear to me how it's supposed to happen or if it's > > just user error in the configuration files of the Lenny installation > > that was upgraded. > > > waldi says the kernel should break pre-policy versions of bootloader > packages, and apparently grub was missed.
It wasn't. update-grub has never been called explicitly from the linux-image maintainer scripts. Instead, debian-installer used to set postinst_hook and postrm_hook in /etc/kernel-img.conf if the user chose to install GRUB. A subsequent installation of GRUB would not install any hook. This is a longstanding bug and is not related to the recent changes in linux-image maintainer scripts, therefore a Breaks relation is not appropriate. I think this does belong in release-notes. Ben. -- 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
