[Pkg-javascript-devel] Bug#1068750: moment-timezone.js: FTBFS everywhere

2024-04-30 Thread Santiago Vila

# Fail the build if the tzdata package does not match TZVER.
grep -q '^# version 2023d$' /usr/share/zoneinfo/tzdata.zi


Yes, this is expected after each update to tzdata.


I'm curious: Does this package embed the information from tzdata into 
javascript code,
in such a way that a change in tzdata requires a rebuild?


Yes. It is the only way I found to keep the package aligned with tzdata while 
ensuring it is fully built from source: upstream ships the pre-compiled tzdata 
information, so I regenerate those files using the tzdata package.


I think it would be highly desirable to find a way for this package to do what
it's supposed to do without having to fix it in oldstable and stable every year.


Without a new upload, I cannot imagine how.. :-/


(In fact, I asked Paul Gevers about this, he says that a package which we know
for sure that it will fail to build during the support time of the release is 
RC).


It fails to build if tzdata is updated, but it never stops working. It just 
needs to be updated as often as tzdata is. But if you have a suggestion to make 
this more automatic, I would love to hear it..


Sorry, I still don't get it.

Why does the package build needs to fail if tzdata is updated?

What happens if we allow the package to be built anyway?
(as in the attached patch).

Would the resulting package be broken in any way?


I have been doing this very repetitive maintenance for years!


Well, I get that you have to make a new upload so that the package is current.
What I don't get is that the package fails to build. At most, it would result
in an improved package, not worse. Or maybe I'm missing anything.

Thanks.--- a/debian/control
+++ b/debian/control
@@ -10,6 +10,7 @@ Build-Depends: debhelper-compat (= 13)
  , dh-sequence-nodejs
  , uglifyjs
  , ts-node 
+ , tzdata (>= 2024a)
  , tzdata-legacy (>= 2024a)
 Standards-Version: 4.6.2
 Vcs-Browser: https://salsa.debian.org/js-team/moment-timezone.js
--- a/debian/rules
+++ b/debian/rules
@@ -23,10 +23,6 @@ all: binary
 %:
dh $@
 
-execute_before_dh_auto_configure:
-   # Fail the build if the tzdata package does not match TZVER.
-   grep -q '^# version $(TZVER)$$' /usr/share/zoneinfo/tzdata.zi
-
 override_dh_auto_build: $(TARGETS)
 
 execute_before_dh_auto_test: tests/zones/zulu.js
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel


[Pkg-javascript-devel] Bug#1017811: node-wikibase-cli: FTBFS without Internet access

2024-04-26 Thread Santiago Vila

I have commented out a pair of test cases which attempted network access in the 
upload of node-wikibase-cli 15.15.4-5. Could you please check whether FTBFS 
continues?


Hello. Yes, it continues to fail.

You can tell by looking at the reproducible-builds page for the package:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-wikibase-cli.html

because packages trying to use the network fail in reproducible-builds.

Another way to tell is by using the unshare backend of sbuild:

https://wiki.debian.org/sbuild#Using_unshare_with_mmdebstrap_.28no_root_needed.29

The unshare backend also makes packages like this to fail (this is how I arrived
at this report, I'm currently helping Jochen to build the whole archive using 
the unshare backend).

Thanks.

--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel


[Pkg-javascript-devel] Bug#1069888: node-bunyan: FTBFS: failing tests

2024-04-26 Thread Santiago Vila

Package: src:node-bunyan
Version: 2.0.5+~cs4.4.3-2
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/exeunt -> ../exeunt
Link node_modules/mv -> ../mv
Link node_modules/safe-json-stringify -> ../safejsonstringify
   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
   dh_auto_test --buildsystem=nodejs
ln -s ../. node_modules/bunyan
/bin/sh -ex debian/tests/pkg-js/test
+ tap -R tap -J --no-cov test/add-stream.test.js test/buffer.test.js 
test/child-behaviour.test.js test/cli-client-req.test.js test/cli-res.test.js 
test/cli.test.js test/ctor.test.js test/cycles.test.js test/error-event.test.js 
test/level.test.js test/log.test.js test/other-api.test.js 
test/process-exit.test.js test/raw-stream.test.js test/ringbuffer.test.js 
test/safe-json-stringify.test.js test/serializers.test.js test/src.test.js 
test/stream-levels.test.js
TAP version 13
# Subtest: test/add-stream.test.js
# Subtest: non-writables passed as stream
ok 1 - "stream" stream is not writable
ok 2 - "stream" stream is not writable
1..2
ok 1 - non-writables passed as stream # time=18.713ms

# Subtest: proper stream

ok 1 - expect truthy value
1..1
ok 2 - proper stream # time=4.908ms

1..2

# time=46.964ms
ok 1 - test/add-stream.test.js # time=46.964ms

# Subtest: test/buffer.test.js
# Subtest: log.info(BUFFER)
ok 1 - log.trace msg is inspect(BUFFER)
ok 2 - no "0" array index key in record: undefined
ok 3 - no "parent" array index key in record: undefined
ok 4 - log.trace(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
ok 5 - log.debug msg is inspect(BUFFER)
ok 6 - no "0" array index key in record: undefined
ok 7 - no "parent" array index key in record: undefined
ok 8 - log.debug(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
ok 9 - log.info msg is inspect(BUFFER)
ok 10 - no "0" array index key in record: undefined
ok 11 - no "parent" array index key in record: undefined
ok 12 - log.info(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
ok 13 - log.warn msg is inspect(BUFFER)
ok 14 - no "0" array index key in record: undefined
ok 15 - no "parent" array index key in record: undefined
ok 16 - log.warn(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
ok 17 - log.error msg is inspect(BUFFER)
ok 18 - no "0" array index key in record: undefined
ok 19 - no "parent" array index key in record: undefined
ok 20 - log.error(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
ok 21 - log.fatal msg is inspect(BUFFER)
ok 22 - no "0" array index key in record: undefined
ok 23 - no "parent" array index key in record: undefined
ok 24 - log.fatal(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
1..24
ok 1 - log.info(BUFFER) # time=15.595ms

1..1

# time=36.998ms
ok 2 - test/buffer.test.js # time=36.998ms

# Subtest: test/child-behaviour.test.js
# Subtest: child can add stream
ok 1 - should be equal
ok 2 - should be equal
ok 3 - should be equal
ok 4 - should be equal
1..4
ok 1 - child can add stream # time=8.798ms

# Subtest: child can set level of inherited streams

ok 1 - should be equal
ok 2 - should be equal
ok 3 - should be equal
1..3
ok 2 - child can set level of inherited streams # time=2.496ms

# Subtest: child can set level of inherited streams and add streams

ok 1 - should be equal
ok 2 - should be equal
ok 3 - should be equal
ok 4 - should be equal
ok 5 - should be equal
ok 6 - should be equal
1..6
ok 3 - child can set level of inherited streams and add streams # 
time=5.594ms

# Subtest: child should not lose parent "hostname"

ok 1 - should be equal
ok 2 - should be equal
ok 3 - should be equal
ok 4 - should be equal
1..4
ok 4 - child should not lose parent "hostname" # time=1.888ms

1..4

# time=43.011ms
ok 3 - test/child-behaviour.test.js # time=43.011ms

(node:558561) DeprecationWarning: ifError() is deprecated, use error() instead
(Use `node --trace-deprecation ...` to show where the warning was created)
# Subtest: test/cli-client-req.test.js
# Subtest: client_req extra newlines, client_res={} (pull \#252)
ok 1 - should not error
ok 2 - should be equal

[Pkg-javascript-devel] Bug#1068750: moment-timezone.js: FTBFS everywhere

2024-04-10 Thread Santiago Vila

Package: src:moment-timezone.js
Version: 0.5.32+dfsg1-2+2021a
Severity: serious
Tags: bullseye bookworm trixie sid ftbfs

Dear maintainer:

This package currently fails to build from source in all supported 
distributions.

make[1]: Leaving directory '/<>'
   dh_clean
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   debian/rules execute_before_dh_auto_configure
make[1]: Entering directory '/<>'
# Fail the build if the tzdata package does not match TZVER.
grep -q '^# version 2023d$' /usr/share/zoneinfo/tzdata.zi
make[1]: *** [debian/rules:28: execute_before_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:24: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

See also:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/moment-timezone.js.html

I'm curious: Does this package embed the information from tzdata into 
javascript code,
in such a way that a change in tzdata requires a rebuild?

I think it would be highly desirable to find a way for this package to do what
it's supposed to do without having to fix it in oldstable and stable every year.

(In fact, I asked Paul Gevers about this, he says that a package which we know
for sure that it will fail to build during the support time of the release is 
RC).

Thanks.

--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel


[Pkg-javascript-devel] Bug#1067797: node-y-protocols: FTBFS: error TS2307: Cannot find module 'undici-types' or its corresponding type declarations.

2024-03-26 Thread Santiago Vila

Package: src:node-y-protocols
Version: 1.0.5-7
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --with nodejs --buildsystem=nodejs
   dh_update_autotools_config -O--buildsystem=nodejs
   dh_autoreconf -O--buildsystem=nodejs
   dh_auto_configure --buildsystem=nodejs -O--buildsystem=nodejs
Link ./node_modules/@rollup/plugin-commonjs -> 
/usr/share/nodejs/@rollup/plugin-commonjs
Link ./node_modules/@rollup/plugin-node-resolve -> 
/usr/share/nodejs/@rollup/plugin-node-resolve
Copy /usr/share/nodejs/lib0 -> ./node_modules/
cp: cannot overwrite non-directory './node_modules/@rollup/plugin-node-resolve' 
with directory '/usr/share/nodejs/@rollup/plugin-node-resolve'
Copy /usr/share/nodejs/@rollup/plugin-node-resolve -> ./node_modules/@rollup
Copy /usr/share/nodejs/@rollup/pluginutils -> ./node_modules/@rollup
Copy /usr/share/nodejs/rollup -> ./node_modules/
cp: cannot overwrite non-directory './node_modules/@rollup/plugin-commonjs' 
with directory '/usr/share/nodejs/@rollup/plugin-commonjs'
Copy /usr/share/nodejs/@rollup/plugin-commonjs -> ./node_modules/@rollup
Copy /usr/share/nodejs/@types/node -> ./node_modules/@types
Not found
### @types/undici-types is required by debian/nodejs/./extcopies but not 
available
# Typescript definition detected, Fallback to main module
### You SHOULD update your debian/nodejs/./extcopies file!
Copy /usr/share/nodejs/yjs -> ./node_modules/
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
tsc --outDir .
node_modules/@types/node/ts4.8/globals.d.ts(325,84): error TS2307: Cannot find 
module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(326,85): error TS2307: Cannot find 
module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(327,85): error TS2307: Cannot find 
module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(328,84): error TS2307: Cannot find 
module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(330,22): error TS2307: Cannot find 
module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(336,35): error TS2307: Cannot find 
module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(337,35): error TS2307: Cannot find 
module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(338,32): error TS2307: Cannot find 
module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(339,39): error TS2307: Cannot find 
module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(340,42): error TS2307: Cannot find 
module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(341,35): error TS2307: Cannot find 
module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(342,38): error TS2307: Cannot find 
module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(343,34): error TS2307: Cannot find 
module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(344,37): error TS2307: Cannot find 
module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(360,21): error TS2307: Cannot find 
module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(367,21): error TS2307: Cannot find 
module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(374,21): error TS2307: Cannot find 
module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(381,21): error TS2307: Cannot find 
module 'undici-types' or its corresponding type declarations.
make[1]: *** [debian/rules:11: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: binary] Error 2
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/202403/

About the archive rebuild: The build was made on virtual machines
of type m6a.large 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 

[Pkg-javascript-devel] Bug#1057934: libjs-jquery-jstree: FTBFS: dh_debputy: error: debputy internal-command dh-integration-generate-debs -p libjs-jquery-jstree .. returned exit code 1

2023-12-10 Thread Santiago Vila

Package: src:libjs-jquery-jstree
Version: 3.3.16+dfsg1-1
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
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
cp debian/build.js build.js
nodejs /usr/share/nodejs/requirejs/r.js -o build.js

Tracing dependencies for: jstree

/<>/dist/jstree.js

/<>/src/jstree.js
/<>/src/jstree.changed.js
/<>/src/jstree.checkbox.js
/<>/src/jstree.conditionalselect.js
/<>/src/jstree.contextmenu.js
/<>/src/jstree.dnd.js
/<>/src/jstree.massload.js
/<>/src/jstree.search.js
/<>/src/jstree.sort.js
/<>/src/jstree.state.js
/<>/src/jstree.types.js
/<>/src/jstree.unique.js
/<>/src/jstree.wholerow.js
/<>/src/vakata-jstree.js

sed -i -e 's/{{VERSION}}/3.3.16+dfsg1/' dist/jstree.js
Checking syntax of dist/jstree.js ...
uglifyjs dist/jstree.js --output dist/jstree.min.js --compress
dh_auto_build
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
nodejs --check dist/jstree.js
nodejs --check dist/jstree.min.js
make[1]: Leaving directory '/<>'
   create-stamp debian/debhelper-build-stamp
   dh_prep
   dh_auto_install --destdir=debian/libjs-jquery-jstree/
   dh_debputy
Internal error in debputy
  - 8<  BEGIN STACK TRACE  8< -
Traceback (most recent call last):
  File "/usr/share/dh-debputy/debputy/commands/debputy_cmd.py", line 2082, in 
main
command.handler(cmd_context)
  File "/usr/share/dh-debputy/debputy/commands/debputy_cmd.py", line 1133, in 
_dh_integration_generate_debs
intermediate_manifest = manifest.finalize_data_tar_contents(

  File "/usr/share/dh-debputy/debputy/highlevel_manifest.py", line 1177, in 
finalize_data_tar_contents
intermediate_manifest = list(
^
  File "/usr/share/dh-debputy/debputy/highlevel_manifest.py", line 180, in 
_generate_intermediate_manifest
tar_member = _path_to_tar_member(path, clamp_mtime_to)
 ^
  File "/usr/share/dh-debputy/debputy/highlevel_manifest.py", line 159, in 
_path_to_tar_member
return TarMember.from_file(
   
  File "/usr/share/dh-debputy/debputy/intermediate_manifest.py", line 147, in 
from_file
"debputy/scratch_dir/" in fs_path
AssertionError: README.md should not have been stealable
  - 8<  END STACK TRACE  8< -
Please file a bug against debputy with the full output.
README.md should not have been stealable
dh_debputy: error: debputy internal-command dh-integration-generate-debs -p 
libjs-jquery-jstree .. returned exit code 1
make: *** [debian/rules:34: 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/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using 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.

--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel


[Pkg-javascript-devel] Bug#1057585: node-strip-bom-stream: FTBFS: not ok 2 TypeError: getStream is not a function

2023-12-05 Thread Santiago Vila

Package: src:node-strip-bom-stream
Version: 4.0.0-2
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/is-utf8 -> ../is-utf8
Link node_modules/strip-bom-buf -> ../strip-bom-buf
   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
   dh_auto_test --buildsystem=nodejs
ln -s ../. node_modules/strip-bom-stream
/bin/sh -ex debian/tests/pkg-js/test
+ tape test.js
TAP version 13
# main
not ok 1 TypeError: getStream is not a function
  ---
operator: error
stack: |-
  TypeError: getStream is not a function
  at Test. (/<>/test.js:7:23)
  at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Test.run (/usr/share/nodejs/tape/lib/test.js:115:28)
  at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Immediate.next (/usr/share/nodejs/tape/lib/results.js:157:7)
  at process.processImmediate (node:internal/timers:476:21)
  ...
# low `highWaterMark`
not ok 2 TypeError: getStream is not a function
  ---
operator: error
stack: |-
  TypeError: getStream is not a function
  at Test. (/<>/test.js:13:23)
  at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Test.run (/usr/share/nodejs/tape/lib/test.js:115:28)
  at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Immediate.next (/usr/share/nodejs/tape/lib/results.js:157:7)
  at process.processImmediate (node:internal/timers:476:21)
  ...

1..2
# tests 2
# pass  0
# fail  2

dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/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/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using 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.

--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel


[Pkg-javascript-devel] Bug#1057584: node-qs: FTBFS: Error: module has-proto in /<>/node_modules/get-intrinsic not found

2023-12-05 Thread Santiago Vila

Package: src:node-qs
Version: 6.11.0+ds+~6.9.7-3
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/available-typed-arrays -> 
/usr/share/nodejs/available-typed-arrays
Link ./node_modules/call-bind -> /usr/share/nodejs/call-bind
Link ./node_modules/es-abstract -> /usr/share/nodejs/es-abstract
Link ./node_modules/for-each -> /usr/share/nodejs/for-each
Link ./node_modules/function-bind -> /usr/share/nodejs/function-bind
Link ./node_modules/get-intrinsic -> /usr/share/nodejs/get-intrinsic
Link ./node_modules/gopd -> /usr/share/nodejs/gopd
Link ./node_modules/has-symbols -> /usr/share/nodejs/has-symbols
Link ./node_modules/has -> /usr/share/nodejs/has
Link ./node_modules/has-tostringtag -> /usr/share/nodejs/has-tostringtag
Link ./node_modules/inherits -> /usr/share/nodejs/inherits
Link ./node_modules/is-arguments -> /usr/share/nodejs/is-arguments
Link ./node_modules/is-callable -> /usr/share/nodejs/is-callable
Link ./node_modules/is-generator-function -> 
/usr/share/nodejs/is-generator-function
Link ./node_modules/is-typed-array -> /usr/share/nodejs/is-typed-array
Link ./node_modules/object-inspect -> /usr/share/nodejs/object-inspect
Link ./node_modules/side-channel -> /usr/share/nodejs/side-channel
Link ./node_modules/util -> /usr/share/nodejs/util
Link ./node_modules/which-typed-array -> /usr/share/nodejs/which-typed-array
Link node_modules/@types/qs -> ../../types-qs
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
mkdir dist
browserify-lite ./lib/index.js --outfile dist/qs.js
/usr/share/nodejs/browserify-lite/cli.js:29
  if (err) throw err;
   ^

Error: module has-proto in /<>/node_modules/get-intrinsic not found
at trySearchPath (/usr/share/nodejs/browserify-lite/index.js:269:32)
at /usr/share/nodejs/browserify-lite/index.js:274:7
at /usr/share/nodejs/browserify-lite/index.js:294:21
at FSReqCallback.oncomplete (node:fs:202:21)

Node.js v18.19.0
make[1]: *** [debian/rules:13: override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: binary] Error 2
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/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using 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.

--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel


[Pkg-javascript-devel] Bug#1057583: node-gulp-changed: FTBFS: not ok 3 TypeError: getStream.array is not a function

2023-12-05 Thread Santiago Vila

Package: src:node-gulp-changed
Version: 4.0.3-2
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
   dh_auto_build --buildsystem=nodejs
No build command found, searching known files
   dh_auto_test --buildsystem=nodejs
mkdir -p node_modules
ln -s ../debian/tests/test_modules/figures node_modules/figures
ln -s ../debian/tests/test_modules/touch node_modules/touch
ln -s ../. node_modules/gulp-changed
/bin/sh -ex debian/tests/pkg-js/test
+ tape test.js
TAP version 13
# compareLastModifiedTime › using relative dest
# compareLastModifiedTime › using relative dest
# compareContents › should not pass any files through in identical directories
not ok 1 TypeError: getStream.array is not a function
  ---
operator: error
stack: |-
  TypeError: getStream.array is not a function
  at Test. (/<>/test.js:94:32)
  at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Test.run (/usr/share/nodejs/tape/lib/test.js:115:28)
  at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Immediate.next (/usr/share/nodejs/tape/lib/results.js:157:7)
  at process.processImmediate (node:internal/timers:476:21)
  ...
# compareContents › should only pass through changed files using file extension
not ok 2 TypeError: getStream.array is not a function
  ---
operator: error
stack: |-
  TypeError: getStream.array is not a function
  at Test. (/<>/test.js:102:32)
  at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Test.run (/usr/share/nodejs/tape/lib/test.js:115:28)
  at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Immediate.next (/usr/share/nodejs/tape/lib/results.js:157:7)
  at process.processImmediate (node:internal/timers:476:21)
  ...
# compareContents › should only pass through changed files using transformPath
not ok 3 TypeError: getStream.array is not a function
  ---
operator: error
stack: |-
  TypeError: getStream.array is not a function
  at Test. (/<>/test.js:117:32)
  at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Test.run (/usr/share/nodejs/tape/lib/test.js:115:28)
  at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Immediate.next (/usr/share/nodejs/tape/lib/results.js:157:7)
  at process.processImmediate (node:internal/timers:476:21)
  ...
# compareContents › should only pass through changed files using extension 
.coffee
not ok 4 TypeError: getStream.array is not a function
  ---
operator: error
stack: |-
  TypeError: getStream.array is not a function
  at Test. (/<>/test.js:129:32)
  at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Test.run (/usr/share/nodejs/tape/lib/test.js:115:28)
  at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Immediate.next (/usr/share/nodejs/tape/lib/results.js:157:7)
  at process.processImmediate (node:internal/timers:476:21)
  ...

1..4
# tests 4
# pass  0
# fail  4

dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/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/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using 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.

--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel


[Pkg-javascript-devel] Bug#1057582: node-decompress-response: FTBFS: not ok 13 TypeError: getStream is not a function

2023-12-05 Thread Santiago Vila

Package: src:node-decompress-response
Version: 6.0.0-2
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
   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/decompress-response
/bin/sh -ex debian/tests/pkg-js/test
+ tape test/test.js
TAP version 13
# decompress gzipped content
ok 1 should be truthy
ok 2 should be truthy
ok 3 should be truthy
ok 4 should be truthy
ok 5 should be truthy
ok 6 should be truthy
ok 7 should be truthy
ok 8 should be truthy
ok 9 should be truthy
ok 10 should be truthy
ok 11 should be truthy
ok 12 should be truthy
not ok 13 TypeError: getStream is not a function
  ---
operator: error
stack: |-
  TypeError: getStream is not a function
  at Test. (/<>/test/test.js:72:13)
  at process.processTicksAndRejections 
(node:internal/process/task_queues:95:5)
  ...
# decompress deflated content
node:events:495
  throw er; // Unhandled 'error' event
  ^

Error: listen EADDRINUSE: address already in use :::59060
at Server.setupListenHandle [as _listen2] (node:net:1811:16)
at listenInCluster (node:net:1859:12)
at Server.listen (node:net:1947:7)
at /usr/share/nodejs/pify/index.js:33:11
at new Promise ()
at Server. (/usr/share/nodejs/pify/index.js:6:9)
at Object.apply (/usr/share/nodejs/pify/index.js:85:19)
at before (/<>/test/test.js:46:15)
at Test. (/<>/test/test.js:80:5)
at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:95:17)
Emitted 'error' event on Server instance at:
at emitErrorNT (node:net:1838:8)
at process.processTicksAndRejections 
(node:internal/process/task_queues:82:21) {
  code: 'EADDRINUSE',
  errno: -98,
  syscall: 'listen',
  address: '::',
  port: 59060
}

Node.js v18.19.0
dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/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/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using 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.

--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel


[Pkg-javascript-devel] Bug#1057581: node-clipanion: FTBFS: error TS2307: Cannot find module 'get-stream' or its corresponding type declarations.

2023-12-05 Thread Santiago Vila

Package: src:node-clipanion
Version: 3.2.1+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --with nodejs
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure --buildsystem=nodejs
/!\ website/package.json not found
Unable to load website
workspaces field found in package.json

Found debian/nodejs/additional_components
Link ./node_modules/tslib -> /usr/share/nodejs/tslib
Link ./node_modules/@types/mocha -> /usr/share/nodejs/@types/mocha
Link ./node_modules/typescript -> /usr/share/nodejs/typescript
Link ./node_modules/@rollup/plugin-typescript -> 
/usr/share/nodejs/@rollup/plugin-typescript
Link ./node_modules/@types/chai -> /usr/share/nodejs/@types/chai
Link ./node_modules/ts-node -> /usr/share/nodejs/ts-node
Link ./node_modules/@types/chai-as-promised -> 
/usr/share/nodejs/@types/chai-as-promised
Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node
Link ./node_modules/get-stream -> /usr/share/nodejs/get-stream
/!\ website/package.json not found
Unable to load website
Link ./node_modules/typanion -> /usr/share/nodejs/typanion
Found debian/nodejs/additional_components
   dh_auto_build --buildsystem=nodejs
/!\ website/package.json not found
Unable to load website
workspaces field found in package.json

Found debian/nodejs/additional_components
Found debian/nodejs/./build
cd ./. && sh -ex debian/nodejs/./build
+ rollup -c --bundleConfigAsCjs

/<>/sources/advanced/builtins/definitions.ts, /<>/sources/advanced/builtins/help.ts, /<>/sources/advanced/builtins/index.ts, /<>/sources/advanced/builtins/version.ts, /<>/sources/advanced/Cli.ts, 
/<>/sources/advanced/Command.ts, /<>/sources/advanced/HelpCommand.ts, /<>/sources/advanced/index.ts, /<>/sources/advanced/options/Array.ts, /<>/sources/advanced/options/Boolean.ts, 
/<>/sources/advanced/options/Counter.ts, /<>/sources/advanced/options/index.ts, /<>/sources/advanced/options/Proxy.ts, /<>/sources/advanced/options/Rest.ts, /<>/sources/advanced/options/String.ts, 
/<>/sources/advanced/options/utils.ts, /<>/sources/constants.ts, /<>/sources/core.ts, /<>/sources/errors.ts, /<>/sources/format.ts, /<>/sources/platform/browser.ts, 
/<>/sources/platform/node.ts → lib, lib...
(!) The "preserveModules" option is deprecated. Use the 
"output.preserveModules" option instead.
https://rollupjs.org/https://rollupjs.org/configuration-options/#output-preservemodules
created lib, lib in 3.7s
+ cp -a sources/platform/package.json lib/platform/
+ debian/apply-publish-config ./package.json
   dh_auto_test --buildsystem=nodejs
/!\ website/package.json not found
Unable to load website
workspaces field found in package.json

Found debian/nodejs/additional_components
ln -s ../. node_modules/clipanion
/bin/sh -ex debian/tests/pkg-js/test
+ FORCE_COLOR=1 mocha --require ts-node/register --extension ts tests/specs 
--exclude tests/specs/browser.test.ts --exclude tests/specs/treeshake.test.ts

TSError: ⨯ Unable to compile TypeScript:
tests/tools.ts(1,54): error TS2307: Cannot find module 'get-stream' or its 
corresponding type declarations.

at createTSError (/usr/share/nodejs/ts-node/src/index.ts:865:12)
at reportTSError (/usr/share/nodejs/ts-node/src/index.ts:869:19)
at getOutput (/usr/share/nodejs/ts-node/src/index.ts:1083:36)
at Object.compile (/usr/share/nodejs/ts-node/src/index.ts:1439:41)
at Module.m._compile (/usr/share/nodejs/ts-node/src/index.ts:1623:30)
at Module._extensions..js (node:internal/modules/cjs/loader:1414:10)
at Object.require.extensions. [as .ts] 
(/usr/share/nodejs/ts-node/src/index.ts:1627:12)
at Module.load (node:internal/modules/cjs/loader:1197:32)
at Function.Module._load (node:internal/modules/cjs/loader:1013:12)
at Module.require (node:internal/modules/cjs/loader:1225:19)
at require (node:internal/modules/helpers:177:18)
at Object. (/<>/tests/specs/advanced.test.ts:6:1)
at Module._compile (node:internal/modules/cjs/loader:1356:14)
at Module.m._compile (/usr/share/nodejs/ts-node/src/index.ts:1624:23)
at Module._extensions..js (node:internal/modules/cjs/loader:1414:10)
at Object.require.extensions. [as .ts] 
(/usr/share/nodejs/ts-node/src/index.ts:1627:12)
at Module.load (node:internal/modules/cjs/loader:1197:32)
at Function.Module._load (node:internal/modules/cjs/loader:1013:12)
at Module.require (node:internal/modules/cjs/loader:1225:19)
at require (node:internal/modules/helpers:177:18)
at Object.exports.requireOrImport 
(/usr/share/nodejs/mocha/lib/nodejs/esm-utils.js:53:16)
at async Object.exports.loadFilesAsync 
(/usr/share/nodejs/mocha/lib/nodejs/esm-utils.js:100:20)
at async singleRun 

[Pkg-javascript-devel] Bug#927015: node-serve-static: FTBFS (failing tests)

2019-04-13 Thread Santiago Vila
Package: src:node-serve-static
Version: 1.6.4-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
dh: Compatibility levels before 9 are deprecated (level 8 in use)
   dh_update_autotools_config -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha -C --reporter spec --bail --check-leaks --require should test/


  serveStatic()
basic operations
  ✓ should require root path
  ✓ should require root path to be string
  ✓ should serve static files (125ms)
  ✓ should support nesting
  ✓ should set Content-Type
  ✓ should set Last-Modified
  ✓ should default max-age=0
  ✓ should support urlencoded pathnames
  ✓ should not choke on auth-looking URL
  ✓ should support index.html
  ✓ should support ../
  ✓ should support HEAD
  ✓ should skip POST requests
  ✓ should support conditional requests
  ✓ should ignore hidden files
  ✓ should set max-age=0 by default
current dir
  ✓ should be served with "."
extensions
  ✓ should be not be enabled by default
  ✓ should be configurable
  ✓ should support disabling extensions
  ✓ should support fallbacks
  ✓ should 404 if nothing found
hidden files
  ✓ should be served when dotfiles: "allow" is given
lastModified
  when false
✓ should not include Last-Modifed
  when true
✓ should include Last-Modifed
maxAge
  ✓ should accept string
  ✓ should be reasonable when infinite
redirect
  ✓ should redirect directories
  ✓ should include HTML link
  ✓ should redirect directories with query string
  ✓ should not redirect to protocol-relative locations
  ✓ should not redirect incorrectly
  when false
1) should disable redirect


  32 passing (378ms)
  1 failing

  1) serveStatic()
   redirect
 when false
   should disable redirect:
 Error: expected 404 "Not Found", got 500 "Internal Server Error"
  at Test.assert (/usr/lib/nodejs/supertest/lib/test.js:205:15)
  at Server.assert (/usr/lib/nodejs/supertest/lib/test.js:132:12)
  at emitCloseNT (net.js:1616:8)
  at process._tickCallback (internal/process/next_tick.js:63:19)



make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-serve-static.html

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.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#926720: node-miller-rabin: FTBFS randomly (uses a non-prime to test the test)

2019-04-09 Thread Santiago Vila
Package: src:node-miller-rabin
Version: 4.0.1-4
Severity: serious
Tags: ftbfs patch

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with nodejs
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_test --buildsystem=nodejs -i
/bin/sh -e debian/tests/pkg-js/test


  Miller-Rabin
1) should test number for primality


  0 passing (93ms)
  1 failing

  1) Miller-Rabin
   should test number for primality:

  AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:

  assert(!mr.test(new bn(221)))

  + expected - actual

  -false
  +true
  
  at Context. (test/api-test.js:8:5)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:334:5)



dh_auto_test: /bin/sh -e debian/tests/pkg-js/test returned exit code 1
make: *** [debian/rules:8: build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The failure happens randomly. Sometimes it happens, sometimes it does not,
so the only recipe to reproduce it is to try many times.

I've put two build logs here:

https://people.debian.org/~sanvila/build-logs/node-miller-rabin/

AFAIK, this being a primality test, I assume the outcome is either
"not prime" or "maybe prime", so the only way to test the test is by
giving a known prime and expect "maybe prime" as output.

So: Why is the test calling mr.test with 221, which is not prime? (221 = 13 x 
17)

And why this fails randomly? Does the test perform random calculations
internally and it's therefore not deterministic? Even in such case I
don't see how a non-prime like 221 may help to catch obvious errors in
a test suite for a primality test.

Proposed patch below.

Thanks.

--- a/test/api-test.js
+++ b/test/api-test.js
@@ -5,7 +5,6 @@ var bn = require('bn.js');
 describe('Miller-Rabin', function() {
   it('should test number for primality', function() {
 this.timeout(8000);
-assert(!mr.test(new bn(221)));
 assert(mr.test(new bn(257)));
 
 var p = new bn('dba8191813fe8f51eaae1de70213aafede8f323f95f32cff' +

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#919588: Bug#919588: nodejs: FTBFS nodejs

2019-03-27 Thread Santiago Vila
On Wed, Mar 13, 2019 at 01:22:17AM +0100, Jérémy Lal wrote:

> Course of action:
> - check if upstream already knows about those two flaky tests
> - report and mark them as flaky, or apply upstream patch fixing them
> - upload... but i'm not sure this will be unblocked.

Please consider disabling at least the tests which fail a lot.
Everybody should be able to build packages without failures, not
just buildd.debian.org.

Thanks.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#919588: Bug#919588: nodejs: FTBFS randomly

2019-03-12 Thread Santiago Vila
retitle 919588 nodejs: FTBFS randomly 
(parallel/test-net-listen-after-destroying-stdin fails)
thanks

Hi.

Today I built nodejs the standard way (i.e. without eatmydata) 26 times,
of which it failed 12 times. This makes the failure rate to be around
46%, too high for my taste.

For these builds I was using a mix of self-hosted KVM machines and
n1-standard-1 instances from GCE.

Failed build logs available here:

https://people.debian.org/~sanvila/build-logs/nodejs/

Fortunately the (single) failing test was always the same, the one
I've just put in the bug title:

not ok 1208 parallel/test-net-listen-after-destroying-stdin

So I would definitely disable such test for buster.

Alternatively, if you feel brave enough to investigate and debug why
the test fails so much (and fix it the "proper" and "elegant" way),
I will gladly offer ssh access to an instance where this "randomness"
is reproducible (so to speak). If interested, please contact me
privately for details.

Thanks a lot.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#919588: Bug#919588: nodejs: FTBFS nodejs

2019-03-12 Thread Santiago Vila
Hi.

For the record, I have been unable to build nodejs at all since 2018-04.
This is my build history for buster:

Status: successful  nodejs_8.9.3~dfsg-12_amd64-20180226T123733Z
Status: failed  nodejs_8.11.1~dfsg-2_amd64-20180418T105030Z
Status: failed  nodejs_8.11.2~dfsg-1_amd64-20180521T234811Z
Status: failed  nodejs_8.11.2~dfsg-1_amd64-20180608T120305Z
Status: failed  nodejs_8.11.2~dfsg-1_amd64-20180614T234712Z
Status: failed  nodejs_8.11.2~dfsg-1_amd64-20180620T121016Z
Status: failed  nodejs_8.11.2~dfsg-1_amd64-20180630T103408Z
Status: failed  nodejs_8.11.2~dfsg-1_amd64-20180709T222124Z
Status: failed  nodejs_8.11.2~dfsg-1_amd64-20180729T033115Z
Status: failed  nodejs_8.11.2~dfsg-1_amd64-20180812T235312Z
Status: failed  nodejs_8.11.2~dfsg-1_amd64-20180830T211131Z
Status: failed  nodejs_8.11.2~dfsg-1_amd64-20180921T132811Z
Status: failed  nodejs_8.11.2~dfsg-1_amd64-20181012T152154Z
Status: failed  nodejs_8.11.2~dfsg-1_amd64-20181207T133517.964Z
Status: failed  nodejs_10.15.0~dfsg-8_amd64-20190116T104234.702Z
Status: failed  nodejs_10.15.0~dfsg-10_amd64-20190126T113009.661Z
Status: failed  nodejs_10.15.0~dfsg-10_amd64-20190131T043316.958Z
Status: failed  nodejs_10.15.1~dfsg-2_amd64-20190204T103205.172Z
Status: failed  nodejs_10.15.1~dfsg-5_amd64-20190211T131413.708Z
Status: failed  nodejs_10.15.1~dfsg-5_amd64-20190301T191242.213Z
Status: failed  nodejs_10.15.2~dfsg-1_amd64-20190303T150622.376Z

I've put my failed build logs here:

https://people.debian.org/~sanvila/build-logs/nodejs/

I am using sbuild + schroot + eatmydata. Will now try without eatmydata
to make sure eatmydata is not to blame for the failures.

On Thu, 17 Jan 2019, Jérémy Lal wrote:

> It's building all right - the problem you see is that there are some tests 
> (4) failures:
> not ok 1 parallel/test-assert
> not ok 1428 parallel/test-repl-preprocess-top-level-await
> not ok 1447 parallel/test-repl-top-level-await
> not ok 2181 parallel/test-net-listen-after-destroying-stdin
> 
> repl and net failures might happen depending on your build env.
> If i were you i'd simply mark them as FLAKY (there is a debian patch doing 
> similar changes).
> 
> Build tests failures are ignored (see debian/rules) if you build with 
> experimental distribution
> or UNRELEASED,
> so i suggest you do the build like that, then see if, once installed,
> node test/parallel/test-assert.js
> reports the same error or not. Likewise for the other errors.
> If it doesn't then just shut the failure using the technique in the patch.
> It it still does then it's a good idea to report it upstream.

I don't think this reply is good enough for a FTBFS bug in a supported
architecture (amd64).

Packages should build for everybody, including the tests, and the end
user should never be told that they have to try the build in
experimental, or disable the tests, or, in general, jumping through
hoops. The build should just work (with 0 exit status, indicating
success) without doing anything "special".

Thanks.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#922216: node-normalize.css: FTBFS (error: unknown option `--s0')

2019-02-13 Thread Santiago Vila
Package: src:node-normalize.css
Version: 8.0.1-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
cleancss --s0 normalize.css -o normalize.min.css

  error: unknown option `--s0'

make[1]: *** [debian/rules:11: normalize.min.css] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-normalize.css.html

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.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#922093: node-commander: FTBFS in sid (AssertionError: expected '' to be 'SIGHUPn')

2019-02-11 Thread Santiago Vila
Package: src:node-commander
Version: 2.12.2-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid but it failed:


[...]
 debian/rules build-indep
dh build-indep --with nodejs
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   dh_auto_test --buildsystem=nodejs -i
/bin/sh -e debian/tests/pkg-js/test
make[1]: Entering directory '/<>'

   test.arguments.js ✓
   test.command.action.js ✓
   test.command.alias.help.js ✓
   test.command.allowUnknownOption.js ✓
   test.command.executableSubcommand.js ✓
   test.command.executableSubcommand.signals.hup.js ✖

/usr/lib/nodejs/should/lib/assertion.js:72
throw new AssertionError(params);
^
AssertionError: expected '' to be 'SIGHUP\n'
at Assertion.fail (/usr/lib/nodejs/should/lib/assertion.js:92:17)
at Assertion.value (/usr/lib/nodejs/should/lib/assertion.js:164:19)
at Timeout._onTimeout 
(/<>/test/test.command.executableSubcommand.signals.hup.js:19:19)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)
make[1]: *** [Makefile:5: test] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: /bin/sh -e debian/tests/pkg-js/test returned exit code 2
make: *** [debian/rules:8: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-commander.html

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.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#921896: json-js: FTBFS (ERROR: `cycle.min.map` is not a supported option)

2019-02-09 Thread Santiago Vila
Package: src:json-js
Version: 0~20160510-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
test -x debian/rules
mkdir -p "."

Scanning upstream source for new/changed copyright notices...

set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive 
--copyright --deb-fmt --ignore 
'^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 * | 
/usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
2 combinations of copyright and licensing found.
WARNING:New or changed notices discovered:

Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/

To fix the situation please do the following:
  1) Examine debian/copyright_* and referenced files
  2) Update debian/copyright as needed
  3) Replace debian/copyright_hints with debian/copyright_newhints
touch debian/stamp-copyright-check
touch debian/stamp-upstream-cruft
uglifyjs --source-map cycle.min.map -o cycle.min.js cycle.js
Supported options:
  content null
  filenamenull
  includeSources  false
  rootnull
  url null
ERROR: `cycle.min.map` is not a supported option
at DefaultsError.get (eval at  
(/usr/lib/nodejs/uglify-js/tools/node.js:20:1), :71:23)
at fatal (/usr/lib/nodejs/uglify-js/bin/uglifyjs:291:53)
at run (/usr/lib/nodejs/uglify-js/bin/uglifyjs:235:9)
at Object. (/usr/lib/nodejs/uglify-js/bin/uglifyjs:160:5)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
make: *** [debian/rules:36: cycle.min.js] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/json-js.html

where you can get a full build log if you need it.

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.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#921794: node-cross-spawn-async: FTBFS (failing tests)

2019-02-08 Thread Santiago Vila
Package: src:node-cross-spawn-async
Version: 2.2.5-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
nodejs test/prepare && mocha -C -R spec test/test
Copied "prepare_()%!^&;, .sh" to "()%!^&;, "


  cross-spawn-async
1) should support shebang in executables with /usr/bin/env
2) should support shebang in executables without /usr/bin/env
3) should support shebang in executables with relative path
✓ should support shebang in executables with relative path that starts 
with `..` (1538ms)
4) should support shebang in executables with extensions
✓ should expand using PATHEXT properly
✓ should handle commands with spaces
✓ should handle commands with special shell chars
✓ should handle arguments with quotes (1744ms)
✓ should handle empty arguments (1244ms)
✓ should handle non-string arguments (1236ms)
✓ should handle arguments with spaces (1196ms)
✓ should handle arguments with \" (1237ms)
✓ should handle arguments that end with \ (1213ms)
✓ should handle arguments that contain shell special chars (1202ms)
✓ should handle special arguments when using echo
✓ should handle optional args correctly (63ms)
✓ should not mutate args nor options
✓ should give correct exit code (1216ms)
✓ should work with a relative command
✓ should emit "error" and "close" if command does not exist (1024ms)
✓ should NOT emit "error" if shebang command does not exist (1013ms)
✓ should NOT emit "error" if the command actual exists but exited with 1 
(1012ms)


  19 passing (23s)
  4 failing

  1) cross-spawn-async
   should support shebang in executables with /usr/bin/env:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  2) cross-spawn-async
   should support shebang in executables without /usr/bin/env:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  3) cross-spawn-async
   should support shebang in executables with relative path:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  4) cross-spawn-async
   should support shebang in executables with extensions:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)



make[1]: *** [debian/rules:11: override_dh_auto_test] Error 4
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-cross-spawn-async.html

where you can get a full build log if you need it.

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.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#921797: node-lru-cache: FTBFS (failing tests)

2019-02-08 Thread Santiago Vila
Package: src:node-lru-cache
Version: 5.1.1-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
tap -R spec test/*.js

test/basic.js
  basic

✓ should be equal

✓ should be equal

[... snipped ...]


✓ should be equal

✓ should be equal

✓ should be equal

✓ should be equal

✓ should be equal

✓ should be equal

✓ should be equal

✓ should be equal

✓ should be equal

✓ should be equal

✓ should be equal

  dumpLru

✓ type is Yallist


  650 passing (14s)
  1 failing

  1) test/foreach.js expires should be equal:

  Error: should be equal
  + expected - actual

  -3
  +5
  
  at Timeout._onTimeout (test/foreach.js:125:7)

make[1]: *** [debian/rules:12: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-lru-cache.html

where you can get a full build log if you need it.

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.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#921796: node-libnpx: FTBFS (failing tests)

2019-02-08 Thread Santiago Vila
Package: src:node-libnpx
Version: 10.2.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
tail -n +2 README.md | marked-man --manual 'User Commands' --version 
libnpx@$(dpkg-parsechangelog -S version) > libnpx.1
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mkdir node_modules
ln -s /usr/lib/nodejs/npm node_modules
ln -s .. node_modules/libnpx

[... snipped ...]

1..10
ok 15 - treats directory-type commands specially # time=39.876ms

# Subtest: -n and --node-arg special parsing rules
ok 1 - should match pattern provided
ok 2 - should match pattern provided
ok 3 - should match pattern provided
ok 4 - should match pattern provided
ok 5 - should match pattern provided
ok 6 - should match pattern provided
ok 7 - should match pattern provided
ok 8 - should match pattern provided
ok 9 - should match pattern provided
ok 10 - should match pattern provided
1..10
ok 16 - -n and --node-arg special parsing rules # time=75.918ms

1..16
# time=708.137ms
ok 5 - test/parse-args.js # time=2287.591ms

# Subtest: test/util.js
# Subtest: promisify with existing util.promisify
ok 1 - used existing promisify fn
1..1
ok 1 - promisify with existing util.promisify # time=33.67ms

# Subtest: promisify without existing util.promisify
ok 1 - got a thenable
ok 2 - value passed through successfully
ok 3 - got the error!
1..3
ok 2 - promisify without existing util.promisify # time=22.968ms

1..2
# time=109.629ms
ok 6 - test/util.js # time=1657.342ms

1..6
# failed 1 of 6 tests
# time=49363.288ms
make[1]: *** [debian/rules:27: override_dh_auto_test] Error 123
make[1]: Leaving directory '/<>'
make: *** [debian/rules:9: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-libnpx.html

where you can get a full build log if you need it.

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.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#921798: node-mocha: FTBFS (Module not found: Error: Recursion in resolving)

2019-02-08 Thread Santiago Vila
Package: src:node-mocha
Version: 4.1.0+ds3-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/node-mocha-4.1.0+ds3'
NODE_PATH='/usr/share/nodejs:/usr/lib/nodejs' webpack --verbose --config 
debian/webpack.config.js
Hash: 87cc69c5bf02c862585f
Version: webpack 3.5.6
Time: 2463ms
   AssetSize  ChunksChunk Names
mocha.js  458 kB   0  [emitted]  [big]  main
Entrypoint main [big] = mocha.js

[... snipped ...]

  raw-module: (/<>/node-mocha-4.1.0+ds3) buffer
  module: (/<>/node-mocha-4.1.0+ds3) buffer
  resolve: (/usr/share/nodejs) ./buffer
  new-resolve: (/usr/share/nodejs) ./buffer
  parsed-resolve: (/usr/share/nodejs) ./buffer
  described-resolve: (/usr/share/nodejs) ./buffer
  resolve: (/<>/node-mocha-4.1.0+ds3) buffer
 @ /usr/lib/nodejs/core-util-is/lib/util.js 1:0-79
 @ /usr/lib/nodejs/readable-stream/lib/_stream_duplex.js
 @ /usr/lib/nodejs/readable-stream/readable-browser.js
 @ /usr/lib/nodejs/stream-browserify/index.js
 @ /usr/lib/nodejs/browser-stdout/index.js
 @ ./browser-entry.js

ERROR in /usr/share/javascript/util/support/isBuffer.js
Module not found: Error: Recursion in resolving
Stack:
  resolve: (/usr/share/javascript/util/support) 
./../../../../../<>/node-mocha-4.1.0+ds3/buffer
  new-resolve: (/usr/share/javascript/util/support) 
./../../../../../<>/node-mocha-4.1.0+ds3/buffer
  parsed-resolve: (/usr/share/javascript/util/support) 
./../../../../../<>/node-mocha-4.1.0+ds3/buffer
  described-resolve: (/usr/share/javascript/util/support) 
./../../../../../<>/node-mocha-4.1.0+ds3/buffer
  relative: (/<>/node-mocha-4.1.0+ds3/buffer) 
  described-relative: (/<>/node-mocha-4.1.0+ds3/buffer) 
  raw-file: (/<>/node-mocha-4.1.0+ds3/buffer) 
  file: (/<>/node-mocha-4.1.0+ds3/buffer) 
  resolve: (/<>/node-mocha-4.1.0+ds3) buffer
  new-resolve: (/<>/node-mocha-4.1.0+ds3) buffer
  parsed-resolve: (/<>/node-mocha-4.1.0+ds3) buffer module
  described-resolve: (/<>/node-mocha-4.1.0+ds3) buffer module
  raw-module: (/<>/node-mocha-4.1.0+ds3) buffer
  module: (/<>/node-mocha-4.1.0+ds3) buffer
  resolve: (/usr/share/nodejs) ./buffer
  new-resolve: (/usr/share/nodejs) ./buffer
  parsed-resolve: (/usr/share/nodejs) ./buffer
  described-resolve: (/usr/share/nodejs) ./buffer
  resolve: (/<>/node-mocha-4.1.0+ds3) buffer
 @ /usr/share/javascript/util/support/isBuffer.js 1:0-79
 @ /usr/share/javascript/util/util.js
 @ ./lib/utils.js
 @ ./lib/mocha.js
 @ ./browser-entry.js
make[1]: *** [debian/rules:23: mocha.js] Error 2
make[1]: Leaving directory '/<>/node-mocha-4.1.0+ds3'
make: *** [debian/rules:8: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-mocha.html

where you can get a full build log if you need it.

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.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#921795: node-flagged-respawn: FTBFS (failing tests)

2019-02-08 Thread Santiago Vila
Package: src:node-flagged-respawn
Version: 1.0.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha -R spec


  flaggedRespawn
isV8flags
  ✓ should return true when flag is in v8flags
  ✓ should ignore separator differences of "-" and "_"
  ✓ should return false when flag is not in v8flags

[... snipped ...]

 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  7) flaggedRespawn
   force and forbid respawning
 always forbid respawning with inner --no-respawning:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  8) flaggedRespawn
   force and forbid respawning
 should force respawning with node flags (array):
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  9) flaggedRespawn
   force and forbid respawning
 should force respawning with node flags (string):
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  10) flaggedRespawn
   force and forbid respawning
 should take priority to forbidding than forcing:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  11) flaggedRespawn
   cli args which are passed to app
 should pass args except v8flags, forced node flags, --no-respawning 
when respawned:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  12) flaggedRespawn
   cli args which are passed to app
 should pass args except v8flags, forced node flags, --no-respawning 
when not respawned:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)



make[1]: *** [debian/rules:13: override_dh_auto_test] Error 12
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-flagged-respawn.html

where you can get a full build log if you need it.

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.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#884155: show be fixed in unstable & testing

2019-01-29 Thread Santiago Vila
On Tue, Jan 29, 2019 at 04:42:09PM +0100, Paolo Greppi wrote:
> chai 4.2 has landed in testing, and all tests pass.
> can this be closed now ?

AFAIK, yes (unless there is yet another different version in
experimental of either this package or a build-dependency, which I
have not tested).

Thanks.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#886664: fixed in node-d3-timer 1.0.7-4

2019-01-25 Thread Santiago Vila
found 886664 1.0.7-4
thanks

>[ Xavier Guimard ]
>* Remove timeout based tests (Closes: #886664)

Hi. Sorry for the reopening but this does not seem fixed:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/node-d3-timer.html

Thanks.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#919905: node-istanbul: FTBFS in sid

2019-01-20 Thread Santiago Vila
Package: src:node-istanbul
Version: 0.4.5+ds-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/node-istanbul-0.4.5+ds'
mkdir -p lib/assets/vendor
test -f  /usr/share/javascript/prettify/prettify.js
make[1]: *** [debian/rules:15: override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>/node-istanbul-0.4.5+ds'
make: *** [debian/rules:8: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-istanbul.html

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.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#919737: underscore: FTBFS (ERROR: `underscore.min.map` is not a supported option)

2019-01-19 Thread Santiago Vila
tags 919737 - unreproducible moreinfo
thanks

Based on the last message by Jonas, I'm removing those tags
which do not apply here.

Thanks.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#919734: node-yauzl: FTBFS (TypeError: FdSlicer is not a constructor)

2019-01-18 Thread Santiago Vila
Package: src:node-yauzl
Version: 2.1.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
dh: Compatibility levels before 9 are deprecated (level 8 in use)
   dh_update_autotools_config -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
nodejs test/test.js
/<>/index.js:44
var fdSlicer = new FdSlicer(fd, {autoClose: true});
   ^

TypeError: FdSlicer is not a constructor
at /<>/index.js:44:20
at FSReqWrap.oncomplete (fs.js:153:5)
make[1]: *** [debian/rules:11: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-yauzl.html

where you can get a full build log if you need it.

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.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#919737: underscore: FTBFS (ERROR: `underscore.min.map` is not a supported option)

2019-01-18 Thread Santiago Vila
Package: src:underscore
Version: 1.8.3~dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
test -x debian/rules
mkdir -p "."

Scanning upstream source for new/changed copyright notices...

set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive 
--copyright --deb-fmt --ignore 
'^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 * | 
/usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
9 combinations of copyright and licensing found.
WARNING:New or changed notices discovered:

Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Copyright: NONE
Copyright: 2009-2015, Jeremy Ashkenas, DocumentCloud and Investigative
Files: docs/images/background.png
Copyright: 
…R…W…r…g…2…n…0f…X[E…p…O…8…y$)…F…d…X…1=…-…l-…r…n…
  …!…U…|…}…zQ…6'…N…Ij…dO…Q…C…WR…5…
  b,UE.…O…kz…~…1…kk…J….…;…%N…o…?~…"…[B…T…hd.
  e…"n|…|…4…/…9pwb…"…
  …w`…u…j…r…mt"…!…6(…v
License: UNKNOWN
 FIXME

Files: underscore.js
Copyright: 2009-2015, Jeremy Ashkenas, DocumentCloud and Investigative 
Reporters & Editors
License: UNKNOWN
 FIXME

Copyright: 2009-.
Files: docs/images/underscore.png
Copyright: …PA?2…J…P…{…   
…$…}c…6)…=…R<…,q……e…|…%z…J…1…Zf…1…G…D…
  …4…2…X=…J;U…Q…9…U6…K:…"-*…"…ch…

To fix the situation please do the following:
  1) Examine debian/copyright_* and referenced files
  2) Update debian/copyright as needed
  3) Replace debian/copyright_hints with debian/copyright_newhints
touch debian/stamp-copyright-check
touch debian/stamp-upstream-cruft
uglifyjs --source-map underscore.min.map -o underscore.min.js underscore.js
Supported options:
  content null
  filenamenull
  includeSources  false
  rootnull
  url null
ERROR: `underscore.min.map` is not a supported option
at DefaultsError.get (eval at  
(/usr/lib/nodejs/uglify-js/tools/node.js:20:1), :71:23)
at fatal (/usr/lib/nodejs/uglify-js/bin/uglifyjs:291:53)
at run (/usr/lib/nodejs/uglify-js/bin/uglifyjs:235:9)
at Object. (/usr/lib/nodejs/uglify-js/bin/uglifyjs:160:5)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
make: *** [debian/rules:35: underscore.min.js] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/underscore.html

where you can get a full build log if you need it.

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.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#919732: node-es6-shim: FTBFS (ERROR: cannot write source map to STDOUT)

2019-01-18 Thread Santiago Vila
Package: src:node-es6-shim
Version: 0.35.4+ds-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/node-es6-shim-0.35.4+ds'
uglifyjs --support-ie8 --keep-fnames --comments -m -b 
ascii_only=true,beautify=false es6-shim.js --source-map=es6-shim.map > 
es6-shim.min.js
ERROR: cannot write source map to STDOUT
make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>/node-es6-shim-0.35.4+ds'
make: *** [debian/rules:6: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-es6-shim.html

where you can get a full build log if you need it.

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.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#919524: node-groove: FTBFS in sid (no matching function for call to 'v8::Function::NewInstance()')

2019-01-16 Thread Santiago Vila
Package: src:node-groove
Version: 2.5.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
node-gyp configure build
gyp info it worked if it ends with ok
gyp info using node-gyp@3.8.0
gyp info using node@10.15.0 | linux | x64
gyp info spawn /usr/bin/python2
gyp info spawn args [ '/usr/share/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/<>/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/usr/share/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/usr/include/nodejs/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/usr/include/nodejs',
gyp info spawn args   '-Dnode_gyp_dir=/usr/share/node-gyp',
gyp info spawn args   
'-Dnode_lib_file=/usr/include/nodejs/<(target_arch)/node.lib',
gyp info spawn args   '-Dmodule_root_dir=/<>',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.' ]
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
make[2]: Entering directory '/<>/build'
  CXX(target) Release/obj.target/groove/src/groove.o
In file included from ../src/groove.cc:2:
../../../../usr/lib/nodejs/nan/nan.h: In function 'void 
Nan::AsyncQueueWorker(Nan::AsyncWorker*)':
../../../../usr/lib/nodejs/nan/nan.h:2232:62: warning: cast between 
incompatible function types from 'void (*)(uv_work_t*)' {aka 'void 
(*)(uv_work_s*)'} to 'uv_after_work_cb' {aka 'void (*)(uv_work_s*, int)'} 
[-Wcast-function-type]
 , reinterpret_cast(AsyncExecuteComplete)
  ^
../src/groove.cc: In function 'Nan::NAN_METHOD_RETURN_TYPE 
SetLogging(Nan::NAN_METHOD_ARGS_TYPE)':
../src/groove.cc:21:45: warning: 'double v8::Value::NumberValue() const' is 
deprecated: Use maybe version [-Wdeprecated-declarations]
 groove_set_logging(info[0]->NumberValue());
 ^
In file included from /usr/include/nodejs/deps/v8/include/v8.h:26,
 from /usr/include/nodejs/src/node.h:63,
 from ../src/groove.cc:1:
/usr/include/nodejs/deps/v8/include/v8.h:2475:45: note: declared here
   V8_DEPRECATED("Use maybe version", double NumberValue() const);
 ^~~
/usr/include/nodejs/deps/v8/include/v8config.h:324:3: note: in definition of 
macro 'V8_DEPRECATED'
   declarator __attribute__((deprecated(message)))
   ^~
In file included from ../src/groove.cc:1:
../src/groove.cc: At global scope:
/usr/include/nodejs/src/node.h:570:43: warning: cast between incompatible 
function types from 'void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)' {aka 
'void (*)(v8::Local)'} to 'node::addon_register_func' {aka 'void 
(*)(v8::Local, v8::Local, void*)'} [-Wcast-function-type]
   (node::addon_register_func) (regfunc),  \
   ^
/usr/include/nodejs/src/node.h:604:3: note: in expansion of macro 
'NODE_MODULE_X'
   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
   ^
../src/groove.cc:101:1: note: in expansion of macro 'NODE_MODULE'
 NODE_MODULE(groove, Initialize)
 ^~~
In file included from /usr/include/nodejs/src/node.h:63,
 from ../src/groove.cc:1:
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of 'void 
v8::PersistentBase::SetWeak(P*, typename v8::WeakCallbackInfo::Callback, 
v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename 
v8::WeakCallbackInfo::Callback = void (*)(const 
v8::WeakCallbackInfo&)]':
/usr/include/nodejs/src/node_object_wrap.h:85:78:   required from here
/usr/include/nodejs/deps/v8/include/v8.h:9502:16: warning: cast between 
incompatible function types from 
'v8::WeakCallbackInfo::Callback' {aka 'void (*)(const 
v8::WeakCallbackInfo&)'} to 'Callback' {aka 'void (*)(const 
v8::WeakCallbackInfo&)'} [-Wcast-function-type]
reinterpret_cast(callback), type);
^~~~
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of 'void 
v8::PersistentBase::SetWeak(P*, typename v8::WeakCallbackInfo::Callback, 
v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename 
v8::WeakCallbackInfo::Callback = void (*)(const 
v8::WeakCallbackInfo&)]':
/usr/include/nan_object_wrap.h:66:61:   

[Pkg-javascript-devel] Bug#919237: node-jsonld: FTBFS in sid (Error: Can't resolve 'rdf-canonize')

2019-01-13 Thread Santiago Vila
Package: src:node-jsonld
Version: 1.4.0-2
Severity: serious
Tags: ftbfs

Hello Jonas.

I tried to build this package in sid but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
BROWSERSLIST='node 6' babeljs \
--no-babelrc --presets=env \
--out-dir dist/node6/lib \
-- lib
lib/ActiveContextCache.js -> dist/node6/lib/ActiveContextCache.js
lib/DocumentCache.js -> dist/node6/lib/DocumentCache.js
lib/JsonLdError.js -> dist/node6/lib/JsonLdError.js
lib/JsonLdProcessor.js -> dist/node6/lib/JsonLdProcessor.js
lib/NQuads.js -> dist/node6/lib/NQuads.js

[... snipped ...]

 [239] /usr/lib/nodejs/core-js/fn/symbol/index.js 254 bytes {0} [built]
 [247] ./lib/jsonld.js 54.6 kB {0} [built]
 [281] ./lib/flatten.js 1.06 kB {0} [built]
 [282] ./lib/fromRdf.js 17.3 kB {0} [built]
 [283] ./lib/toRdf.js 10.3 kB {0} [built]
+ 277 hidden modules

WARNING in jsonld.min.js from UglifyJs
Side effects in initialization of unused variable _expandIri 
[./lib/jsonld.js:66,13]
Condition always false 
[./usr/lib/nodejs/regenerator-runtime/runtime.js:21,17]
Dropping side-effect-free statement [./lib/frame.js:91,23]
Side effects in initialization of unused variable _ret 
[./lib/frame.js:91,23]
Dropping side-effect-free statement [./lib/compact.js:165,40]
Side effects in initialization of unused variable _ret 
[./lib/compact.js:165,40]

ERROR in ./lib/jsonld.js
Module not found: Error: Can't resolve 'rdf-canonize' in 
'/<>/lib'
 @ ./lib/jsonld.js 60:15-38
 @ multi core-js/fn/array/from core-js/fn/array/includes core-js/fn/map 
core-js/fn/object/assign core-js/fn/promise core-js/fn/set 
core-js/fn/string/starts-with core-js/fn/symbol ./lib/index.js

ERROR in ./lib/NQuads.js
Module not found: Error: Can't resolve 'rdf-canonize' in 
'/<>/lib'
 @ ./lib/NQuads.js 8:17-40
 @ ./lib/jsonld.js
 @ multi core-js/fn/array/from core-js/fn/array/includes core-js/fn/map 
core-js/fn/object/assign core-js/fn/promise core-js/fn/set 
core-js/fn/string/starts-with core-js/fn/symbol ./lib/index.js

ERROR in ./lib/util.js
Module not found: Error: Can't resolve 'rdf-canonize' in 
'/<>/lib'
 @ ./lib/util.js 39:23-46
 @ ./lib/jsonld.js
 @ multi core-js/fn/array/from core-js/fn/array/includes core-js/fn/map 
core-js/fn/object/assign core-js/fn/promise core-js/fn/set 
core-js/fn/string/starts-with core-js/fn/symbol ./lib/index.js
make[1]: *** [debian/rules:8: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


This is just how the build ends in my autobuilder, but it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-jsonld.html

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.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#918004: fixed in node-inline-source-map 0.6.2~git-2

2019-01-12 Thread Santiago Vila
Hi.

This package propagated to testing and now the package FTBFS in testing:

https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/node-inline-source-map.html

Is there a reason why the control file was not updated? (as in the patch below)

Thanks.

--- a/debian/control
+++ b/debian/control
@@ -5,7 +5,7 @@ Maintainer: Debian Javascript Maintainers 

 Build-Depends: debhelper (>= 11)
, dh-buildinfo,
-   , nodejs (>= 8)
+   , nodejs (>= 10)
   , dpkg-dev (>= 1.17.14)
, node-tap (>= 0.7.0) 
, node-source-map (>= 0.5.3) 

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#918491: coffeescript: FTBFS with nodejs 10.x (The "error/message" argument is ambiguous)

2019-01-06 Thread Santiago Vila
retitle 918491 coffeescript: FTBFS with nodejs 10.x (The "error/message" 
argument is ambiguous)
thanks

Slightly more informative.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#918491: coffeescript: FTBFS (The "error/message" argument is ambiguous)

2019-01-06 Thread Santiago Vila
Package: src:coffeescript
Version: 1.12.8~dfsg-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid but it failed:


[...]
 debian/rules binary-indep
CDBS WARNING:  copyright-check disabled - licensecheck is missing.
test -x debian/rules
dh_testroot
dh_prep 
dh_installdirs -A 
mkdir -p "."

Scanning upstream source for new/changed copyright notices...

set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive 
--copyright --deb-fmt --ignore 
'^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 * | 
/usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
/bin/sh: 1: /usr/bin/licensecheck: not found
0 combinations of copyright and licensing found.
No new copyright notices found - assuming no news is good news...
touch debian/stamp-copyright-check
mkdir -p "debian/upstream-cruft"
cp -a "lib" "debian/upstream-cruft/lib";
touch debian/stamp-upstream-cruft
mkdir -p docs/v1/browser-compiler
chmod +x bin/cake
bin/cake build
bin/cake build
bin/cake build:browser
bin/cake test
failed 1 and passed 855 tests in 10.37 seconds 

  basic exception throwing 
  TypeError [ERR_AMBIGUOUS_ARGUMENT]: The "error/message" argument is 
ambiguous. The error "error" is identical to the message.
at expectsError (assert.js:1:1)
at throws (assert.js:1:1)
at Function. 
(/<>/test/exception_handling.coffee:1:1)
at global.test (/<>/Cakefile:1:1)
at Object. (/<>/test/exception_handling.coffee:1:1)
at Object. (/<>/test/exception_handling.coffee:1:1)
at Module._compile (internal/modules/cjs/loader.js:1:1)
at Object.exports.run 
(/<>/lib/coffee-script/coffee-script.js:1:1)
at runTests (/<>/Cakefile:1:1)
at Object.action (/<>/Cakefile:1:1)
at invoke (/<>/lib/coffee-script/cake.js:1:1)
at Object.exports.run (/<>/lib/coffee-script/cake.js:1:1)
at Object. (/<>/bin/cake:1:1)
at Module._compile (internal/modules/cjs/loader.js:1:1)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1:1)
at Module.load (internal/modules/cjs/loader.js:1:1)
at tryModuleLoad (internal/modules/cjs/loader.js:1:1)
at Function.Module._load (internal/modules/cjs/loader.js:1:1)
at Function.Module.runMain (internal/modules/cjs/loader.js:1:1)
at startup (internal/bootstrap/node.js:1:1)
at bootstrapNodeJSCore (internal/bootstrap/node.js:1:1)
 
  function() {
return throws((function() {
  throw 'error';
}), 'error');
  }
make: *** [debian/rules:37: debian/stamp-build] Error 1
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/coffeescript.html

where you can get a full build log if you need it.
[ Note: It fails in sid but it builds ok in buster ]

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.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#884155: Still needs to be fixed in buster/sid, reopening to avoid duplicate reports

2019-01-05 Thread Santiago Vila
reopen 884155
thanks

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#918441: node-websocket: FTBFS (ld: cannot find -lnode)

2019-01-05 Thread Santiago Vila
Package: src:node-websocket
Version: 1.0.23-3.1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with nodejs
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/<>'
dh_auto_build
make -j1
make[2]: Entering directory '/<>'
node-gyp configure build
gyp info it worked if it ends with ok
gyp info using node-gyp@3.8.0
gyp info using node@8.11.2 | linux | x64
gyp info spawn /usr/bin/python2

[... snipped ...]

   
^~~
../src/bufferutil.cc:104:7: note: here
   case 2: *((unsigned char*)to+1) = *((unsigned char*)from+1) ^ 
*((unsigned char*)mask+1);
   ^~~~
../src/bufferutil.cc:104:39: warning: this statement may fall through 
[-Wimplicit-fallthrough=]
   case 2: *((unsigned char*)to+1) = *((unsigned char*)from+1) ^ 
*((unsigned char*)mask+1);
   
^~~
../src/bufferutil.cc:105:7: note: here
   case 1: *((unsigned char*)to  ) = *((unsigned char*)from  ) ^ 
*((unsigned char*)mask);
   ^~~~
../src/bufferutil.cc: In static member function 'static 
Nan::NAN_METHOD_RETURN_TYPE BufferUtil::Unmask(Nan::NAN_METHOD_ARGS_TYPE)':
../src/bufferutil.cc:78:41: warning: this statement may fall through 
[-Wimplicit-fallthrough=]
   case 3: *((unsigned char*)from+2) = *((unsigned char*)from+2) ^ 
((unsigned char*)mask)[2];
   
~~^~~
../src/bufferutil.cc:79:7: note: here
   case 2: *((unsigned char*)from+1) = *((unsigned char*)from+1) ^ 
((unsigned char*)mask)[1];
   ^~~~
../src/bufferutil.cc:79:41: warning: this statement may fall through 
[-Wimplicit-fallthrough=]
   case 2: *((unsigned char*)from+1) = *((unsigned char*)from+1) ^ 
((unsigned char*)mask)[1];
   
~~^~~
../src/bufferutil.cc:80:7: note: here
   case 1: *((unsigned char*)from  ) = *((unsigned char*)from  ) ^ 
((unsigned char*)mask)[0];
   ^~~~
  SOLINK_MODULE(target) Release/obj.target/bufferutil.node
/usr/bin/ld: cannot find -lnode
collect2: error: ld returned 1 exit status
make[3]: *** [bufferutil.target.mk:131: Release/obj.target/bufferutil.node] 
Error 1
make[3]: Leaving directory '/<>/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit 
(/usr/share/node-gyp/lib/build.js:262:23)
gyp ERR! stack at emitTwo (events.js:126:13)
gyp ERR! stack at ChildProcess.emit (events.js:214:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit 
(internal/child_process.js:198:12)
gyp ERR! System Linux 4.9.0-8-amd64
gyp ERR! command "/usr/bin/node" "/usr/bin/node-gyp" "configure" "build"
gyp ERR! cwd /<>
gyp ERR! node -v v8.11.2
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok 
make[2]: *** [Makefile:2: all] Error 1
make[2]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make[1]: *** [debian/rules:44: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:14: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-websocket.html

where you can get a full build log if you need it.

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.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#907766: node-chokidar: FTBFS in buster/sid (failing tests)

2018-09-01 Thread Santiago Vila
Package: src:node-chokidar
Version: 1.7.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha --exit --reporter spec


  chokidar
✓ should expose public API methods
fs.watch (non-polling)
  watch a directory
✓ should produce an instance of chokidar.FSWatcher
✓ should expose public API methods
✓ should emit `add` event when file was added (57ms)
✓ should emit `addDir` event when directory was added (56ms)
✓ should emit `change` event when file was changed
✓ should emit `unlink` event when file was removed (104ms)
✓ should emit `unlinkDir` event when a directory was removed (53ms)
✓ should emit `unlink` and `add` events when a file is renamed (156ms)
✓ should emit `add`, not `change`, when previously deleted file is 
re-added (161ms)
✓ should not emit `unlink` for previously moved files (404ms)
✓ should survive ENOENT for missing subdirectories
✓ should notice when a file appears in a new directory
✓ should watch removed and re-added directories (1514ms)
  watch individual files
✓ should detect changes
✓ should detect unlinks (156ms)
✓ should detect unlink and re-add (257ms)
✓ should ignore unwatched siblings (55ms)
  renamed directory
✓ should emit `add` for a file in a renamed directory (1017ms)
  watch non-existent paths
✓ should watch non-existent file and detect add (56ms)
✓ should watch non-existent dir and detect addDir/add (106ms)
  watch glob patterns
✓ should correctly watch and emit based on glob input (62ms)
✓ should respect negated glob patterns (156ms)
✓ should traverse subdirs to match globstar patterns (216ms)
✓ should resolve relative paths with glob patterns (72ms)
✓ should correctly handle conflicting glob patterns (158ms)
✓ should correctly handle intersecting glob patterns (58ms)
✓ should not confuse glob-like filenames with globs (103ms)
✓ should treat glob-like directory names as literal directory names 
when globbing is disabled (64ms)
✓ should treat glob-like filenames as literal filenames when globbing 
is disabled (51ms)
✓ should not prematurely filter dirs against complex globstar 
patterns (62ms)
✓ should emit matching dir events
  watch symlinks
✓ should watch symlinked dirs
✓ should watch symlinked files
✓ should follow symlinked files within a normal dir
✓ should watch paths with a symlinked parent
✓ should not recurse indefinitely on circular symlinks
✓ should recognize changes following symlinked dirs
✓ should follow newly created symlinks (57ms)
✓ should watch symlinks as files when followSymlinks:false
✓ should watch symlinks within a watched dir as files when 
followSymlinks:false (310ms)
✓ should not reuse watcher when following a symlink to elsewhere 
(115ms)
✓ should properly match glob patterns that include a symlinked dir
  watch arrays of paths/globs
✓ should watch all paths in an array
✓ should accommodate nested arrays in input
✓ should throw if provided any non-string paths
  watch options
ignoreInitial
  false
✓ should emit `add` events for preexisting files
✓ should emit `addDir` event for watched dir
✓ should emit `addDir` events for preexisting dirs
  true
✓ should ignore inital add events (51ms)
✓ should ignore add events on a subsequent .add() (1002ms)
✓ should notice when a file appears in an empty directory
✓ should emit a change on a preexisting file as a change
✓ should not emit for preexisting dirs when depth is 0 (418ms)
ignored
  ✓ should check ignore after stating
  ✓ should not choke on an ignored watch path
  ✓ should ignore the contents of ignored dirs (359ms)
  ✓ should allow regex/fn ignores (57ms)
depth
  ✓ should not recurse if depth is 0
  ✓ should recurse to specified depth (66ms)
  ✓ should respect depth setting when following symlinks (65ms)
  ✓ should respect depth setting when following a new symlink
  ✓ should correctly handle dir events when depth is 0 (68ms)
atomic
  ✓ should ignore vim/emacs/Sublime swapfiles (906ms)
  ✓ should ignore stale tilde files (53ms)
cwd
  

[Pkg-javascript-devel] Bug#906390: node-vhost: FTBFS in buster/sid (autobuilder hangs)

2018-08-17 Thread Santiago Vila
Package: src:node-vhost
Version: 3.0.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
dh: Compatibility levels before 9 are deprecated (level 8 in use)
   dh_update_autotools_config -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha -C --reporter spec --bail --check-leaks test/


  vhost(hostname, server)
✓ should route by Host (57ms)
✓ should ignore port in Host
✓ should support IPv6 literal in Host
✓ should 404 unless matched
✓ should 404 without Host header
arguments
  hostname
✓ should be required
✓ should accept string
✓ should accept RegExp
  handle
✓ should be required
✓ should accept function
✓ should reject plain object
with string hostname
  ✓ should support wildcards
  ✓ should restrict wildcards to single part
  ✓ should treat dot as a dot
  ✓ should match entire string
  ✓ should populate req.vhost
with RegExp hostname
  ✓ should match using RegExp
  ✓ should match entire hostname
  ✓ should populate req.vhost


  19 passing (88ms)

E: Build killed with signal TERM after 60 minutes of inactivity


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-vhost.html

where you can get a full build log if you need it.

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.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#906389: node-mime-types: FTBFS in buster/sid (cp: cannot stat '/usr/share/node-mime/types.json': No such file or directory)

2018-08-17 Thread Santiago Vila
Package: src:node-mime-types
Version: 2.1.17-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
cd node_modules/mime-db/ && nodejs scripts/extensions
# just copy the file from node-mime
cp /usr/share/node-mime/types.json node_modules/mime-db/src/deb.types.json
cp: cannot stat '/usr/share/node-mime/types.json': No such file or directory
make[1]: *** [debian/rules:21: override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-mime-types.html

where you can get a full build log if you need it.

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.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#903336: node-babel-plugin-add-module-exports: FTBFS in buster/sid (dh_installdocs: Cannot find "README.md")

2018-07-08 Thread Santiago Vila
Package: src:node-babel-plugin-add-module-exports
Version: 0.2.1-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
 fakeroot debian/rules binary-indep
dh binary-indep
   dh_testroot -i
   dh_prep -i
   dh_install -i
   dh_installdocs -i
dh_installdocs: Cannot find (any matches for) "README.md" (tried in .)

debian/rules:8: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-babel-plugin-add-module-exports.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#903337: node-traverse: FTBFS in buster/sid (dh_installdocs: Cannot find "README.markdown")

2018-07-08 Thread Santiago Vila
Package: src:node-traverse
Version: 0.6.6-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-indep
dh binary-indep
   dh_testroot -i
   dh_prep -i
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
install -D -m644 index.js 
/<>/debian/node-traverse/usr/lib/nodejs/traverse.js
install -D -m644 index.js 
/<>/debian/libjs-traverse/usr/share/javascript/traverse/traverse.js
make[1]: Leaving directory '/<>'
   dh_installdocs -i
dh_installdocs: Cannot find (any matches for) "README.markdown" (tried in .)

debian/rules:8: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-traverse.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#903340: prettify.js: FTBFS in buster/sid (dh_installdocs: Cannot find "README.html")

2018-07-08 Thread Santiago Vila
Package: src:prettify.js
Version: 2015.12.04+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/prettify.js-2015.12.04+dfsg'
mkdir -p loader/skins/
make distrib.tstamp
make[2]: Entering directory '/<>/prettify.js-2015.12.04+dfsg'
Compiling
1570 src/prettify.css
 675 distrib/google-code-prettify/prettify.css
62985 src/prettify.js
14514 distrib/google-code-prettify/prettify.js
src/run_prettify.js:95: WARNING - "function (this:Window, 
(Function|null|string), number, ...[*]): number" must be called with a "this" 
type

[... snipped ...]

1909 src/lang-tex.js
 858 distrib/google-code-prettify/lang-tex.js
3938 src/lang-vb.js
2404 distrib/google-code-prettify/lang-vb.js
2846 src/lang-vhdl.js
2035 distrib/google-code-prettify/lang-vhdl.js
1928 src/lang-wiki.js
1139 distrib/google-code-prettify/lang-wiki.js
25439 src/lang-xq.js
23276 distrib/google-code-prettify/lang-xq.js
1468 src/lang-yaml.js
1002 distrib/google-code-prettify/lang-yaml.js
make[2]: Leaving directory '/<>/prettify.js-2015.12.04+dfsg'
make[1]: Leaving directory '/<>/prettify.js-2015.12.04+dfsg'
   dh_auto_build -i
make -j1
make[1]: Entering directory '/<>/prettify.js-2015.12.04+dfsg'
tar cf distrib/prettify-small.tar -C distrib google-code-prettify
/bin/bash: line 2: zip: command not found
wc: distrib/prettify-small.zip: No such file or directory
37202 distrib/prettify-small.tar.bz2
37826 distrib/prettify-small.tgz
1645 styles/desert.css
 940 loader/skins/desert.css
2726 styles/doxy.css
1604 loader/skins/doxy.css
1519 styles/sons-of-obsidian.css
 698 loader/skins/sons-of-obsidian.css
1945 styles/sunburst.css
1147 loader/skins/sunburst.css
tools/lang-handler-aliases.sh \
distrib/google-code-prettify \
  | perl -ne 'system("cp $1 $2") if m/^(\S+) (\S+)$/ && ! -e $2' \
  && touch lang-aliases.tstamp
cp: cannot stat 'to': No such file or directory
make[1]: Leaving directory '/<>/prettify.js-2015.12.04+dfsg'
   dh_auto_test -i
 fakeroot debian/rules binary-indep
dh binary-indep
   dh_testroot -i
   dh_prep -i
   dh_auto_install -i
   dh_install -i
   dh_installdocs -i
dh_installdocs: Cannot find (any matches for) "README.html" (tried in .)

debian/rules:12: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prettify.js.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#902507: node-multiparty: FTBFS in buster/sid (TypeError: mime.lookup is not a function)

2018-06-27 Thread Santiago Vila
Package: src:node-multiparty
Version: 4.0.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep
dh: Compatibility levels before 9 are deprecated (level 8 in use)
   dh_update_autotools_config -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
nodejs test/test.js
Fixture tests:
content-type/charset.http...(node:20301) [DEP0022] DeprecationWarning: 
os.tmpDir() is deprecated. Use os.tmpdir() instead.
OK
content-type/charset-last.http...OK
content-type/custom.http...OK
content-type/custom-equal-sign.http...OK

[... snipped ...]

special-chars-in-filename/osx-firefox-3.6.http...OK
special-chars-in-filename/osx-safari-5.http...OK
special-chars-in-filename/xp-chrome-12.http...OK
special-chars-in-filename/xp-ie-7.http...OK
special-chars-in-filename/xp-ie-8.http...OK
special-chars-in-filename/xp-safari-5.http...OK

Standalone tests:
test-chunked...(node:20311) [DEP0022] DeprecationWarning: os.tmpDir() is 
deprecated. Use os.tmpdir() instead.
OK
test-connection-aborted-closed...(node:20325) [DEP0022] DeprecationWarning: 
os.tmpDir() is deprecated. Use os.tmpdir() instead.
OK
test-connection-aborted...(node:20335) [DEP0022] DeprecationWarning: 
os.tmpDir() is deprecated. Use os.tmpdir() instead.
OK
test-content-transfer-encoding...(node:20345) [DEP0022] DeprecationWarning: 
os.tmpDir() is deprecated. Use os.tmpdir() instead.
OK
test-emit-order.../usr/lib/nodejs/form-data/form_data.js:130
'Content-Type: ' +  (options.contentType || 
mime.lookup(options.filename || value.path));
 ^

TypeError: mime.lookup is not a function
at FormData._multiPartHeader (/usr/lib/nodejs/form-data/form_data.js:130:58)
at FormData.append (/usr/lib/nodejs/form-data/form_data.js:39:21)
at Request.attach (/usr/lib/nodejs/superagent/lib/node/index.js:200:18)
at Server. 
(/<>/test/standalone/test-emit-order.js:51:7)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:106:13)
at Server.emit (events.js:208:7)
at emitListeningNT (net.js:1382:10)
at _combinedTickCallback (internal/process/next_tick.js:135:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
/<>/test/test.js:61
if (code) throw new Error("exited with code " + code);
  ^

Error: exited with code 1
at ChildProcess. (/<>/test/test.js:61:25)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
debian/rules:11: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-multiparty.html

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 page for this package.

Thanks.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#902506: node-husl: FTBFS in buster/sid (uglifyjs: not found)

2018-06-27 Thread Santiago Vila
Package: src:node-husl
Version: 6.0.1+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/node-husl-6.0.1+dfsg'
dh_auto_build
make -j1
make[2]: Entering directory '/<>/node-husl-6.0.1+dfsg'
coffee --compile husl.coffee
make[2]: Leaving directory '/<>/node-husl-6.0.1+dfsg'
make husl.min.js
make[2]: Entering directory '/<>/node-husl-6.0.1+dfsg'
uglifyjs husl.js > husl.min.js
/bin/sh: 1: uglifyjs: not found
Makefile:5: recipe for target 'husl.min.js' failed
make[2]: *** [husl.min.js] Error 127
make[2]: Leaving directory '/<>/node-husl-6.0.1+dfsg'
debian/rules:11: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>/node-husl-6.0.1+dfsg'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-husl.html

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 page for this package.

Thanks.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#902509: node-serve-static: FTBFS in buster/sid (TypeError: mime.lookup is not a function)

2018-06-27 Thread Santiago Vila
Package: src:node-serve-static
Version: 1.6.4-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep
dh: Compatibility levels before 9 are deprecated (level 8 in use)
   dh_update_autotools_config -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha -C --reporter spec --bail --check-leaks --require should test/


  serveStatic()
basic operations
  ✓ should require root path
  ✓ should require root path to be string
  1) should serve static files


  2 passing (41ms)
  1 failing

  1) serveStatic()
   basic operations
 should serve static files:
 Uncaught TypeError: mime.lookup is not a function
  at SendStream.type (/usr/lib/nodejs/send/index.js:693:19)
  at SendStream.send (/usr/lib/nodejs/send/index.js:503:8)
  at onstat (/usr/lib/nodejs/send/index.js:585:10)
  at FSReqWrap.oncomplete (fs.js:153:5)



debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-serve-static.html

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 page for this package.

Thanks.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#902510: node-source-map-support: FTBFS in buster/sid (Cannot find module 'source-map')

2018-06-27 Thread Santiago Vila
Package: src:node-source-map-support
Version: 0.5.5+ds-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>/node-source-map-support-0.5.5+ds'
mocha -R spec test.js
module.js:549
throw err;
^

Error: Cannot find module 'source-map'
at Function.Module._resolveFilename (module.js:547:15)
at Function.Module._load (module.js:474:25)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object. 
(/<>/node-source-map-support-0.5.5+ds/source-map-support.js:1:87)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object. 
(/<>/node-source-map-support-0.5.5+ds/test.js:1:63)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at /usr/lib/nodejs/mocha/lib/mocha.js:231:27
at Array.forEach ()
at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:228:14)
at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:536:10)
at Object. (/usr/lib/nodejs/mocha/bin/_mocha:573:18)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:191:16)
at bootstrap_node.js:612:3
debian/rules:8: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>/node-source-map-support-0.5.5+ds'
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-source-map-support.html

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 page for this package.

Thanks.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#834915: node-temp: FTBFS (AssertionError: temp.createWriteStream did not create a file)

2018-06-01 Thread Santiago Vila
As promised, full build logs available here:

https://people.debian.org/~sanvila/build-logs/node-temp/

This time I tried 100 times and it failed 96 times,
so it failed 96% of the time.

BTW: My autobuilders have nothing to do with reproducible builds
autobuilders. They use pbuilder, I use sbuild. They have multiple
CPUs, I usually have a single CPU. But in either case, the fact that
this happens in both sets of autobuilders makes this unlikely to be a
local problem in my side.

Thanks.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel