| 1 |
On May 24, 2016 10:05:44 AM GMT+02:00, Arve Barsnes <arve.barsnes@×××××.com> wrote: |
| 2 |
>On 24 May 2016 at 09:41, Marcin Cieslak <saper@×××××.info> wrote: |
| 3 |
>> sys-apps/portage:0 |
| 4 |
>> |
| 5 |
>> (sys-apps/portage-2.2.26:0/0::gentoo, ebuild scheduled for merge) |
| 6 |
>pulled in by |
| 7 |
>> sys-apps/portage (Argument) |
| 8 |
>> |
| 9 |
>> (sys-apps/portage-2.2.14:0/0::gentoo, installed) pulled in by |
| 10 |
>> |
| 11 |
>sys-apps/portage[python_targets_python2_7(-)?,python_targets_python3_3(-)?,-python_single_target_python2_7(-),-> |
| 12 |
>python_single_target_python3_3(-)] required by |
| 13 |
>(app-admin/webapp-config-1.52-r1:0/0::gentoo, installed) |
| 14 |
> |
| 15 |
>Not quite sure but I guess you could try one of |
| 16 |
>- upgrading portage one version at a time (emerge -1va |
| 17 |
>=portage-2.2.20.1) |
| 18 |
>- upgrading webapp-config at least to 1.53.-r2 which supports python |
| 19 |
>3.4 |
| 20 |
>- doing the upgrade with PYTHON_TARGETS="python3_3" |
| 21 |
> |
| 22 |
>Any one of these or any combination might get you a step closer to a |
| 23 |
>solution, as it seems python is for both setuptools and portage |
| 24 |
>conflicts. |
| 25 |
|
| 26 |
The usual method is to do it in stages. |
| 27 |
Get portage snapshots about 3 to 6 months apart and do it that way. |
| 28 |
|
| 29 |
How long ago did you update that system last? |
| 30 |
|
| 31 |
-- |
| 32 |
Joost |
| 33 |
-- |
| 34 |
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
Archives