Re: hypothesis about the trouble I had with libc6 and multilib: extraneous libc6-amd64
On Fri, Jan 18, 2013 at 10:11:50AM -0600, Paul Johnson wrote:
> $ dpkg -l | grep libc6
> ii libc6:amd64 2.13-37 amd64
> ii libc6:i386 2.13-37 i386
> ii libc6-amd64 2.13-37 i386
> ii libc6-i386 2.13-37 amd64
So you basicly have libc6 installed 4 times, twice for i386 and
twice for amd64. I could understand that you had 3 of the 4
packages installed, but all 4 makes little sense to me.
So it means that if dpkg is looking for which package provides the
shared library it will actually find 2 packages.
The libc6-amd64 symbol file says you should depend on libc6-amd64,
so dpkg is probably picking that up, and you're probably only
using symbols that were available since 2.7.
If you remove libc6-amd64 (and libc6-i386) you shouldn't see those
issues anymore. But watch out for #699206.
Maybe libc6-amd64 and libc6-i386 shouldn't be providing shlibs and
symbol files anymore.