Re: sarge upgrade - linux, grub conflict
On Mon, Apr 17, 2006 at 01:51:30PM +0100, Colin Watson wrote:
> On Mon, Apr 17, 2006 at 11:38:54AM +0200, Bastian Blank wrote:
> > On Sun, Apr 16, 2006 at 09:59:55PM -0700, Steve Langasek wrote:
> > > On Mon, Apr 17, 2006 at 12:29:04AM +0200, Bastian Blank wrote:
> > > > For sarge updates of the linux kernels, grub needs to be updated before
> > > > linux-image*. Can this be forced by an conflict with older versions? A
> > > > dependency is not appropriate.
> > >
> > > Can you give more detail on why grub needs to be updated first? I haven't
> > > heard anything about this incompatibilty, and would like to understand it
> > > before endorsing a versioned conflict; there's a very good chance that a
> > > versioned conflict with grub would force removal, not upgrade, of the
> > > bootloader.
> > kernel-package >> 10 uses debconf for the user communication. This
> > includes the pre and post scripts specified in /etc/kernel-img.conf.
> > update-grub from grub older than 0.97-3 writes informations to stdout,
> > which is coupled to debconf and makes it fail.
> Surely sarge kernel updates should be using the kernel-package in sarge,
> namely 8.135. If there are changes needed from later versions of
> kernel-package, they should be backported.
I kind of believe this was in the light of sarge -> etch migrations though,
where etch kernels will have trouble with sarge grub or something such.