1 |
Gavin Seddon posted <1136903339.6259.5.camel@linuxstation>, excerpted |
2 |
below, on Tue, 10 Jan 2006 14:28:59 +0000: |
3 |
|
4 |
> Hi, |
5 |
> I have been updating my system. Firstly I used 'emerge --sync' then |
6 |
> 'emerge --update world'. However, the update stops with a segmentation |
7 |
> fault. Is this a big problem that needs fixing and how? |
8 |
|
9 |
You don't provide much information there. Where does it stop? What's the |
10 |
last output before the segfault? Can you do an emerge --pretend --update |
11 |
world? What about an emerge --pretend --update system? What about an |
12 |
emerge --pretend portage (this one to see if it can handle a specific |
13 |
package)? |
14 |
|
15 |
If all those work, it's a problem in actually merging a package. We'll |
16 |
need the last 20 lines or so of the output, the command you were running, |
17 |
and the last 10 lines or so of /var/log/emerge.log, to see what's going |
18 |
on. If the above emerge --pretend tests don't work, continue with the |
19 |
below tests, stopping after each one if it works or you found the problem. |
20 |
|
21 |
You should be safely able to rename your entire portage tree |
22 |
(/usr/portage/ by default) and do another emerge sync to regenerate it. |
23 |
See if that solves the problem. |
24 |
|
25 |
Check your world file (/var/lib/portage/world). It should be a plain text |
26 |
file consisting of a list of category/package names, one to a line, with |
27 |
the last line a blank line. Back it up before making any changes, of |
28 |
course, so you can restore the backup if you screw up. If it's /not/ a |
29 |
simply plain text file as described above, you'll probably have to rebuild |
30 |
it. Post the problem and we'll go from there. |
31 |
|
32 |
It could also be a corrupted portage database. Try renaming /var/db/pkg/ |
33 |
to something else (like /var/db/pkg.test). You should then be able to |
34 |
complete an emerge --pretend world, altho it will want to merge |
35 |
everything, since you just removed the portage database telling it what |
36 |
you have merged at present. This one gets a bit more complex, as you |
37 |
probably don't want to remerge everything, altho you could. If you've |
38 |
been using FEATURES=buildpkg, it wouldn't even be that hard. (That's why |
39 |
I said /rename/ the portage tree, above, not /delete/ it, since the |
40 |
packages you built you'll want to keep, and they are normally in |
41 |
/usr/portage/package.) |
42 |
|
43 |
If you haven't found the problem by this point, you may have a bad portage |
44 |
or python itself. If so, you'll have to find a binary package of |
45 |
whichever one, to get back up and running. They are available, but no use |
46 |
worrying about that until we find it's the problem. |
47 |
|
48 |
-- |
49 |
Duncan - List replies preferred. No HTML msgs. |
50 |
"Every nonfree program has a lord, a master -- |
51 |
and if you use the program, he is your master." Richard Stallman in |
52 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
53 |
|
54 |
|
55 |
-- |
56 |
gentoo-amd64@g.o mailing list |