I am running testing and did an upgrade today, which included libc6 and quite
a few other packages.
>From experience it seems that after a release there is always a lot of
upload activity in Debian (which is good). This breaks things in
unstable, stalls the transition into testing and sometimes even breaks
things in testing (which is not so good, but probably inevitable).
Therefore you should only use "testing" if you want to help testing. In
a few month, testing will probably stabilise and become more useable.
Now I have problems with some non-Debian libraries, that I use for work, and
the backtrace looks a lot like problems with the new libc6. Is there any
connection between the new libc6 and the gcc4.0 transition?
Absolutely possible. Especially java packages regularly break after
libc upgrade, but also other binary packages may be affected. Can you
be a bit more specific concerning your third party packages?
How can I downgrade libc6 to the previous state? I tried with apt-get:
apt-get install libc6=
2.3.2.ds1-22
(which was the previous version) but it tells me, it can't find this version
anymore. Is there any way of reverting the upgrade, without downgrading to
Sarge?
The only thing I can recommend is to downgrade to Sarge. There is an
archive for old testing packages, and you should be able to find the
libc6 package there. See
http://snapshot.debian.net/ . However, the
upgrade probably changed more than one package, and you have to
download, compile and install all affected packages. You then have to
put a hold on libc6, which probably stalls most new packages in testing
coming forth. So you will not get much benefit out of testing compared
to using Sarge.
Thomas