[Pkg-javascript-devel] Bug#897545: node-bluebird: FTBFS: cp: cannot stat '/<<BUILDDIR>>/node-bluebird-3.5.1+dfsg2/js/release/*': No such file or directory

Lucas Nussbaum lucas at debian.org
Wed May 2 21:52:35 BST 2018


Source: node-bluebird
Version: 3.5.1+dfsg2-1
Severity: serious
Tags: buster sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20180502 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):
> make[1]: Entering directory '/<<BUILDDIR>>/node-bluebird-3.5.1+dfsg2'
> # Use the Debian built release of bluebird for tests
> mkdir -p /<<BUILDDIR>>/node-bluebird-3.5.1+dfsg2/node_modules/bluebird/js/release
> cp /<<BUILDDIR>>/node-bluebird-3.5.1+dfsg2/js/release/* /<<BUILDDIR>>/node-bluebird-3.5.1+dfsg2/node_modules/bluebird/js/release/
> cp: cannot stat '/<<BUILDDIR>>/node-bluebird-3.5.1+dfsg2/js/release/*': No such file or directory
> make[1]: *** [debian/rules:24: override_dh_auto_test] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2018/05/02/node-bluebird_3.5.1+dfsg2-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.



More information about the Pkg-javascript-devel mailing list