| 1 |
On Thu, May 19, 2016 at 01:21:20AM +0800, Andrew Lowe wrote: |
| 2 |
> Hi all, |
| 3 |
> Doing the usual "emerge -NuD world" and I get hit with: |
| 4 |
> |
| 5 |
> ******************** |
| 6 |
> |
| 7 |
> Calculating dependencies... done! |
| 8 |
> |
| 9 |
> !!! The ebuild selected to satisfy ">=kde-frameworks/ki18n-5.18.0:5" has |
| 10 |
> unmet requirements. |
| 11 |
> - kde-frameworks/ki18n-5.22.1::gentoo USE="-debug -doc -test" |
| 12 |
> ABI_X86="64" PYTHON_SINGLE_TARGET="python3_4 -python2_7" |
| 13 |
> PYTHON_TARGETS="python2_7 -python3_4" |
| 14 |
|
| 15 |
PYTHON_SINGLE_TARGET sets the version of python for a package that can |
| 16 |
only be installed with a single python. PYTHON_TARGETS sets the versions |
| 17 |
of python a python package will be installed to/with for packages that |
| 18 |
can be installed to multiple python versions. |
| 19 |
|
| 20 |
You have PYTHON_SINGLE_TARGET=python3_4, but PYTHON_TARGETS does *not* |
| 21 |
contain python3_4. This is bad. |
| 22 |
|
| 23 |
> The following REQUIRED_USE flag constraints are unsatisfied: |
| 24 |
> python_single_target_python3_4? ( python_targets_python3_4 ) |
| 25 |
|
| 26 |
This is the line that enforces the above (i.e. PYTHON_SINGLE_TARGET must |
| 27 |
be in PYTHON_TARGETS). |
| 28 |
|
| 29 |
> ******************** |
| 30 |
> |
| 31 |
> kde-frameworks/ki18n python_single_target_python3_4 |
| 32 |
> |
| 33 |
|
| 34 |
This is not the problem and can be removed. |
| 35 |
|
| 36 |
> ******************** |
| 37 |
> |
| 38 |
> But the problem persists, nothing has changed. "eselect python list" |
| 39 |
> lists that I've got Python 2.7, 3.4 and 3.5 installed. I've just noticed |
| 40 |
> that doing "emerge --info ki18n" shows: |
| 41 |
> |
| 42 |
> PYTHON SINGLE_TARGET="python3_5" |
| 43 |
|
| 44 |
what? |
| 45 |
|
| 46 |
What do you have PYTHON_TARGETS and PYTHON_SINGLE_TARGET in |
| 47 |
/etc/portage/make.conf? |
| 48 |
|
| 49 |
Alec |
Archives