[Pkg-javascript-devel] Bug#1082992: node-http-server: FTBFS: TypeError: util.puts is not a function
Santiago Vila
sanvila at debian.org
Sun Sep 29 19:07:49 BST 2024
Package: src:node-http-server
Version: 14.1.1+~cs3.14.34-4
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
--------------------------------------------------------------------------------
[...]
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
dh_auto_configure --buildsystem=nodejs
Link node_modules/corser -> ../corser
Link node_modules/eol -> ../eol
Link node_modules/portfinder -> ../portfinder
Link node_modules/union -> ../union
dh_auto_build --buildsystem=nodejs
No build command found, searching known files
No build command found, searching known files
No build command found, searching known files
No build command found, searching known files
No build command found, searching known files
dh_auto_test --buildsystem=nodejs
ln -s ../. node_modules/http-server
cd ./corser && sh -ex ../debian/nodejs/corser/test
+ mocha
Corser
undefined should not add any headers if the "Origin" header is not present in the request
undefined should not add any headers if the given origin does not match one of the origins in the list of origins
undefined should support passing a function as origins and it should work both synchronously and asynchronously
undefined should not accept any non-boolean value as the second parameter of an match origin callback
undefined should expose errors encountered in the match origin callback
undefined should not add any headers if the given origin is not a case-sentitive match of one of the origins in the list of origins
An actual request
undefined should add an Access-Control-Allow-Origin header of "*" for any given origin if the list of origins in unbound
undefined should add an Access-Control-Allow-Origin header of "example.com" if the given origin matches one of the origins in the list of origins
undefined should add an Access-Control-Allow-Origin header of "example.com" and an Access-Control-Allow-Credentials header of "true" if credentials are supported and the list of origins in unbound
undefined should add an Access-Control-Allow-Origin header of "example.com" and an Access-Control-Allow-Credentials header of "true" if credentials are supported and the given origin matches one of the origins in the list of origins
undefined should not add an Access-Control-Allow-Headers header if there are no response headers to expose
undefined should add an Access-Control-Expose-Headers header with all the exposed response headers if there are response headers to expose
A preflight request
undefined should not add any headers if an Access-Control-Request-Method header is not present in the request
undefined should not add any headers if the Access-Control-Request-Method header contains a non-simple method
undefined should not add any headers if the Access-Control-Request-Headers header contains a non-simple request header
undefined should add an Access-Control-Allow-Origin header of "*" for any given origin if the list of origins in unbound
undefined should add an Access-Control-Allow-Origin header of "example.com" if the given origin matches one of the origins in the list of origins
undefined should add an Access-Control-Allow-Origin header of "example.com" and an Access-Control-Allow-Credentials header of "true" if credentials are supported and the list of origins in unbound
undefined should add an Access-Control-Allow-Origin header of "example.com" and an Access-Control-Allow-Credentials header of "true" if credentials are supported and the given origin matches one of the origins in the list of origins
undefined should add an Access-Control-Allow-Origin header even though Origin was not added to the list of request headers
undefined should add an Access-Control-Max-Age header of "50" if maxAge is set
undefined should add an Access-Control-Allow-Methods header with all methods that are in the list of methods
undefined should add an Access-Control-Allow-Headers header with all request headers that are in the list of request headers
undefined should add an Access-Control-Allow-Headers header that includes x-corser even though the name of the header in the Access-Control-Request-Headers header is not a case-sensitive match
undefined should end preflight requests by default
25 passing (22ms)
cd ./portfinder && sh -ex ../debian/nodejs/portfinder/test
+ vows test/port-finder-multiple-test.js test/port-finder-socket-test.js test/port-finder-test.js test/port-finder-z-integration-test.js --spec
♢ portfinder
/usr/share/nodejs/vows/lib/vows.js:208
util.puts(console.result(results));
^
TypeError: util.puts is not a function
at process.<anonymous> (/usr/share/nodejs/vows/lib/vows.js:208:14)
at process.emit (node:events:519:28)
at options.Emitter.emit (/usr/share/nodejs/vows/lib/vows.js:241:24)
Node.js v20.17.0
dh_auto_test: error: cd ./portfinder && sh -ex ../debian/nodejs/portfinder/test returned exit code 1
make: *** [debian/rules:8: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:
https://people.debian.org/~sanvila/build-logs/202409/
About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.
If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks.
More information about the Pkg-javascript-devel
mailing list