1 |
Mark Knecht wrote: |
2 |
> |
3 |
> It's almost exactly the question I Came back to ask. Thanks. |
4 |
> |
5 |
> I finished the python emerge and saw the message about running |
6 |
> python-updater. Before doing that I tried the emerge -pvDuN |
7 |
> python-updater and saw it still wanted me to remove the old python. I |
8 |
> am running python-updater (the old version) now. After that's done |
9 |
> it's then OK for me to emerge -C the older version of python by hand |
10 |
> and proceed with the emerge -DuN python-updater operation? |
11 |
> |
12 |
|
13 |
After the updater gets through, run this without the quotes: "equery |
14 |
depends =dev-lang/python-2.3.6-r2" That should tell you if anything |
15 |
still depends on the old version. If it lists something then don't |
16 |
unmerge the old version yet. |
17 |
> I am getting messages about packages now being masked, such as: |
18 |
> |
19 |
> * Adding to list: =games-board/pysol-sound-server-3.01 |
20 |
> * Adding to list: =dev-tcltk/snack-2.2.10 |
21 |
> |
22 |
> These are the packages that would be merged, in order: |
23 |
> |
24 |
> Calculating dependencies - |
25 |
> !!! All ebuilds that could satisfy "=dev-python/pygtk-2.12.0-r1" have |
26 |
> been masked. |
27 |
> !!! One of the following masked packages is required to complete your request: |
28 |
> - dev-python/pygtk-2.12.0-r1 (masked by: ~x86 keyword) |
29 |
> |
30 |
> For more information, see MASKED PACKAGES section in the emerge man page or |
31 |
> refer to the Gentoo Handbook. |
32 |
> |
33 |
> dragonfly ~ # eix -I pygtk |
34 |
> [D] dev-python/pygtk |
35 |
> Available versions: (2) 2.10.6 2.12.0 ~2.12.0-r1 ~2.12.1 ~2.12.1-r2 |
36 |
> {X doc examples opengl} |
37 |
> Installed versions: 2.12.0-r1(2)["proaudio" |
38 |
> /usr/portage/local/layman/pro-audio](19:14:20 01/01/08)(opengl -doc |
39 |
> -examples) |
40 |
> Homepage: http://www.pygtk.org/ |
41 |
> Description: GTK+2 bindings for Python |
42 |
> |
43 |
> |
44 |
> Do I need to unmask these things by hand to make forward progress? |
45 |
> (Either that or do an emerge -C to remove them and then let an emerge |
46 |
> -DuN world/revdep-rebuild catch them...) It seems strange to me that |
47 |
> an emerge -DuN system operation is leading me to do things that don't |
48 |
> have anything to do with the system. I'm pretty sure that package is |
49 |
> used for a game and just getting caught in this general python-updater |
50 |
> process. |
51 |
> |
52 |
> Thanks, |
53 |
> Mark |
54 |
> |
55 |
> |
56 |
> |
57 |
|
58 |
I would let the updater run then see if anything changes. It may be |
59 |
that some of the packages will be OK as they are. |
60 |
|
61 |
You can unmask that in /etc/portage/package.keywords and |
62 |
/etc/portage/package.unmask. Keep in mind that these packages are still |
63 |
be tested. You shouldn't use them unless you know the risks. |
64 |
|
65 |
Dale |
66 |
|
67 |
:-) :-) |