Bug#169024: libstdc++-libc6.2-2.so.3 after apt-get upgrade today from unstable included incorrect symlink?
Package: libstdc++3
Version: 1:3.0.4-13
After running a dist-upgrade today from unstable, several programs
(including apt-cache, apt-get, and mozilla) would give the following
error when attempting to launch them from a console:
error while loading shared libraries: libstdc++-libc6.2-2.so.3: cannot
open shared object file: No such file or directory
I checked out /usr/lib, and found that /usr/lib/libstdc++-libc6.2-2.so.3
indeed did not exist. I guesstimated from the existing symlinks that
this should be linked to /usr/lib/libstdc++-3libc6.2-2-2.10.0.so. I
created the link with (as root):
ln -s /usr/lib/libstdc++-3libc6.2-2-2.10.0.so
/usr/lib/libstdc++-libc6.2-2.so.3
This then allowed me to use my programs as normal.
There IS a similar link in /usr/lib, namely:
/usr/lib/libstdc++libc6.2-2.so.3, linked to libstdc++-3libc6.2-2-2.10.0.so
as well as:
/usr/lib/libstdc++libc6.2-2.a.3, linked to
libstdc++-3libc6.2-2-2.10.0.a
Is it possible that these symlinks were typos? It appears that
libstdc++ in both of these links should have been written as libstdc++-
so I believe that these are typos.
I include the pertinent portion of my sources.list file, as I am using
several unofficial 'cutting-edge' unstable sources:
#real unstable Debian
deb ftp://ftp.index.hu/debian/ unstable main non-free contrib
deb ftp://ftp.arnes.si/packages/debian/ unstable main non-free contrib
deb-src ftp://ftp.arnes.si/packages/debian/ unstable main non-free contrib
#main sid sources
deb http://http.us.debian.org/debian/ unstable main non-free contrib
deb-src http://http.us.debian.org/debian/ unstable main non-free contrib
deb http://ftp.se.debian.org/debian-non-US/ unstable/non-US main contrib
non-free
deb http://ftp.no.debian.org/debian-non-US/ unstable/non-US main contrib
non-free
I want this bug report to get to the correct maintainer, so I am mailing
it to the debian-user mailing list as well as the bug submission email.
If someone has upgraded recently and has this problem, they will have to
correct the symlinks before any apt functions will work.
Thanks,
Nathan Waddell
Reply to: