Thanks known issue of compatibility with recently uploaded nibabel 1.2.0... Will be fixed with an upcoming upstream release I am waiting for... otherwise (if doesn't come soon) I will patch
Cheers, On Sat, 19 May 2012, Samuel Thibault wrote: > Source: nipy > Version: 0.1.999-2 > Severity: serious > Justification: FTBFS > Hello, > nipy currently FTBFS in sid: > Ran 4832 tests in 471.162s > FAILED (SKIP=5, failures=2) > FAIL: Doctest: nipy.core.image.image_spaces > File > "/tmp/buildd/nipy-0.1.999/debian/tmp/usr/lib/python2.7/dist-packages/nipy/core/image/image_spaces.py", > line 52, in nipy.core.image.image_spaces > Failed example: > xyz_affine(nimg) > Expected: > array([[2, 0, 0, 0], > [0, 3, 0, 0], > [0, 0, 4, 0], > [0, 0, 0, 1]]) > Got: > array([[ 2., 0., 0., 0.], > [ 0., 3., 0., 0.], > [ 0., 0., 4., 0.], > [ 0., 0., 0., 1.]]) > FAIL: Doctest: nipy.core.image.image_spaces.xyz_affine > File > "/tmp/buildd/nipy-0.1.999/debian/tmp/usr/lib/python2.7/dist-packages/nipy/core/image/image_spaces.py", > line 115, in nipy.core.image.image_spaces.xyz_affine > Failed example: > xyz_affine(nimg) > Expected: > array([[2, 0, 0, 0], > [0, 3, 0, 0], > [0, 0, 4, 0], > [0, 0, 0, 1]]) > Got: > array([[ 2., 0., 0., 0.], > [ 0., 3., 0., 0.], > [ 0., 0., 4., 0.], > [ 0., 0., 0., 1.]]) > It seems the formatting has simply changed somewhere. > See attached full log. > Samuel -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
