Bug#629983: libc6 install aborts with "A non-dpkg owned copy of the C library was found in /lib."
Judging from my upgrade experience I'd now say that the entire handling
to me seems pretty much solidly wrong.
I believe that I (as opposed to some other people?) _do_ have (almost) all
files properly dpkg-managed, by the ldso package.
Status: purge ok installed
Maintainer: David Engel <email@example.com>
Depends: libc6 (>= 2.1.94)
Description: The Linux dynamic linker and library for libc4 and libc5.
This dynamic linker provides the user-level support for loading and
linking DLL and ELF shared libraries. You do not need this package
unless you have very old programs which use libc4 or libc5. The libc6
package has its own dynamic linker that is used for all current
The only file that was "actually" rogue was /bin/ld.so, and even moving away
that single remaining non-managed file did not suffice to satisfy
the (woefully incorrect?) preinst check.
Thus I had to FORCEFULLY remove files belonging to the ldso package to make
the upgrade proceed.
I'm now having severe questions about glibc upgrade at this package version
and especially its compatibility versus a pre-installed and existing ldso package (which is to be used for __FOREIGN__ purposes such as libc4/5 compat!!).
Don't tell me that this upgrade just successfully and singlehandedly
broke any and all libc4/5 compat... (not that I personally would still much
rely on that at this moment ;-)).
[note that I recently changed package status to "purged" -
which was ultimately unsuccessful since ldso is obviously required by
the properly installed libc5 package]