On Mon, Apr 09, 2007 at 01:28:18PM +0200, Christian Hammers wrote: > > Mmm, guess I wasn't clear -- I mean that there's no point in trying to work > > on this bug, because lenny *as a whole* will not support 2.4 kernels. (the > > glibc maintainers are eager to drop LinuxThreads support, which means lenny > > will stop supporting threading on 2.4 within days/weeks of the etch > > release.)
> What I feared was the upgrade process itself. I guess that mysql and the > new 2.6 kernel will get installed in the same "apt-get dist-upgrade" run > and thus if mysql-server-5.0 hangs and the user presses ctrl-c he is left > with a half broken system. It *doesn't* *matter*. Running etch with a 2.4 kernel is not officially supported; upgrading to lenny on a system running a 2.4 kernel is *guaranteed* to break, and nothing you do in the mysql package will make any difference to this as soon as the new glibc is uploaded to unstable. > Or is there some mechanism that tells the user first to upgrade to a 2.6 > kernel then reboot and then update the rest of the packages? There are the release notes. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
