Your message dated Wed, 21 Feb 2018 12:17:12 -0500
with message-id <20180221171712.gh3...@hopa.kiewit.dartmouth.edu>
and subject line Re: Bug#868916: nipy: FTBFS: ld: cannot find -lcblas
has caused the Debian Bug report #868916,
regarding nipy: FTBFS: ld: cannot find -lcblas
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
868916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nipy
Version: 0.4.0+git26-gf8d3149-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> x86_64-linux-gnu-gcc -pthread /tmp/tmpQbIMed/tmp/tmpQbIMed/source.o -lcblas
> -o /tmp/tmpQbIMed/a.out
> /usr/bin/ld: cannot find -lcblas
> collect2: error: ld returned 1 exit status
The full build log is available from:
http://aws-logs.debian.net/2017/07/19/nipy_0.4.0+git26-gf8d3149-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 0.4.2-1
It seems that nipy builds fine across all architectures
https://buildd.debian.org/status/package.php?p=nipy
so this issue could be marked out as resolved
On Sun, 05 Nov 2017, peter green wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> The good news is that this particular build failure seems to have been
> fixed in the most recent upload to sid.
> The bad news is that when binnmuing for the python2.7 removal of "fpectl"
> symbols the package failed with a test suite failure
> There also seems to be a build-timeout issue on armel, I dunno if that was
> a one-off glitch or something more serious.
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
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
--- End Message ---
