1 |
On 12/10/2013 10:10 AM, gottlieb@×××.edu wrote: |
2 |
> I just tried to run python-updater and received several lines like the |
3 |
> following |
4 |
> Traceback (most recent call last): |
5 |
> File "<string>", line 7, in <module> |
6 |
> ImportError: No module named portage |
7 |
> |
8 |
> It did find 4 files to update |
9 |
> |
10 |
> [ebuild R ] dev-python/gconf-python-2.28.1:2 USE="-examples" 0 kB |
11 |
> [ebuild R ] dev-libs/libgamin-0.1.10-r4 USE="-debug -python -static-libs" ABI_X86="(64) -32 (-x32)" 0 kB |
12 |
> [ebuild R ] sys-libs/libcap-ng-0.7.3 USE="-python -static-libs" 0 kB |
13 |
> [ebuild R ] sys-libs/cracklib-2.9.0-r1 USE="nls zlib -python -static-libs" 0 kB |
14 |
> |
15 |
> However, after the merges, running python-updater again, gave the same |
16 |
> result. |
17 |
> |
18 |
> I remerged python-updater with no change. |
19 |
> |
20 |
> I know that I should be changing my python3 from 3.2 to 3.3 since I have |
21 |
> gotten msgs from other merges saying |
22 |
> |
23 |
> Building package for python3.3 only while python3.2 is active. |
24 |
> Please consider switching the active Python 3 interpreter: |
25 |
> |
26 |
> eselect python set --python3 python3.3 |
27 |
> |
28 |
> Please note that after switching the active Python interpreter, |
29 |
> you may need to run 'python-updater' to rebuild affected packages. |
30 |
> |
31 |
> But I worry about relying on python-updater when it is giving errors. |
32 |
> Should I do the requested eselect ? |
33 |
|
34 |
I switched from 3.2 to 3.3 as the message recommended, although I'm still using |
35 |
2.7 as my primary python version. |
36 |
|
37 |
I should confess, though, that I didn't use python-updater because I'm having |
38 |
other (probably self-inflicted) problems with the gnome3/systemd update at the same |
39 |
time and I also didn't want to trust an automated process like python-updater. |
40 |
|
41 |
Instead, I manually emerged all of the packages in /usr/lib/python3.2/site-packages |
42 |
from a command prompt and all went well. Note: I'm not saying python-updater would |
43 |
screw it up -- I just wasn't in the mood yesterday to take that chance :) |