[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#95800: upgrade is broken



Brian May writes:
 > Package: libstdc++2.10-dev
 > Version: 1:2.95.2-13
 > Severity: grave
 > 
 > Preparing to replace libstdc++2.10-dev 1:2.95.2-13 (using .../libstdc++2.10-dev_1%3a2.95.4-0.010424_i386.deb) ...
 > perl: /lib/libc.so.6: version `GLIBC_2.2' not found (required by /lib/libdb.so.3)
 > dpkg: warning - old pre-removal script returned error exit status 1
 > dpkg - trying script from the new package instead ...
 > perl: /lib/libc.so.6: version `GLIBC_2.2' not found (required by /lib/libdb.so.3)

these messages seem indpendent of the dependency issue.


 > dpkg: error processing /var/cache/apt/archives/libstdc++2.10-dev_1%3a2.95.4-0.010424_i386.deb (--unpack):
 >  subprocess new pre-removal script returned error exit status 1
 > dpkg: regarding .../libc6-dev_2.2.2-4_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.2-4_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.4-0.010424_i386.deb
 >  /var/cache/apt/archives/libc6-dev_2.2.2-4_i386.deb
 > E: Sub-process /usr/bin/dpkg returned an error code (1)
 > 
 > I reported this (and a more complete listing) to debian-devel.
 > 
 > Apparently a predepends should fix this (Sorry, I can't remember
 > what package, probably was libc6 which hasn't been installed yet).

- libc6-2.2.2 has been installed, so I assume libstdc++2.10-glibc2.2
  doesn't need a Pre-Dependency on libc6 (>=2.2)?

- does libstdc++2.10-dev need a pre-dependency on libc6-dev (>= 2.2)?



Reply to: