| 1 |
On 24 May 2016 at 09:41, Marcin Cieslak <saper@×××××.info> wrote: |
| 2 |
> sys-apps/portage:0 |
| 3 |
> |
| 4 |
> (sys-apps/portage-2.2.26:0/0::gentoo, ebuild scheduled for merge) pulled in by |
| 5 |
> sys-apps/portage (Argument) |
| 6 |
> |
| 7 |
> (sys-apps/portage-2.2.14:0/0::gentoo, installed) pulled in by |
| 8 |
> sys-apps/portage[python_targets_python2_7(-)?,python_targets_python3_3(-)?,-python_single_target_python2_7(-),-> python_single_target_python3_3(-)] required by (app-admin/webapp-config-1.52-r1:0/0::gentoo, installed) |
| 9 |
|
| 10 |
Not quite sure but I guess you could try one of |
| 11 |
- upgrading portage one version at a time (emerge -1va =portage-2.2.20.1) |
| 12 |
- upgrading webapp-config at least to 1.53.-r2 which supports python 3.4 |
| 13 |
- doing the upgrade with PYTHON_TARGETS="python3_3" |
| 14 |
|
| 15 |
Any one of these or any combination might get you a step closer to a |
| 16 |
solution, as it seems python is for both setuptools and portage |
| 17 |
conflicts. |
Archives