View previous topic :: View next topic |
Author |
Message |
pente n00b
Joined: 21 Mar 2013 Posts: 29
|
Posted: Mon Sep 15, 2014 10:50 pm Post subject: python targets: 3.2 is missing |
|
|
I am trying to update all my packages in world, and one of the problems I'm running into along the way is that it seems I can no longer have python 3.2 as a target.
Excerpt from make.conf:
Code: |
PYTHON_TARGETS="python2_7 python3_2 python3_3"
PYTHON_SINGLE_TARGET="python3_2"
USE_PYTHON="2.7 3.2 3.3"
|
Python 3.2 is selected:
Code: |
$ eselect python list
Available Python interpreters:
[1] python2.7
[2] python3.2 *
[3] python3.3
[4] python3.4
|
Python 3.2 is installed:
Code: |
$ eix dev-lang/python
[I] dev-lang/python
Available versions:
(2.7) 2.7.7 (~)2.7.8
(3.2) 3.2.5-r6
(3.3) 3.3.5-r1
(3.4) (~)3.4.0 (~)3.4.1
{-berkdb build doc examples gdbm hardened ipv6 +ncurses +readline sqlite +ssl +threads tk +wide-unicode wininst +xml ELIBC="uclibc"}
Installed versions: 2.7.8(2.7)(12:11:45 PM 09/12/2014)(gdbm ipv6 ncurses readline sqlite ssl threads wide-unicode xml -berkdb -build -doc -examples -hardened -tk -wininst ELIBC="-uclibc") 3.2.5-r6(3.2)(02:24:28 PM 09/15/2014)(gdbm ipv6 ncurses readline sqlite ssl threads wide-unicode xml -build -doc -examples -hardened -tk -wininst ELIBC="-uclibc") 3.3.5-r1(3.3)(12:12:44 PM 09/12/2014)(gdbm ipv6 ncurses readline sqlite ssl threads xml -build -doc -examples -hardened -tk -wininst ELIBC="-uclibc") 3.4.1(3.4)(12:20:00 PM 09/12/2014)(gdbm ipv6 ncurses readline sqlite ssl threads xml -build -examples -hardened -tk -wininst ELIBC="-uclibc")
|
(I guess the highlighting doesn't show, but all four slots have the newest available version installed.)
But when I try to emerge any package that specifies python targets, I get a result like this:
Code: |
# PYTHON_TARGETS="python2_7 python3_2 python3_3" emerge -1 statsmodels
These are the packages that would be merged, in reverse order:
Calculating dependencies... done!
[ebuild R ] dev-python/statsmodels-0.5.0 USE="-doc -examples {-test}" PYTHON_TARGETS="python2_7 python3_3 (-python3_2*) (-python2_6%)"
|
Whether or not I explicitly specify PYTHON_TARGETS, the result is the same. Note that the same version of the same package is currently installed with python 3.2 as a target.
Some more excerpts:
Code: |
$ emerge --info
Portage 2.2.12 (python 3.2.5-final-0, default/linux/amd64/13.0, gcc-4.7.3, glibc-2.19-r1, 3.12.0-gentoo x86_64)
=================================================================
PYTHON_SINGLE_TARGET=""
PYTHON_TARGETS="python2_7 python3_3"
USE_PYTHON="2.7 3.2 3.3"
$ PYTHON_TARGETS="python2_7 python3_2" emerge --info
PYTHON_SINGLE_TARGET=""
PYTHON_TARGETS="python2_7"
USE_PYTHON="2.7 3.2 3.3"
|
Any ideas what I can do to fix this problem?
Full emerge --info below.
https://bpaste.net/show/5d58504393b4 |
|
Back to top |
|
|
dol-sen Retired Dev
Joined: 30 Jun 2002 Posts: 2805 Location: Richmond, BC, Canada
|
Posted: Mon Sep 15, 2014 11:14 pm Post subject: |
|
|
The python_target_python3_2 use flag has been masked. It is no longer supported by upstream python and support is already being dropped from some active python pkgs. The 3.2 ebuild will remain in the tree for awhile yet.
In order to merge to the 3.2 target you will have to unmask the use flag. _________________ Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch... |
|
Back to top |
|
|
pente n00b
Joined: 21 Mar 2013 Posts: 29
|
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|