libstdc++2.10-dev install problem in testing/woody?
Hi.
I pointed my apt sources.list at testing and did an 'apt-get
dist-upgrade' which did it's job for the most part but left me with
the following error messages (modulo some formatting):
Preparing to replace libstdc++2.10-dev 1:2.95.2-13 (using
.../libstdc++2.10-dev_1%3a2.95.2-20_i386.deb) ... install-info: No dir
file specified; try --help for more information.
dpkg: warning - old pre-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
install-info: No dir file specified; try --help for more information.
dpkg: error processing /var/cache/apt/archives/libstdc++2.10-dev_1%3a2.95.2-20_i386.deb
(--unpack): subprocess new pre-removal script returned error exit status 1
dpkg: regarding .../libc6-dev_2.2-6_i386.deb containing libc6-dev:
libc6-dev conflicts with libstdc++2.10-dev (<< 1:2.95.2-15)
libstdc++2.10-dev (version 1:2.95.2-13) is installed.
dpkg: error processing /var/cache/apt/archives/libc6-dev_2.2-6_i386.deb
(--unpack): conflicting packages - not installing libc6-dev
Errors were encountered while processing:
/var/cache/apt/archives/libstdc++2.10-dev_1%3a2.95.2-20_i386.deb
/var/cache/apt/archives/libc6-dev_2.2-6_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
As I read this, it seems as if there's a problem with the install
script in the libstdc++2.10-dev_1%3a2.95.2-20_i386.deb package which
prevents libstdc++2.10-dev from being upgraded. This then cascades to
prevent libc6-dev from being upgraded as well.
My question is: is this a bug in the libstdc++2.10-dev package, or is
it a corruption on my system, and what would be the best way to
diagnose this?
Dan
Reply to: