1 |
Francesco Talamona wrote: |
2 |
> |
3 |
> On Sunday 07 August 2011, john wrote: |
4 |
> |
5 |
> > Hello, |
6 |
> |
7 |
> > |
8 |
> |
9 |
> > I am trying to emerge kde-meta but getting the following error |
10 |
> |
11 |
> > message |
12 |
> |
13 |
> > |
14 |
> |
15 |
> > Calculating dependencies... done! |
16 |
> |
17 |
> > Traceback (most recent call last): |
18 |
> |
19 |
> > File "/usr/bin/emerge", line 43, in <module> |
20 |
> |
21 |
> > retval = emerge_main() |
22 |
> |
23 |
> > File "/usr/lib64/portage/pym/_emerge/main.py", line 1907, in |
24 |
> |
25 |
> > emerge_main myopts, myaction, myfiles, spinner) |
26 |
> |
27 |
> > File "/usr/lib64/portage/pym/_emerge/actions.py", line 302, in |
28 |
> |
29 |
> > action_build mydepgraph.display_problems() |
30 |
> |
31 |
> > File "/usr/lib64/portage/pym/_emerge/depgraph.py", line 5998, in |
32 |
> |
33 |
> > display_problems self._display_problems() |
34 |
> |
35 |
> > File "/usr/lib64/portage/pym/_emerge/depgraph.py", line 6019, in |
36 |
> |
37 |
> > _display_problems self._show_slot_collision_notice() |
38 |
> |
39 |
> > File "/usr/lib64/portage/pym/_emerge/depgraph.py", line 702, in |
40 |
> |
41 |
> > _show_slot_collision_notice |
42 |
> |
43 |
> > self._dynamic_config._slot_conflict_handler = |
44 |
> |
45 |
> > slot_conflict_handler(self) File |
46 |
> |
47 |
> > "/usr/lib64/portage/pym/_emerge/resolver/slot_collision.py", line |
48 |
> |
49 |
> > 129, in __init__ |
50 |
> |
51 |
> > self._prepare_conflict_msg_and_check_for_specificity() File |
52 |
> |
53 |
> > "/usr/lib64/portage/pym/_emerge/resolver/slot_collision.py", line |
54 |
> |
55 |
> > 346, in _prepare_conflict_msg_and_check_for_specificity if use in |
56 |
> |
57 |
> > violated_atom.use.enabled.union(violated_atom.use.disabled): |
58 |
> |
59 |
> > AttributeError: 'NoneType' object has no attribute 'enabled' |
60 |
> |
61 |
> |
62 |
> Is kde-meta the only packages that give this error? Have you tried to |
63 |
> emerge something else? |
64 |
> |
65 |
> |
66 |
> It looks like your computer has a problem with python. |
67 |
> |
68 |
> |
69 |
> HTH |
70 |
> |
71 |
> Francesco |
72 |
> |
73 |
> |
74 |
|
75 |
|
76 |
I was wondering the same thing. OP, did you upgrade python and forget |
77 |
to run python-updater by chance? |
78 |
|
79 |
Also, yours should look like this too: |
80 |
|
81 |
root@fireball / # eselect python list |
82 |
Available Python interpreters: |
83 |
[1] python2.7 * |
84 |
[2] python3.1 |
85 |
root@fireball / # |
86 |
|
87 |
Make sure you don't have it set to 3.1. |
88 |
|
89 |
Dale |
90 |
|
91 |
:-) :-) |