On Mon, May 19, 2003 at 04:52:51PM +0200, Matthias Klose wrote: > Never seen this upgrade behaviour. Was libgcc1 installed before > libstdc++5? If not, please could you explictely install libgcc1 and > then libstdc++5? i have tried that.
it says "already at latest version". then i tried installing gcc 3.3. that failed to fix the problem. when i manually installed the OLD version of libstdc++: 514 dpkg -i /var/cache/apt/archives/libgcc1_1%3a3.2.3-0pre6_i386.deb 515 dpkg -i /var/cache/apt/archives/libstdc++5_1%3a3.2.3-0pre6_i386.deb then it fixed the problem ****** BUT ****** i now cannot install gcc 3.3 or anything else that depends on gcc 3.3 including groff, kernel-package, dselect, dpkg and a WHOLE boat load of critical packages. the only way that i can recover my system back to a useable state is: - remove unstable from sources.list - deinstall gcc (!!!!) - deinstall python2.2 (!!!) and all of its dependent modules, python-mysql, htmltmpl, crypto, .... python-postgres just to name a few - reinstall python2.2 - re-add unstable back into sources.list - reinstall all of my python modules including python2.2-dev if i do NOT follow this procedure i end up with being either unable to reinstall or unable to run python. trust me when i say that this is a SERIOUS problem with the present debian unstable and i guarantee that you will see more people get into difficulties if they have python2.2 or any of the other programs that depend on libstdc++5 compiled with gcc3.2, and gcc3.3 on their system. l. > 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. there are a LOT of broken programs that have exactly this dependency problem. python2.2, update-menus were only two that i noticed and started to freak out over. > 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). -- -- expecting email to be received and understood is a bit like picking up the telephone and immediately dialing without checking for a dial-tone; speaking immediately without listening for either an answer or ring-tone; hanging up immediately and then expecting someone to call you (and to be able to call you). -- every day, people send out email expecting it to be received without being tampered with, read by other people, delayed or simply - without prejudice but lots of incompetence - destroyed. -- please therefore treat email more like you would a CB radio to communicate across the world (via relaying stations): ask and expect people to confirm receipt; send nothing that you don't mind everyone in the world knowing about...
