Am Donnerstag, 12. Juni 2008 schrieb ext Nicolai Beuermann: > You are right it´s not a real solution. Only a solution to get back the > old (and working) system with two installed versions of glibc in package > database.
So emerge -ep world shows it would re-install 2.3.4.
> > > > quickpkg glibc-2.3.4 (just in case...)
> > > > emerge -C glib-2.3.4
> > >
> > > you mean to unmerge glibc-2.3.4?
> > > When I do this my system is no longer useable. emerge wouldn´t work.
OK, didn't see that in previous messages. In this case, you could have
re-emerged python before unmerging 2.3.4.
> > > Marvelously i´ve repaired it via reemerging glibc-2.6.1 via a live cd
> > > and chroot...
OK, good to know.
Bye...
Dirk
--
Dirk Heinrichs | Tel: +49 (0)162 234 3408
Configuration Manager | Fax: +49 (0)211 47068 111
Capgemini Deutschland | Mail: [EMAIL PROTECTED]
Wanheimerstraße 68 | Web: http://www.capgemini.com
D-40468 Düsseldorf | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: wwwkeys.pgp.net
signature.asc
Description: This is a digitally signed message part.
