pyentropy version 0.4-1 failed to build in oneiric

Bug #835744 reported by Matthias Klose
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pyentropy (Ubuntu)
Fix Released
High
Unassigned
Oneiric
Fix Released
High
Unassigned

Bug Description

pyentropy version 0.4-1 failed to build in oneiric
Link to failed build: https://launchpad.net/ubuntu/+archive/test-rebuild-20110816/+build/2709006

Details about the rebuild:
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110816-oneiric.html

Direct link to the build log: https://launchpad.net/ubuntu/+archive/test-rebuild-20110816/+build/2709006/+files/buildlog_ubuntu-oneiric-i386.pyentropy_0.4-1_FAILEDTOBUILD.txt.gz

This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'.
Excerpt 567 lines into the build log:

  File "/usr/lib/python2.7/dist-packages/scipy/sparse/base.py", line 384, in __getattr__
    raise AttributeError(attr + " not found")
AttributeError: matvec not found

----------------------------------------------------------------------
Ran 29 tests in 2.028s

FAILED (errors=4)
Order 1 complete. Time: Sat Aug 27 11:55:41 2011
Order 2 complete. Time: Sat Aug 27 11:55:41 2011
Order 3 complete. Time: Sat Aug 27 11:55:41 2011
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory `/build/buildd/pyentropy-0.4'
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
******************************************************************************
Build finished at 20110827-1155
FAILED [dpkg-buildpackage died]
Purging chroot-autobuild/build/buildd/pyentropy-0.4

Matthias Klose (doko)
Changed in pyentropy (Ubuntu):
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Julian Taylor (jtaylor) wrote :

fixed by 0.4-1.1
sync request: 836343

Revision history for this message
Matthias Klose (doko) wrote :

synced

Changed in pyentropy (Ubuntu Oneiric):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.