Looks like you are mixing stable and testing.
That generally ends badly - especially where the core libs get involved.

What is the output of:

1 members found this post helpful.

Hi,
How could you tell? Did you cross check the version numbers of the various packages from the apt-get output?

Sure does.

Evo2.

Only this one The libc6-i386 he is installing is the wheezy one, as it is requiring the wheezy libc6 - however 2.18-4 (presumably a previous testing version - current is 2.19-4) "is to be installed".

I think "is to be installed" can also mean "is already installed", and means that either the sources.list is pointing to jessie/testing as well as stable or (more likely) a package from testing has been installed which pulled in the updated libc6, and the testing repo has subsequently been disabled again.

The "best" way out is probably to update the entire system to jessie (or restore from a pre-bork backup or just reinstall - depending on the role of the machine), as this is going to be a recurring problem with every package install/upgrade.

As far as I remember I needed to install a newer compiler, but nothing else. Otherwise it is the latest stable. No jessie, probably backport was in use. I have no backup, I will simply reinstall if needed (that would be much faster)
Just a bit strange: first installing multiarch together with i386 and finally upgrade libc6 should work, but this way cannot be handled.

The problem is you started with an already broken system, with the 'out of branch' libc6.

Presumably came along with this: