1 |
Quoting Jan Marten Simons <marten@××××××××××××××××.de>: |
2 |
|
3 |
> Hi sci, |
4 |
> |
5 |
> While trying to update my installation I got a rather strange result, which I |
6 |
> cannot really make any sense of: |
7 |
> |
8 |
> # emerge -avt scipy |
9 |
> |
10 |
> These are the packages that would be merged, in reverse order: |
11 |
> |
12 |
> Calculating dependencies... done! |
13 |
> |
14 |
> emerge: there are no ebuilds built with USE flags to satisfy "virtual/python- |
15 |
> imaging[python_targets_python2_5(-)?,python_targets_python2_6(-)?,python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,- |
16 |
> python_single_target_python2_5(-),-python_single_target_python2_6(-),- |
17 |
> python_single_target_python2_7(-),-python_single_target_python3_2(-),- |
18 |
> python_single_target_python3_3(-)]". |
19 |
> !!! One of the following packages is required to complete your request: |
20 |
> - sci-libs/scipy-0.12.0::gentoo (Change USE: -python_targets_python3_2 - |
21 |
> python_targets_python2_7, this change violates use flag constraints |
22 |
> defined by |
23 |
> sci-libs/scipy-0.12.0: 'any-of ( python_targets_python2_5 |
24 |
> python_targets_python2_6 python_targets_python2_7 python_targets_python3_2 |
25 |
> python_targets_python3_3 )') |
26 |
> (dependency required by "sci-libs/scipy-0.12.0" [ebuild]) |
27 |
> (dependency required by "scipy" [argument]) |
28 |
> |
29 |
> I wonder what might be wrong here. Any idea on this? |
30 |
> |
31 |
I have just hit that and need to fix things in the sage-on-gentoo overlay. |
32 |
This is caused by a combination of things: |
33 |
1) scipy now supports python3 target |
34 |
2) migration to virtual/python-imaging |
35 |
|
36 |
By default portage will now want to build scipy for python 3.2. But you |
37 |
probably |
38 |
still use imaging which python 2.x only rather than the fork pillow which is |
39 |
compatible with python 3.x. |
40 |
|
41 |
pillow and imaging cannot be installed at the same time (they are mutual |
42 |
blockers). Because you have an historic imaging install virtual/python-imaging |
43 |
default to python 2.x targets and no python 3.x targets. |
44 |
|
45 |
Solutions: |
46 |
1) restrict scipy to python 2.7 in package.use |
47 |
or |
48 |
2) migrate to pillow |
49 |
|
50 |
Francois |