1 |
On Sat, Jul 26, 2008 at 6:18 PM, Dale <dalek1967@×××××××××.net> wrote: |
2 |
> Mark Knecht wrote: |
3 |
>> |
4 |
>> On Sat, Jul 26, 2008 at 4:20 PM, Nikos Chantziaras <realnc@×××××.de> |
5 |
>> wrote: |
6 |
>> |
7 |
>>> |
8 |
>>> Dale wrote: |
9 |
>>> |
10 |
>>>> |
11 |
>>>> Mark Knecht wrote: |
12 |
>>>> |
13 |
>>>>> |
14 |
>>>>> As part of emerge -DuN system portage appears to first make me remove |
15 |
>>>>> python by hand. Is this safe? |
16 |
>>>>> |
17 |
>>>> |
18 |
>>>> No! Not until you get a working version installed. Portage needs |
19 |
>>>> python. |
20 |
>>>> Someone correct me if I misstep here: |
21 |
>>>> |
22 |
>>>> emerge the new python, run the python updater and let it emerge whatever |
23 |
>>>> packages it needs to rebuild, check to make sure nothing still needs the |
24 |
>>>> old |
25 |
>>>> version and then you can unmerge the old one. |
26 |
>>>> |
27 |
>>>> I think that is the correct way. |
28 |
>>>> |
29 |
>>> |
30 |
>>> It is. *Only* unmerge the old Python after you emerged the new one *and* |
31 |
>>> ran python-updater. |
32 |
>>> |
33 |
>>> Unmerging Python without first emerging the new version is equivalent to |
34 |
>>> sawing off the branch you are sitting on. You could as well unmerge |
35 |
>>> portage |
36 |
>>> itself and wonder where portage went and why you can't emerge. |
37 |
>>> |
38 |
>>> |
39 |
>> |
40 |
>> Thanks. That is sort of what I thought but I felt it best to ask |
41 |
>> first. It seems I have python oriented things in my world file that |
42 |
>> I'm not clear need to be there. One is python-updater. I'll emerge |
43 |
>> python first and then return to look at how emerge -DuN world would |
44 |
>> proceed. |
45 |
>> |
46 |
>> Thanks! |
47 |
>> |
48 |
>> Cheers, |
49 |
>> Mark |
50 |
>> |
51 |
>> |
52 |
>> |
53 |
> |
54 |
> Not quite there yet. After you emerge the new python, run the python |
55 |
> updater and let it update/re-emerge whatever it needs to. You really need |
56 |
> to run the updater tool. It looks for packages that will still depend on |
57 |
> the old python and rebuild them so they will work with the new one. |
58 |
> |
59 |
> If you emerge the new python and unmerge the old python, some things may not |
60 |
> work, including portage. |
61 |
> |
62 |
> After you get that sorted out, then you can do the other updates. |
63 |
> |
64 |
> Make sense? |
65 |
> |
66 |
> Dale |
67 |
> |
68 |
> :-) :-) |
69 |
> |
70 |
|
71 |
It's almost exactly the question I Came back to ask. Thanks. |
72 |
|
73 |
I finished the python emerge and saw the message about running |
74 |
python-updater. Before doing that I tried the emerge -pvDuN |
75 |
python-updater and saw it still wanted me to remove the old python. I |
76 |
am running python-updater (the old version) now. After that's done |
77 |
it's then OK for me to emerge -C the older version of python by hand |
78 |
and proceed with the emerge -DuN python-updater operation? |
79 |
|
80 |
I am getting messages about packages now being masked, such as: |
81 |
|
82 |
* Adding to list: =games-board/pysol-sound-server-3.01 |
83 |
* Adding to list: =dev-tcltk/snack-2.2.10 |
84 |
|
85 |
These are the packages that would be merged, in order: |
86 |
|
87 |
Calculating dependencies - |
88 |
!!! All ebuilds that could satisfy "=dev-python/pygtk-2.12.0-r1" have |
89 |
been masked. |
90 |
!!! One of the following masked packages is required to complete your request: |
91 |
- dev-python/pygtk-2.12.0-r1 (masked by: ~x86 keyword) |
92 |
|
93 |
For more information, see MASKED PACKAGES section in the emerge man page or |
94 |
refer to the Gentoo Handbook. |
95 |
|
96 |
dragonfly ~ # eix -I pygtk |
97 |
[D] dev-python/pygtk |
98 |
Available versions: (2) 2.10.6 2.12.0 ~2.12.0-r1 ~2.12.1 ~2.12.1-r2 |
99 |
{X doc examples opengl} |
100 |
Installed versions: 2.12.0-r1(2)["proaudio" |
101 |
/usr/portage/local/layman/pro-audio](19:14:20 01/01/08)(opengl -doc |
102 |
-examples) |
103 |
Homepage: http://www.pygtk.org/ |
104 |
Description: GTK+2 bindings for Python |
105 |
|
106 |
|
107 |
Do I need to unmask these things by hand to make forward progress? |
108 |
(Either that or do an emerge -C to remove them and then let an emerge |
109 |
-DuN world/revdep-rebuild catch them...) It seems strange to me that |
110 |
an emerge -DuN system operation is leading me to do things that don't |
111 |
have anything to do with the system. I'm pretty sure that package is |
112 |
used for a game and just getting caught in this general python-updater |
113 |
process. |
114 |
|
115 |
Thanks, |
116 |
Mark |