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