Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#17258 - [python-scipy] conflicts with arpack
Attached to Project:
Community Packages
Opened by sftrytry (sftrytry) - Monday, 23 November 2009, 20:14 GMT
Last edited by Angel Velasquez (angvp) - Thursday, 26 November 2009, 15:01 GMT
Opened by sftrytry (sftrytry) - Monday, 23 November 2009, 20:14 GMT
Last edited by Angel Velasquez (angvp) - Thursday, 26 November 2009, 15:01 GMT
|
DetailsDescription:
Compile scipy in ABS with arparck preinstalled, then you will get segment fault when running scipy.test() or using some arpack related functions. The pre-compiled python-scipy in the repos is fine, which, I think, is compiled without arpack. The problem only occurs you compile from source with arpack installed. I workarround solution is that, remove arpack, compile scipy in ABS, then install arpack again. Everything is fine. Additional info: * package version(s) * config and/or log files etc. python-scipy 0.7.1-3 arpack 2.1-3 Steps to reproduce: Just complie scipy in ABS with arparck installed in system. Then load python shell, import scipy and run scipy.test(). U will get segment fault around the non_symmetric eigen value testing. |
This task depends upon
Closed by Angel Velasquez (angvp)
Thursday, 26 November 2009, 15:01 GMT
Reason for closing: Not a bug
Additional comments about closing: The package itself has not a bug, we can't guess about segfaults by X packages installed on your system.
Thursday, 26 November 2009, 15:01 GMT
Reason for closing: Not a bug
Additional comments about closing: The package itself has not a bug, we can't guess about segfaults by X packages installed on your system.

Packages should be built in a clean chroot, so this isn't an issue actually. If the packages inside the repo haven't been built with arpack installed, then this is not a bug.