[Pkg-javascript-devel] Bug#954646: node-fbjs: FTBFS: ln: failed to create symbolic link 'packages/fbjs/node_modules/4': File exists

[Lucas Nussbaum]

Source: node-fbjs
Version: 1.0.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> mkdir -p packages/fbjs/node_modules
> for f in `ls -s debian/build_modules`; do \
> 	ln -s ../../../debian/build_modules/$f packages/fbjs/node_modules/$f; \
> done
> ln: failed to create symbolic link 'packages/fbjs/node_modules/4': File exists
> cd packages/fbjs && gulp build
> [03:11:46] Local gulp not found in /<<PKGBUILDDIR>>/packages/fbjs
> [03:11:46] Try running: npm install gulp
> [03:11:46] Using globally installed gulp
> internal/modules/cjs/loader.js:638
>     throw err;
>     ^
> 
> Error: Cannot find module 'merge-stream'
>     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
>     at Function.Module._load (internal/modules/cjs/loader.js:562:25)
>     at Module.require (internal/modules/cjs/loader.js:692:17)
>     at require (internal/modules/cjs/helpers.js:25:18)
>     at Object.<anonymous> (/<<PKGBUILDDIR>>/packages/fbjs/gulpfile.js:14:21)
>     at Module._compile (internal/modules/cjs/loader.js:778:30)
>     at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
>     at Module.load (internal/modules/cjs/loader.js:653:32)
>     at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
>     at Function.Module._load (internal/modules/cjs/loader.js:585:3)
> make[1]: *** [debian/rules:13: override_dh_auto_build] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/node-fbjs_1.0.0-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.