Gentoo Archives: gentoo-user

From: Kevin O'Gorman <kogorman@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] emerge stopped working
Date: Mon, 02 May 2011 17:20:08
Message-Id: BANLkTinKToA+t2BAbpkW2b0hb93bY=EH0w@mail.gmail.com
In Reply to: Re: [gentoo-user] emerge stopped working by Kevin O'Gorman
1 On Mon, May 2, 2011 at 9:54 AM, Kevin O'Gorman <kogorman@×××××.com> wrote:
2
3 >
4 >
5 > On Mon, May 2, 2011 at 9:05 AM, Davide Carnovale <
6 > francesco.davide.carnovale@×××××.com> wrote:
7 >
8 >>
9 >> 2011/5/2 Helmut Jarausch <jarausch@××××××××××××××××.de>
10 >>
11 >>> On 05/02/2011 05:38:03 PM, Davide Carnovale wrote:
12 >>> > Hi all!
13 >>> > i was going through a world update today and during --depclean emerge
14 >>> > throw
15 >>> > an error complaining about possible corrupted binaries or hw failure.
16 >>> > since then it has stopped working, no matter what i try to emerge,
17 >>> > the
18 >>> > command simply return to the shell without any kind of error or any
19 >>> > other
20 >>> > output at all.
21 >>> > i fired and usb stick with the gentoo 11 live dvd and i copied over
22 >>> > both
23 >>> > bash and emerge binaries to my machine, in case they were corrupted
24 >>> > (bash
25 >>> > was given as the most likely) but nothing changed.
26 >>> > now i simply have no clue on what's wrong and how can i fix it, apart
27 >>> > from a
28 >>> > full reinstall, which i'd like to avoid.
29 >>> >
30 >>> > can anyone point me somewhere to solve this problem?
31 >>> >
32 >>>
33 >>> emerge needs Python. Have you tried to invoke Python, just by
34 >>>
35 >>> python
36 >>> import portage
37 >>> quit()
38 >>>
39 >>> Helmut.
40 >>>
41 >>> @alan, no error are printed, where and what should i look for in the
42 >> logs?
43 >>
44 >> @helmut python just returns to the console, without error or effect of any
45 >> sort, does it means python has get unmerged and that's why emerge doesn't
46 >> work anymore?
47 >>
48 >>
49 > I have the same problem. I just did a --depclean, and find that 'vim'
50 > cannot run:
51 >
52 > treat log # vim
53 > vim: error while loading shared libraries: libpython2.6.so.1.0: cannot open
54 > shared object file: No such file or directory
55 > treat log #
56 >
57 > So I have to fall back on pico, which I only barely know how to use.
58 >
59 > I have quite a collection of binary packages (everything emerged in the
60 > last few years), but even untarring them fails (just wedges with no message,
61 > and even strace(1) is not helping me find this.)
62 >
63 > I can unpack on a different machine, but will that even help?
64 >
65 > BTW, it's not that I don't have python, it's just that version 2.6.6 got
66 > unloaded somehow:
67 > [I] dev-lang/python
68 > Available versions:
69 > (2.4) 2.4.6{tbz2}
70 > (2.5) 2.5.4-r4{tbz2}
71 > (2.6) 2.6.5-r3{tbz2} 2.6.6-r1{tbz2} 2.6.6-r2{tbz2}
72 > (2.7) 2.7.1-r1{tbz2}
73 > (3.1) 3.1.2-r4{tbz2} 3.1.3-r1{tbz2}
74 > (3.2) [M]~3.2
75 > {-berkdb bootstrap build +cxx doc elibc_uclibc examples gdbm ipv6
76 > +ncurses +readline sqlite +ssl +threads tk +wide-unicode wininst +xml}
77 > Installed versions: <reformatted for clarity>
78 > 2.4.6(2.4){tbz2}(11:05:11 PM 02/19/2011)(cxx gdbm ipv6 ncurses
79 > readline ssl threads tk wide-unicode xml -berkdb -bootstrap -build -doc
80 > -elibc_uclibc -examples -wininst)
81 > 2.5.4-r4(2.5){tbz2}(11:16:07 PM 02/19/2011)(gdbm ipv6 ncurses
82 > readline ssl threads tk wide-unicode xml -berkdb -build -doc -elibc_uclibc
83 > -examples -sqlite -wininst)
84 > 2.7.1-r1(2.7){tbz2}(06:11:36 PM 04/21/2011)(gdbm ipv6 ncurses
85 > readline ssl threads tk wide-unicode xml -berkdb -build -doc -elibc_uclibc
86 > -examples -sqlite -wininst)
87 > 3.1.3-r1(3.1){tbz2}(02:31:33 PM 02/26/2011)(gdbm ipv6 ncurses
88 > readline ssl threads tk wide-unicode xml -build -doc -elibc_uclibc -examples
89 > -sqlite -wininst)
90 > Homepage: http://www.python.org/
91 >
92 > I'm right now trying to see if "eselect python set 3" will let emerge, vim
93 > and tar run again. 3 is version 2.7.
94 >
95 > --
96 > Kevin O'Gorman, PhD
97 >
98 >
99 ANSWER: yes it did. At least emerge and vim are working again. I'm also
100 doing all of my usual post-emerge cleanups just in case:
101 #!/bin/bash
102
103 echo ' !!! Running dispatch-conf'
104 dispatch-conf
105 echo ' !!! Running revdep-rebuild --ignore'
106 revdep-rebuild --ignore
107 echo ' !!! Running lafilefixer --justfixit'
108 lafilefixer --justfixit | fgrep -v 'skipping update'
109 echo ' !!! Running perl-cleaner all'
110 perl-cleaner all | fgrep -v 'Skipping directory'
111 I'm hoping you also have an extra copy of python around, so you can do the
112 same thing.
113
114
115 --
116 Kevin O'Gorman, PhD