| 1 |
I always do "emerge -uDNavq world" |
| 2 |
I think it should be OK |
| 3 |
|
| 4 |
Thelma |
| 5 |
|
| 6 |
On 08/30/2015 05:58 PM, Fernando Rodriguez wrote: |
| 7 |
> On Sunday, August 30, 2015 9:41:04 AM thelma@×××××××××××.com wrote: |
| 8 |
>> All it was needed was in portage.use |
| 9 |
>> |
| 10 |
>> # required by app-portage/gentoolkit-0.3.0.9-r2 |
| 11 |
>> # required by app-portage/gentoolkit (argument) |
| 12 |
>> =sys-apps/portage-2.2.20.1 python_targets_python3_3 |
| 13 |
>> |
| 14 |
>> Thelma |
| 15 |
> |
| 16 |
> Now you'll probably run into similar errors when you do run an update with the |
| 17 |
> --newuse (ideally you should use it for every update -- it's the same as the N |
| 18 |
> flag on my original reply) or when one of those packages is updated. |
| 19 |
> |
| 20 |
> |
| 21 |
>> On 08/30/2015 08:43 AM, Mick wrote: |
| 22 |
>>> On Saturday 29 Aug 2015 20:36:04 neu pat wrote: |
| 23 |
>>>> I emerge python3.4 set as active: |
| 24 |
>>>> eselect python list |
| 25 |
>>>> Available Python interpreters: |
| 26 |
>>>> [1] python2.7 |
| 27 |
>>>> [2] python3.3 |
| 28 |
>>>> [3] python3.4 * |
| 29 |
>>>> but it still complain about Multiple package instances |
| 30 |
>>>> |
| 31 |
>>>> [ebuild U ] sys-apps/portage-2.2.20.1 [2.2.14] |
| 32 |
>>>> PYTHON_TARGETS="python3_4* -python3_3*" |
| 33 |
>>>> |
| 34 |
>>>> !!! Multiple package instances within a single package slot have been |
| 35 |
>>>> pulled !!! into the dependency graph, resulting in a slot conflict: |
| 36 |
>>>> |
| 37 |
>>>> sys-apps/portage:0 |
| 38 |
>>>> |
| 39 |
>>>> (sys-apps/portage-2.2.20.1:0/0::gentoo, ebuild scheduled for merge) |
| 40 |
>>>> pulled in by |
| 41 |
>>>> sys-apps/portage (Argument) |
| 42 |
>>>> |
| 43 |
>>>> (sys-apps/portage-2.2.14:0/0::gentoo, installed) pulled in by |
| 44 |
>>>> |
| 45 |
>>>> sys- |
| 46 |
> apps/portage[python_targets_python2_7(-)?,python_targets_python3_3(-)?, |
| 47 |
>>>> -python_single_target_python2_7(-),-python_single_target_python3_3(-)] |
| 48 |
>>>> required by (app-admin/webapp-config-1.52-r1:0/0::gentoo, installed) |
| 49 |
>>>> |
| 50 |
>>>> |
| 51 |
>>>> |
| 52 |
>>>> sys- |
| 53 |
> apps/portage[python_targets_python2_7(-)?,python_targets_python3_3(-)?, |
| 54 |
>>>> python_targets_python3_4(-)?,python_targets_pypy(-)?,- |
| 55 |
> python_single_target_ |
| 56 |
>>>> python2_7(-),-python_single_target_python3_3(-),- |
| 57 |
> python_single_target_pytho |
| 58 |
>>>> n3_4(-),-python_single_target_pypy(-)] required by |
| 59 |
>>>> (app-portage/gentoolkit-0.3.0.9-r2:0/0::gentoo, installed) |
| 60 |
>>>> |
| 61 |
>>>> How to fix it? |
| 62 |
>>>> |
| 63 |
>>>> #joseph |
| 64 |
>>> |
| 65 |
>>> Try the --newuse flag, after you remove any 'python_targets_python3_3' |
| 66 |
> entries |
| 67 |
>>> you have inadvertently left in your /etc/portage/package.use |
| 68 |
>>> |
| 69 |
>> |
| 70 |
> |
Archives