[Pkg-javascript-devel] Bug#1006069: node-browser-stdout: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.

[Lucas Nussbaum]

Source: node-browser-stdout
Version: 1.3.1-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>    dh_update_autotools_config
>    dh_autoreconf
>    dh_auto_configure --buildsystem=nodejs
>    dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>    dh_auto_test --buildsystem=nodejs
> 	mkdir -p node_modules
> 	ln -s ../. node_modules/browser-stdout
> 	/usr/bin/node -e require\(\"./.\"\)
> Removing node_modules/browser-stdout
>    create-stamp debian/debhelper-build-stamp
>    dh_prep
>    dh_auto_install --buildsystem=nodejs --destdir=debian/node-browser-stdout/
> dh_auto_install: warning: ### Missing ./build/config.gypi, skipping
> 
> No "files" field in ./package.json, install all files
> Files to install: ., !./build/config.gypi
> 	mkdir -p /<<PKGBUILDDIR>>/debian/node-browser-stdout//usr/share/nodejs/browser-stdout/
> 	install -m 644 ./package.json /<<PKGBUILDDIR>>/debian/node-browser-stdout//usr/share/nodejs/browser-stdout//
> 	install -m 644 ./index.js /<<PKGBUILDDIR>>/debian/node-browser-stdout//usr/share/nodejs/browser-stdout//
> 	install -m 644 ./package.json /<<PKGBUILDDIR>>/debian/node-browser-stdout//usr/share/nodejs/browser-stdout//
> Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.
> make: *** [debian/rules:8: binary] Error 255


The full build log is available from:
http://qa-logs.debian.net/2022/02/18/node-browser-stdout_1.3.1-5_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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.