Source: node-topcube
Version: 0.1.2+ds1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130811 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Maybe this is related to that as of node.js v0.8 node-waf was removed
and replaced with node-gyp (packaged independently).
Relevant part (hopefully):
> debian/rules build
> dh build
> dh_testdir
> dh_auto_configure
> ./configure: 2: ./configure: node-waf: not found
> dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr
> --includedir=${prefix}/include --mandir=${prefix}/share/man
> --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
> --libexecdir=${prefix}/lib/node-topcube --disable-maintainer-mode
> --disable-dependency-tracking returned exit code 127
> make: *** [build] Error 2
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2013/08/11/node-topcube_0.1.2+ds1-1_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.
_______________________________________________
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
