1 |
Apparently, though unproven, at 18:05 on Monday 02 May 2011, Davide Carnovale |
2 |
did opine thusly: |
3 |
|
4 |
> @alan, no error are printed, where and what should i look for in the logs? |
5 |
|
6 |
It looks awfully like depclean took away your old version of python before you |
7 |
used eselect. Others have posted details of how to deal with this. |
8 |
|
9 |
I'm assuming you are reasonably new to gentoo, here's a tip from someone who |
10 |
already got bitten hard too many times to mention: |
11 |
|
12 |
Some updates require you to take manual action after the fact, and these |
13 |
things cannot be automated (at least not without breaking the gentoo |
14 |
philosophy of let the user decide always). Ubuntu, Fedora, etc does not have |
15 |
this problem as they tell you how things will be, Gentoo is different. |
16 |
|
17 |
So after an emerge world, *always* go through every log file in |
18 |
/var/log/portag/elog[1] and deal with every issue arising before moving onto |
19 |
the next step which is usually depclean, emerge @preserved-rebuild and so on. |
20 |
|
21 |
Some packages should raise alarm bells when they appear in depclean output: |
22 |
python, glibc, gcc, portage. Make sure you've done everything you need to have |
23 |
done before accepting these choices. |
24 |
|
25 |
Two final DONTs: |
26 |
|
27 |
Never blindly accept what depclean says and let it do it's thing. Study the |
28 |
output, the warning printed on the screen to do just that is there for a |
29 |
reason. |
30 |
|
31 |
Never blindly update protected config files with etc-update etc. Check each |
32 |
one individually and do it manually. |
33 |
|
34 |
|
35 |
|
36 |
|
37 |
> |
38 |
> @helmut python just returns to the console, without error or effect of any |
39 |
> sort, does it means python has get unmerged and that's why emerge doesn't |
40 |
> work anymore? |
41 |
> |
42 |
> 2011/5/2 Helmut Jarausch <jarausch@××××××××××××××××.de> |
43 |
> |
44 |
> > On 05/02/2011 05:38:03 PM, Davide Carnovale wrote: |
45 |
> > > Hi all! |
46 |
> > > i was going through a world update today and during --depclean emerge |
47 |
> > > throw |
48 |
> > > an error complaining about possible corrupted binaries or hw failure. |
49 |
> > > since then it has stopped working, no matter what i try to emerge, |
50 |
> > > the |
51 |
> > > command simply return to the shell without any kind of error or any |
52 |
> > > other |
53 |
> > > output at all. |
54 |
> > > i fired and usb stick with the gentoo 11 live dvd and i copied over |
55 |
> > > both |
56 |
> > > bash and emerge binaries to my machine, in case they were corrupted |
57 |
> > > (bash |
58 |
> > > was given as the most likely) but nothing changed. |
59 |
> > > now i simply have no clue on what's wrong and how can i fix it, apart |
60 |
> > > from a |
61 |
> > > full reinstall, which i'd like to avoid. |
62 |
> > > |
63 |
> > > can anyone point me somewhere to solve this problem? |
64 |
> > |
65 |
> > emerge needs Python. Have you tried to invoke Python, just by |
66 |
> > |
67 |
> > python |
68 |
> > import portage |
69 |
> > quit() |
70 |
> > |
71 |
> > Helmut. |
72 |
|
73 |
-- |
74 |
alan dot mckinnon at gmail dot com |