glibc 2.7-3 MIGRATED to testing causes system to stop starting new programs

[PieterB <PieterB@gewis.nl>]

Hello GNU libc maitainers,

I don't now if this is a new bug, or an addition to bug
#454266 or #454557, so I'm mailing the maintainers.

Today I ran into severe problems after doing a 'apt-get update && apt-get
upgrade'. My previous full update and upgrade was on 2007-12-05 20:25.
See http://gewis.nl/~pieterb/tmp/dpkg.log for the tail of my dpkg.log.

There were problems with upgrading libc to 2.7-3 and after that I could not
start a lot of programs anymore. I tried installing libc 2.7-4 manualy with
dpkg, but I couldn't get it done.

I'll try to recover /var/lib/{apt,dpkg} and /lib from backup tommorow, but I
think it would be good to either:

- upgrade glibc to 2.7-4, or
- downgrade glibc 2.6 in testing?
to prevent other people like me from serious messing up their system.

I tried running 'dpkg -l libc6-i686' as suggested in Bug#454557 but it
didn't work.

If there is anything I can do to help fight these problems please tell me.

Regards,

Pieter