Frank Lichtenheld a écrit : > On Wed, Jun 13, 2007 at 02:22:37PM +0200, Mike Hommey wrote: >> On Wed, Jun 13, 2007 at 02:13:50PM +0200, Pierre Habouzit <[EMAIL >> PROTECTED]> wrote: >>> 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. >> IANASRM, but IMHO, it would be too late to do this in a point release. >> Why not a preinst script in libc 2.5 to disallow upgrade if the running >> kernel is 2.4, as well as adding conflicts on etch libc to kernel packages ? > > libc6 preinst already aborts if the running kernel is a 2.4
Note that there is also a NEWS.Debian asking the user to upgrade to a 2.6 kernel. This let the user one more chance to abort the install before the preinst script is actually run. -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `- people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
