1 |
Hey list |
2 |
|
3 |
during yesterday's upgrade I read the news about python 3.4 being the |
4 |
new profile default. In its course a lot of python-related packages were |
5 |
indeed rebuilt (up until then I had set PYTHON_TARGETS to 2.7, 3.3 and |
6 |
3.4 manually due to blender, which already required 3.4). But in the |
7 |
end, depclean will still not remove python 3.3. So I dug and after some |
8 |
more cleanup (some packages had to be un-keyword to support 3.4) I got: |
9 |
|
10 |
---[ $ emerge -cpv python:3.3 ]------------------------------------------------- |
11 |
Calculating dependencies... done! |
12 |
dev-lang/python-3.3.5-r1 pulled in by: |
13 |
dev-python/lxml-3.3.5 requires >=dev-lang/python-3.3.2-r2:3.3 |
14 |
dev-python/setuptools-7.0 requires >=dev-lang/python-3.3.2-r2:3.3 |
15 |
-------------------------------------------------------------------------------- |
16 |
|
17 |
What I don't understand: |
18 |
|
19 |
---[ $ emerge -pvuD --changed-use --with-bdeps=y world ]------------------------ |
20 |
[...] |
21 |
Total: 0 packages, Size of downloads: 0 kB |
22 |
|
23 |
---[ $ emerge -p lxml setuptools ]---------------------------------------------- |
24 |
[ebuild U ~] dev-python/lxml-3.4.1 [3.3.5] PYTHON_TARGETS="-python3_3*" |
25 |
[ebuild R ~] dev-python/setuptools-7.0 PYTHON_TARGETS="-pypy3% -python3_3*" |
26 |
|
27 |
The following keyword changes are necessary to proceed: |
28 |
(see "package.accept_keywords" in the portage(5) man page for more details) |
29 |
# required by lxml (argument) |
30 |
=dev-python/lxml-3.4.1 ~amd64 |
31 |
|
32 |
---[ $ eix -e lxml ]------------------------------------------------------------- |
33 |
[I] dev-python/lxml |
34 |
Available versions: 3.3.5 ~3.3.6 ~3.4.0 ~3.4.1 {beautifulsoup3 doc examples +threads PYTHON_TARGETS="python2_7 python3_3 python3_4"} |
35 |
Installed versions: 3.3.5(22:03:28 05.11.2014)(threads -beautifulsoup3 -doc -examples PYTHON_TARGETS="python2_7 python3_3 python3_4 -python3_2") |
36 |
-------------------------------------------------------------------------------- |
37 |
|
38 |
If I upgrade the "stable" lxml 3.3.5 to the keyworded 3.4.1, this |
39 |
problem will probably go away. But I want to understand it. How can I |
40 |
find out why portage thinks I need lxml 3.4.1? 3.3.5 knows about python |
41 |
just 3.4 as well, it only uses a different shell syntax to express it: |
42 |
|
43 |
3.3.5: PYTHON_COMPAT=( python{2_7,3_{2,3,4}} ) |
44 |
3.4.1: PYTHON_COMPAT=( python{2_7,3_3,3_4} ) |
45 |
|
46 |
---[ $ emerge -pvc lxml ]------------------------------------------------------- |
47 |
Calculating dependencies... done! |
48 |
dev-python/lxml-3.3.5 pulled in by: |
49 |
app-text/calibre-1.20 requires >=dev-python/lxml-2.2.1 |
50 |
media-gfx/inkscape-0.48.5 requires dev-python/lxml[python_targets_python2_7(-),-python_single_target_jython2_5(-),-python_single_target_jython2_7(-),-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-),python_single_target_python2_7(+)] |
51 |
-------------------------------------------------------------------------------- |
52 |
|
53 |
Both inkscape and calibre only care about python 2.7. |
54 |
|
55 |
|
56 |
Cheers and good night for now. |
57 |
-- |
58 |
Gruß | Greetings | Qapla’ |
59 |
Please do not share anything from, with or about me with any social network. |
60 |
|
61 |
I happen to have some time. Where is nothing to do? |