1 |
Mark Knecht wrote: |
2 |
> Hi, |
3 |
> I was 8 hours through the emerge -eav world part of upgrading gcc |
4 |
> when it hit the pysol package it's not happy with. The messages are |
5 |
> telling me I need to recompile python with Tkinter support and asked |
6 |
> me to add dev/lang/python X tk to package.use, which I did. However |
7 |
> emerge --resume won't go back and recompile python at this point and |
8 |
> if I start over it's a 575 package compile job and I was already |
9 |
> through about 200 of the packages. |
10 |
> |
11 |
> Is there any way to get python updated and then to resume the |
12 |
> remaining 375 packages where I am currently stopped? |
13 |
> |
14 |
> Can I somehow save the file emerge --resume is currently using, |
15 |
> emerge python with the changes, and then put the current worl list |
16 |
> back in? |
17 |
> |
18 |
> Better yet, can I somehow remove pysol from the list so the emerge |
19 |
> --resume just stoarts from the next package? |
20 |
> |
21 |
> Thanks, |
22 |
> Mark |
23 |
|
24 |
For future reference, you can preserve the resume in two ways. |
25 |
|
26 |
1: Rename /var/log/emerge.log to something else then go do what you |
27 |
want and restore it after you are done. I have done that a couple times. |
28 |
|
29 |
2: Open /var/log/emerge.log and put something in there you will find |
30 |
easily. You can put end of resume in all caps or something. Go do what |
31 |
needs doing then come back and delete everything back up to the line you |
32 |
added, including the line you added. |
33 |
|
34 |
I have not done that last one but have read it works well. |
35 |
|
36 |
Also for furture reference since you likely already know this by now, |
37 |
tkinter was replaced by tk. If it helps you to feel any better, I found |
38 |
out the same way you did. Pysol failed to emerge for me too. :-( |
39 |
|
40 |
Hope that helps. |
41 |
|
42 |
Dale |
43 |
:-) :-) |
44 |
-- |
45 |
gentoo-user@g.o mailing list |