On Wed, Jun 13, 2007 at 01:55:12PM +0200, Mike Hommey wrote: > On Wed, Jun 13, 2007 at 01:25:39PM +0200, Pierre Habouzit <madcoder@debian.org> wrote: > > [-- You may want as a background to this question to read #428655. --] > > > > We have users that still run etch with 2.4 kernels. Though, when > > they'll upgrade to lenny, it will completely destroy their upgrade path, > > in ways that are quite hard to figure out for a beginner. > > > > > > I'd suggest that very very very soon, e.g. it would be more than nice > > in .r1 we add in some core package (e.g. the libc ?) a critical debconf > > note (or alike) that warns the user about that issue, and urge him to > > upgrade his kernel. > > > > I know release notes already advise strongly to migrate, but we must > > do better than that. IMHO that's quite critical, because it's impossible > > to install a 2.6 kernel from lenny/sid without having the libc 2.5 installed > > first. > > Isn't it impossible to run a 2.5 libc with a 2.4 kernel ? If so, there is > a chicken and egg problem... if someone is running a 2.4 kernel, she can't > upgrade to the 2.5 libc, and without the 2.5 libc, she can't upgrade to a > 2.6 kernel... that's the point of my question. The 2.6 kernel in etch do not depends upon a 2.5 libc. the ones in unstable do. So in order to upgrade the libc to upstable one, you _have_ to install an etch 2.6.18 first. I'm asking what we can do to ensure people don't get to the point where they don't know how to break that chicken and egg issue like in #428655. IMHO we should have some kind of warning in etch ASAP, but I'd be glad to have the opinions of the RMs and SRMs on this. -- ·O· Pierre Habouzit ··O madcoder@debian.org OOO http://www.madism.org
Attachment:
pgp8yFeKqZb76.pgp
Description: PGP signature