1 |
I just tried to run python-updater and received several lines like the |
2 |
following |
3 |
Traceback (most recent call last): |
4 |
File "<string>", line 7, in <module> |
5 |
ImportError: No module named portage |
6 |
|
7 |
It did find 4 files to update |
8 |
|
9 |
[ebuild R ] dev-python/gconf-python-2.28.1:2 USE="-examples" 0 kB |
10 |
[ebuild R ] dev-libs/libgamin-0.1.10-r4 USE="-debug -python -static-libs" ABI_X86="(64) -32 (-x32)" 0 kB |
11 |
[ebuild R ] sys-libs/libcap-ng-0.7.3 USE="-python -static-libs" 0 kB |
12 |
[ebuild R ] sys-libs/cracklib-2.9.0-r1 USE="nls zlib -python -static-libs" 0 kB |
13 |
|
14 |
However, after the merges, running python-updater again, gave the same |
15 |
result. |
16 |
|
17 |
I remerged python-updater with no change. |
18 |
|
19 |
I know that I should be changing my python3 from 3.2 to 3.3 since I have |
20 |
gotten msgs from other merges saying |
21 |
|
22 |
Building package for python3.3 only while python3.2 is active. |
23 |
Please consider switching the active Python 3 interpreter: |
24 |
|
25 |
eselect python set --python3 python3.3 |
26 |
|
27 |
Please note that after switching the active Python interpreter, |
28 |
you may need to run 'python-updater' to rebuild affected packages. |
29 |
|
30 |
But I worry about relying on python-updater when it is giving errors. |
31 |
Should I do the requested eselect ? |
32 |
|
33 |
thanks, |
34 |
allan |