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.
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