p.s. the version of python 2.2 is back at 2.2.1 compiled with gcc 2.95.4 (stable version)
the version that got into trouble was the python 2.2 that was compiled with gcc 3.2 (unstable latest version?) On Mon, May 19, 2003 at 07:40:06PM +0200, Matthias Klose wrote: > [CC to debian-devel, did anybody see this behaviour on an update?] > > Luke Kenneth Casson Leighton writes: > > 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 > > -- -- 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...