Paul Smith wrote: > dpkg -S was the very first thing I did but: > ~$ dpkg -S /usr/lib/libc.so.6 > dpkg: /usr/lib/libc.so.6 not found. > > The link might have been created by some post-install script.
Paul could you be so kind to do a grep in /var/lib/dpkg/info to see if you can figure out what created those symlinks? I wonder if also something that you might have built/installed locally from source could have created those symlinks. It seems like different pkgs are creating different symlinks and triggering the check in glibc that we are turning into a warning now. Fabio -- libc6 update for Edgy fails due to sanity check https://launchpad.net/bugs/81125 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
