1 |
Am Donnerstag, 12. Juni 2008 schrieb ext Nicolai Beuermann: |
2 |
> You are right it´s not a real solution. Only a solution to get back the |
3 |
> old (and working) system with two installed versions of glibc in package |
4 |
> database. |
5 |
|
6 |
So emerge -ep world shows it would re-install 2.3.4. |
7 |
|
8 |
> > > > quickpkg glibc-2.3.4 (just in case...) |
9 |
> > > > emerge -C glib-2.3.4 |
10 |
> > > |
11 |
> > > you mean to unmerge glibc-2.3.4? |
12 |
> > > When I do this my system is no longer useable. emerge wouldn´t work. |
13 |
|
14 |
OK, didn't see that in previous messages. In this case, you could have |
15 |
re-emerged python before unmerging 2.3.4. |
16 |
|
17 |
> > > Marvelously i´ve repaired it via reemerging glibc-2.6.1 via a live cd |
18 |
> > > and chroot... |
19 |
|
20 |
OK, good to know. |
21 |
|
22 |
Bye... |
23 |
|
24 |
Dirk |
25 |
-- |
26 |
Dirk Heinrichs | Tel: +49 (0)162 234 3408 |
27 |
Configuration Manager | Fax: +49 (0)211 47068 111 |
28 |
Capgemini Deutschland | Mail: dirk.heinrichs@×××××××××.com |
29 |
Wanheimerstraße 68 | Web: http://www.capgemini.com |
30 |
D-40468 Düsseldorf | ICQ#: 110037733 |
31 |
GPG Public Key C2E467BB | Keyserver: wwwkeys.pgp.net |