Created attachment 419376 [details] no-hardcode-blas.patch.out Hi guys, I have just synced my system in order to update the whole @world but I'm now stucked with dev-python/numpy. here's my output: ~# emerge numpy Calculating dependencies... done! >>> Verifying ebuild manifests >>> Emerging (1 of 1) dev-python/numpy-1.9.2::gentoo * numpy-1.9.2.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking numpy-1.9.2.tar.gz to /var/tmp/portage/dev-python/numpy-1.9.2/work >>> Source unpacked in /var/tmp/portage/dev-python/numpy-1.9.2/work >>> Preparing source in /var/tmp/portage/dev-python/numpy-1.9.2/work/numpy-1.9.2 ... * Applying numpy-1.9.2-no-hardcode-blas.patch ... * Failed Patch: numpy-1.9.2-no-hardcode-blas.patch ! * ( /usr/portage/dev-python/numpy/files/numpy-1.9.2-no-hardcode-blas.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/dev-python/numpy-1.9.2/temp/numpy-1.9.2-no-hardcode-blas.patch.out * ERROR: dev-python/numpy-1.9.2::gentoo failed (prepare phase): * Failed Patch: numpy-1.9.2-no-hardcode-blas.patch! * * Call stack: * ebuild.sh, line 90: Called src_prepare * environment, line 4220: Called distutils-r1_src_prepare * environment, line 1186: Called python_prepare_all * environment, line 3920: Called distutils-r1_python_prepare_all * environment, line 1092: Called epatch '/usr/portage/dev-python/numpy/files/numpy-1.9.2-no-hardcode-blas.patch' * environment, line 1560: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!"; * * If you need support, post the output of `emerge --info '=dev-python/numpy-1.9.2::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-python/numpy-1.9.2::gentoo'`. * The complete build log is located at '/var/tmp/portage/dev-python/numpy-1.9.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-python/numpy-1.9.2/temp/environment'. * Working directory: '/var/tmp/portage/dev-python/numpy-1.9.2/work/numpy-1.9.2' * S: '/var/tmp/portage/dev-python/numpy-1.9.2/work/numpy-1.9.2' >>> Failed to emerge dev-python/numpy-1.9.2, Log file: >>> '/var/tmp/portage/dev-python/numpy-1.9.2/temp/build.log' * Messages for package dev-python/numpy-1.9.2: * Failed Patch: numpy-1.9.2-no-hardcode-blas.patch ! * ( /usr/portage/dev-python/numpy/files/numpy-1.9.2-no-hardcode-blas.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/dev-python/numpy-1.9.2/temp/numpy-1.9.2-no-hardcode-blas.patch.out * ERROR: dev-python/numpy-1.9.2::gentoo failed (prepare phase): * Failed Patch: numpy-1.9.2-no-hardcode-blas.patch! * * Call stack: * ebuild.sh, line 90: Called src_prepare * environment, line 4220: Called distutils-r1_src_prepare * environment, line 1186: Called python_prepare_all * environment, line 3920: Called distutils-r1_python_prepare_all * environment, line 1092: Called epatch '/usr/portage/dev-python/numpy/files/numpy-1.9.2-no-hardcode-blas.patch' * environment, line 1560: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!"; * * If you need support, post the output of `emerge --info '=dev-python/numpy-1.9.2::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-python/numpy-1.9.2::gentoo'`. * The complete build log is located at '/var/tmp/portage/dev-python/numpy-1.9.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-python/numpy-1.9.2/temp/environment'. * Working directory: '/var/tmp/portage/dev-python/numpy-1.9.2/work/numpy-1.9.2' * S: '/var/tmp/portage/dev-python/numpy-1.9.2/work/numpy-1.9.2' ~# uname -a Linux ben 4.1.12-gentoo #1 SMP Tue Dec 15 17:21:39 CET 2015 x86_64 Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz GenuineIntel GNU/Linux
Created attachment 419378 [details] emerge --info '=dev-python/numpy-1.9.2::gentoo' emerge --info '=dev-python/numpy-1.9.2::gentoo'
Created attachment 419380 [details] emerge -pqv '=dev-python/numpy-1.9.2::gentoo' emerge -pqv '=dev-python/numpy-1.9.2::gentoo'
Created attachment 419382 [details] build.log build.log
Created attachment 419384 [details] environment environment
I hit the same problem this morning...decided to work around it by adding "dev-python/numpy ~*" to /etc/portage/accept_keywords. numpy-1.10.2-r1 is building without issue.
Confirmed. Workaround on accept_keywords works nice. Probably 1.10.2-r1 doesn't have that patch and it emerges fine, I have previously tried 1.8.2 and 1.9.2 but they have the same problem, 1.10 it's fine. I can revert back to 1.8 if some devel wants to make some tests with it. Ben
Confirmed - same here.
commit 825d57bd12b8538ad1f42b26348966c81776a622 Author: Justin Lecher <jlec@gentoo.org> Date: Thu Dec 17 18:14:49 2015 +0100 dev-python/numpy: Revert accidental change to patch Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=568454 Package-Manager: portage-2.2.26 Signed-off-by: Justin Lecher <jlec@gentoo.org> https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=825d57bd12b8538ad1f42b26348966c81776a622
