Goswin - are you saying stable/sarge from amd64.debian.net will have a patched glibc?
There's another application I discovered which fell victim to this pthread issue. But I can't find where it is, and I know it's not as popular as MySQL. It's a shame, I know a lot of people running amd64-based machines for MySQL, and currently if you choose to run a "stable" version you're left with this nasty bug. If a patched glibc is going to be back in stable off amd64.debian.net, I can keep using sarge then. Otherwise I'll have to use testing it appears... - mike On 11/9/05, Goswin von Brederlow <[EMAIL PROTECTED]> wrote: > The glibc in stable won't be updated. Stable is set in stone for > better and worse. It might be possible to fix this in a point release > but I'm not too optimistic. Replacing glibc on all archs when just > amd64 and (so far) just mysql is affected is a big deal. > > But fortunately we have stinkypete on amd64.debian.net were we already > have a few amd64 specific patches to make thinks work, like cdrdao. An > upload of a fixed glibc is going there as we speak, Frederik beat me > to it this morning.
