Summary: | =sci-libs/scipy-0.12.0 - Does not emerge with Python3. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Johannes Bauer <dfnsonfsduifb> |
Component: | [OLD] Development | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Johannes Bauer
2013-07-12 11:21:02 UTC
@Python herd: Any idea which action or python targets would satisfy this? If you think this needs a fix in scipy, then please assign to sci@g.o. A fix is required if it's broken. ~/cvsPortage/gentoo-x86/sci-libs/scipy $ PYTHON_TARGETS=python3_2 ebuild scipy-0.12.0.ebuild clean install testuser@archtester /mnt/gen2/TmpDir/portage/sci-libs/scipy-0.12.0/image/usr/lib64/python3.2/site-packages $ PYTHONPATH=. python3.2 -c "import scipy" yields blank meaning all is good. testuser@archtester /mnt/gen2/TmpDir/portage/sci-libs/scipy-0.12.0/image/usr/lib64/python3.2/site-packages $ PYTHONPATH=. python3.2 -c "from scipy.weave import build_tools" yields Traceback (most recent call last): File "<string>", line 1, in <module> File "scipy/weave/__init__.py", line 23, in <module> raise ImportError("scipy.weave only supports Python 2.x") ImportError: scipy.weave only supports Python 2.x This says I built scippy-0.12.0 just fine under py3.2, but a module build_tools spoils the party because it's there. Basically it can be conditionally deleted in a py3 emerge or build going from a similar outcome in some other package. As for a build failure under py3, I didn't get that. At least try an emerge --sync and retry. (In reply to Ian Delaney from comment #2) > As for a build failure under py3, I didn't get that. > At least try an emerge --sync and retry. Hmm, it appears you got further than me. Just synced the tree to timestamp "Tue, 23 Jul 2013 07:00:01 +0000" and still: emerge: there are no ebuilds built with USE flags to satisfy "virtual/python-imaging[python_targets_python2_5(-)?,python_targets_python2_6(-)?,python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,-python_single_target_python2_5(-),-python_single_target_python2_6(-),-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-)]". !!! One of the following packages is required to complete your request: - sci-libs/scipy-0.12.0::gentoo (Change USE: -python_targets_python3_2 -python_targets_python2_7, this change violates use flag constraints defined by sci-libs/scipy-0.12.0: 'any-of ( python_targets_python2_5 python_targets_python2_6 python_targets_python2_7 python_targets_python3_2 python_targets_python3_3 )') (dependency required by "sci-libs/scipy-0.12.0" [ebuild]) (dependency required by "scipy" [argument]) How can I track this down? I don't even understand the message completely, never seen that before. inherit python-r1 REQUIRED_USE=" python_targets_python2_5? ( !python_targets_python3_2 !python_targets_python3_3 ) " in virtual/python-imaging/python-imaging-1.ebuild makes for needing a PYTHON_TARGETS= 1 python target. Try; testuser@archtester ~/cvsPortage/gentoo-x86/app-emulation/xen-tools $ PYTHON_TARGETS=python2_6 emerge =sci-libs/scipy-0.12.0 -pv --- Invalid atom in /etc/portage/package.use: virtual/python-imaging-1 * Last emerge --sync was 38d 21h 51m 51s ago. These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] sci-libs/scipy-0.12.0 USE="-doc -sparse {-test}" PYTHON_TARGETS="python2_6 -python2_5 -python2_7* -python3_2 -python3_3" 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB * IMPORTANT: 15 news items need reading for repository 'gentoo'. * Use eselect news to read news items. I'm pretty sure I skirted emerge 20th July by building with sci-libs/scipy $ eebuild scipy-0.12.0.ebuild clean merge sci-libs/scipy $ PYTHON_TARGETS=python3_3 emerge =sci-libs/scipy-0.12.0 -pv --- Invalid atom in /etc/portage/package.use: virtual/python-imaging-1 * Last emerge --sync was 38d 21h 59m 31s ago. These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] sci-libs/scipy-0.12.0 USE="-doc -sparse {-test}" PYTHON_TARGETS="python3_3* -python2_5 -python2_6* -python2_7* -python3_2" 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB I see what you mean. You built the package manually, exluding the sanity checks that portage performs. With that, I can also successfully build the package: [/usr/portage/sci-libs/scipy]: ebuild scipy-0.12.0.ebuild clean merge Builds, installs and the resulting scipy pacakge works. However, I think this will come back to haunt me at the next system update, since: [/usr/portage/sci-libs/scipy]: emerge -pv scipy still spits out These are the packages that would be merged, in order: Calculating dependencies... done! emerge: there are no ebuilds built with USE flags to satisfy "virtual/python-imaging[python_targets_python2_5(-)?,python_targets_python2_6(-)?,python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,-python_single_target_python2_5(-),-python_single_target_python2_6(-),-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-)]". !!! One of the following packages is required to complete your request: - sci-libs/scipy-0.12.0::gentoo (Change USE: -python_targets_python3_2 -python_targets_python2_7, this change violates use flag constraints defined by sci-libs/scipy-0.12.0: 'any-of ( python_targets_python2_5 python_targets_python2_6 python_targets_python2_7 python_targets_python3_2 python_targets_python3_3 )') (dependency required by "sci-libs/scipy-0.12.0" [ebuild]) (dependency required by "scipy" [argument]) * IMPORTANT: 2 news items need reading for repository 'gentoo'. * Use eselect news to read news items. So, all in all, while I do now have a working scipy version thanks to you, the underlying problem is still not fixed (and likely going to cause trouble further down the road). It's really rather weird that this happens on my system, but not on yours. I cannot reproduce this. It was either fix on virtual/imaging level or I'm missing somthing. @Johannes is it still an issue? |