| Stephen Gran on Sat, 29 Mar 2003 09:28:07 -0500 |
|
On Fri, Mar 28, 2003 at 01:51:28PM -0500, Fred K Ollinger said: > > libc6 on sarge is broken for most non-i386 architectures, and php4 is > > broken on all architectures with this version of libc6. It is still not > > wuite worked out in sid, so I wouldn't hold my breath for a quick fix > > for that. Barring php4 problems, libc6 is fairly stable on i386. > > What does "broken" mean? Is the package broken or does it actually not > compile against the new libc6? I compile my own php packages so I would > like to know if this would effect me at all. Still, I wouldn't run a > server on full-blown sarge, yet, anyway. I do grab the "unstable" ssh > binaries, though. > > Fred It mostly means strange bugs appearing in odd places - `date` malfunctioning, unresolved symbol errors, that kind of thing. Problematic if you are depending on the box in question. Check out the bug page http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=libc6 for the gory details. You'll notice that quite a lot of the bugs are for non-i386 architectures. -- -------------------------------------------------------------------------- | Stephen Gran | When childhood dies, its corpses are | | steve@lobefin.net | called adults. -- Brian Aldiss | | http://www.lobefin.net/~steve | | -------------------------------------------------------------------------- Attachment:
pgpa6Su0vjz6Q.pgp
|
|