Never seen this upgrade behaviour. Was libgcc1 installed before libstdc++5? If not, please could you explictely install libgcc1 and then libstdc++5?
Adding a pre-dpends on libgcc1 in libstdc++5 may help here, but this would not catch binaries depending on new symbols in libgcc1, and not depending on libstdc++5. Luke Kenneth Casson Leighton writes: > Package: libgcc1 > Version: 1:3.2.3-0pre6 > Severity: critical > > > actions taken: > apt-get remove jade > > this required, at this time, the installation / upgrade of libgcc1 > and the installation / upgrade of tetex. > > gcc 3.3 and cpp 3.3 was NOT required as part of that installation / upgrade. > > once actioned, python2.2, update-menus, and scores of other programs, > failed to operate, with the following error: > > /usr/lib/libgcc_s.so.1: version 'GCC_3.3' not found (required by > /usr/lib/libstdc++.so.5).