* [gentoo-user] World update and changed PYTHON_TARGETS
@ 2014-11-25 3:35 99% Frank Steinmetzger
0 siblings, 0 replies; 1+ results
From: Frank Steinmetzger @ 2014-11-25 3:35 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 3174 bytes --]
Hey list
during yesterday's upgrade I read the news about python 3.4 being the
new profile default. In its course a lot of python-related packages were
indeed rebuilt (up until then I had set PYTHON_TARGETS to 2.7, 3.3 and
3.4 manually due to blender, which already required 3.4). But in the
end, depclean will still not remove python 3.3. So I dug and after some
more cleanup (some packages had to be un-keyword to support 3.4) I got:
---[ $ emerge -cpv python:3.3 ]-------------------------------------------------
Calculating dependencies... done!
dev-lang/python-3.3.5-r1 pulled in by:
dev-python/lxml-3.3.5 requires >=dev-lang/python-3.3.2-r2:3.3
dev-python/setuptools-7.0 requires >=dev-lang/python-3.3.2-r2:3.3
--------------------------------------------------------------------------------
What I don't understand:
---[ $ emerge -pvuD --changed-use --with-bdeps=y world ]------------------------
[...]
Total: 0 packages, Size of downloads: 0 kB
---[ $ emerge -p lxml setuptools ]----------------------------------------------
[ebuild U ~] dev-python/lxml-3.4.1 [3.3.5] PYTHON_TARGETS="-python3_3*"
[ebuild R ~] dev-python/setuptools-7.0 PYTHON_TARGETS="-pypy3% -python3_3*"
The following keyword changes are necessary to proceed:
(see "package.accept_keywords" in the portage(5) man page for more details)
# required by lxml (argument)
=dev-python/lxml-3.4.1 ~amd64
---[ $ eix -e lxml ]-------------------------------------------------------------
[I] dev-python/lxml
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"}
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")
--------------------------------------------------------------------------------
If I upgrade the "stable" lxml 3.3.5 to the keyworded 3.4.1, this
problem will probably go away. But I want to understand it. How can I
find out why portage thinks I need lxml 3.4.1? 3.3.5 knows about python
just 3.4 as well, it only uses a different shell syntax to express it:
3.3.5: PYTHON_COMPAT=( python{2_7,3_{2,3,4}} )
3.4.1: PYTHON_COMPAT=( python{2_7,3_3,3_4} )
---[ $ emerge -pvc lxml ]-------------------------------------------------------
Calculating dependencies... done!
dev-python/lxml-3.3.5 pulled in by:
app-text/calibre-1.20 requires >=dev-python/lxml-2.2.1
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(+)]
--------------------------------------------------------------------------------
Both inkscape and calibre only care about python 2.7.
Cheers and good night for now.
--
Gruß | Greetings | Qapla’
Please do not share anything from, with or about me with any social network.
I happen to have some time. Where is nothing to do?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2014-11-25 3:35 99% [gentoo-user] World update and changed PYTHON_TARGETS Frank Steinmetzger
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox