Package: python-scipy Version: 0.10.1+dfsg1-3 Severity: wishlist While troubleshooting FTBFS of statsmodels on sparc we just ran into an issue which points to scipy (separate report will be filed whenever confirmed to be scipy-origin). I have looked at scipy build-log [1] and besides build-depends on python-nose I saw no sign of it actually running unittests (full or not) against supported versions of python. If it is so -- it would be great to enable at least minimal package-time build-testing -- it would help to robustify scipy and dependent Python modules across platforms. IMHO it is better to detect/fixed bugs before they get discovered by others (users and maitainers of dependent packages).
[1] https://buildd.debian.org/status/fetch.php?pkg=python-scipy&arch=sparc&ver=0.10.1%2Bdfsg1-3&stamp=1335214019 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-scipy depends on: ii libamd2.2.0 1:3.4.0-2 ii libblas3gf [libblas.so.3gf] 1.2.20110419-2 ii libc6 2.13-18 ii libgcc1 1:4.7.0-1 ii libgfortran3 4.7.0-1 ii liblapack3gf [liblapack.so.3gf] 3.3.1-1 ii libquadmath0 4.7.0-1 ii libstdc++6 4.7.0-1 ii libumfpack5.4.0 1:3.4.0-2 ii python 2.7.2-10 ii python-numpy [python-numpy-abi9] 1:1.6.2-1 ii python2.6 2.6.7-4 ii python2.7 2.7.3~rc2-2.1 Versions of packages python-scipy recommends: ii g++ [c++-compiler] 4:4.6.2-4 ii g++-4.4 [c++-compiler] 4.4.7-1 ii g++-4.6 [c++-compiler] 4.6.3-1 ii python-dev 2.7.2-10 ii python-imaging 1.1.7-4 Versions of packages python-scipy suggests: ii python [python-profiler] 2.7.2-10 -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
