Your message dated Wed, 13 Apr 2022 11:19:03 +0000 with message-id <e1neb1b-00088q...@fasolo.debian.org> and subject line Bug#1009591: fixed in node-output-file-sync 2.0.1-3 has caused the Debian Bug report #1009591, regarding node-output-file-sync: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1009591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009591 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: node-output-file-sync Version: 2.0.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220412 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary > dh_update_autotools_config > dh_autoreconf > dh_auto_configure --buildsystem=nodejs > dh_auto_build --buildsystem=nodejs > No build command found, searching known files > dh_auto_test --buildsystem=nodejs > mkdir -p node_modules > ln -s ../debian/tests/test_modules/array-to-sentence > node_modules/array-to-sentence > ln -s ../debian/tests/test_modules/assert-valid-glob-opts > node_modules/assert-valid-glob-opts > ln -s ../debian/tests/test_modules/get-mode node_modules/get-mode > ln -s ../debian/tests/test_modules/glob-option-error > node_modules/glob-option-error > ln -s ../debian/tests/test_modules/indexed-filter > node_modules/indexed-filter > ln -s ../debian/tests/test_modules/inspect-with-kind > node_modules/inspect-with-kind > ln -s ../debian/tests/test_modules/is-utf8 node_modules/is-utf8 > ln -s ../debian/tests/test_modules/read-utf8-file > node_modules/read-utf8-file > ln -s ../debian/tests/test_modules/rmfr node_modules/rmfr > ln -s ../debian/tests/test_modules/validate-glob-opts > node_modules/validate-glob-opts > ln -s ../. node_modules/output-file-sync > /bin/sh -ex debian/tests/pkg-js/test > + tape test.js > TAP version 13 > # outputFileSync() > ok 1 should return null when it doesn't create any directories. > ok 2 should return the path of the first created directory. > ok 3 should throw an error when fs.writeFile fails. > ok 4 should throw an error when mkdirp fails. > ok 5 should reflect `mode` option to the directory mode. > ok 6 should reflect `mode` option to the file mode. > ok 7 should reflect `dirMode` option to the directory mode. > ok 8 should reflect `fileMode` option to the file mode. > ok 9 should create a file into the existing directory. > ok 10 should create a file into the new directory. > ok 11 should accept fs.writeFile's option. > # Argument validation for outputFileSync() > ok 12 should throw an error when it takes no arguments. > ok 13 should throw an error when the first argument is not a string. > ok 14 should throw an error when the first argument is an empty string. > not ok 15 should throw an error when the second argument is not a valid file > content. > --- > operator: throws > expected: |- > '/^TypeError.*Expected file content to be a string, Buffer or > Uint8Array, but got Set {} instead\\./' > actual: |- > { [TypeError: Expected file content to be a string, Buffer or > Uint8Array, but got Set(0) {} instead.] message: 'Expected file content to be > a string, Buffer or Uint8Array, but got Set(0) {} instead.' } > at: Test.<anonymous> (/<<PKGBUILDDIR>>/test.js:114:4) > stack: |- > TypeError: Expected file content to be a string, Buffer or Uint8Array, > but got Set(0) {} instead. > at outputFileSync (/<<PKGBUILDDIR>>/index.js:31:9) > at /<<PKGBUILDDIR>>/test.js:115:9 > at Test.throws (/usr/share/nodejs/tape/lib/test.js:632:9) > at Test.bound [as throws] (/usr/share/nodejs/tape/lib/test.js:99:32) > at Test.<anonymous> (/<<PKGBUILDDIR>>/test.js:114:4) > at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:99:32) > at Test.run (/usr/share/nodejs/tape/lib/test.js:117:31) > at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:99:32) > at Immediate.next [as _onImmediate] > (/usr/share/nodejs/tape/lib/results.js:88:19) > at processImmediate (internal/timers.js:464:21) > ... > ok 16 should throw an error when the third argument is provided but is > neither string nor an object. > not ok 17 should throw an error when the third argument is an invalid > encoding. > --- > operator: throws > expected: |- > '/^Error.*for exmaple \'utf8\' and \'ascii\', but got \'utf\\\\u0000\' > instead\\./' > actual: |- > { [Error: Expected a string to be a valid encoding, for exmaple 'utf8' > and 'ascii', but got 'utf\x00' instead.] message: 'Expected a string to be a > valid encoding, for exmaple \'utf8\' and \'ascii\', but got \'utf\\x00\' > instead.' } > at: Test.<anonymous> (/<<PKGBUILDDIR>>/test.js:126:4) > stack: |- > Error: Expected a string to be a valid encoding, for exmaple 'utf8' and > 'ascii', but got 'utf\x00' instead. > at outputFileSync (/<<PKGBUILDDIR>>/index.js:43:11) > at /<<PKGBUILDDIR>>/test.js:127:9 > at Test.throws (/usr/share/nodejs/tape/lib/test.js:632:9) > at Test.bound [as throws] (/usr/share/nodejs/tape/lib/test.js:99:32) > at Test.<anonymous> (/<<PKGBUILDDIR>>/test.js:126:4) > at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:99:32) > at Test.run (/usr/share/nodejs/tape/lib/test.js:117:31) > at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:99:32) > at Immediate.next [as _onImmediate] > (/usr/share/nodejs/tape/lib/results.js:88:19) > at processImmediate (internal/timers.js:464:21) > ... > ok 18 should throw an error when the third argument is an empty string. > ok 19 should throw an error when `encoding` option is not a string. > ok 20 should throw an error when `encoding` option is an empty string. > ok 21 should throw an error when `encoding` option is an invalid encoding. > ok 22 should throw an error when mode option is infinite. > ok 23 should throw an error when mode option exceeds the max safe integer. > ok 24 should throw an error when mode option is a negative number. > ok 25 should throw an error when mode option is a non-integer number. > ok 26 should throw an error when mode option is a non-integer number. > ok 27 should throw an error when mode option is an invalid octal. > ok 28 should throw an error when mode option is an invalid octal. > ok 29 should throw an error when mode option is neither string nor number. > > 1..29 > # tests 29 > # pass 27 > # fail 2 > > dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 The full build log is available from: http://qa-logs.debian.net/2022/04/12/node-output-file-sync_2.0.1-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220412&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---Source: node-output-file-sync Source-Version: 2.0.1-3 Done: Yadd <y...@debian.org> We believe that the bug you reported is fixed in the latest version of node-output-file-sync, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1009...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd <y...@debian.org> (supplier of updated node-output-file-sync package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Wed, 13 Apr 2022 12:56:57 +0200 Source: node-output-file-sync Architecture: source Version: 2.0.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers <pkg-javascript-de...@lists.alioth.debian.org> Changed-By: Yadd <y...@debian.org> Closes: 1009591 Changes: node-output-file-sync (2.0.1-3) unstable; urgency=medium . * Team upload * Fix test for nodejs >= 14 (Closes: #1009591) Checksums-Sha1: 4d4782358c861556087cfb9ec84cdf973830ebd0 2305 node-output-file-sync_2.0.1-3.dsc 80da16cb08a1be8332e5886bdac71939b32d2d87 10952 node-output-file-sync_2.0.1-3.debian.tar.xz Checksums-Sha256: 937e1b0032a25b992d82fbc505d3ddef8752d979fee7cd8cb72aefd83012cd72 2305 node-output-file-sync_2.0.1-3.dsc 85ae456858a12011e44ebed7ac524c743f58798db1864d102d5d35925b52fe36 10952 node-output-file-sync_2.0.1-3.debian.tar.xz Files: f6aadea59feed0032d707c07e43e2398 2305 javascript optional node-output-file-sync_2.0.1-3.dsc cff469e97bcef0967b9856df7b3b89d9 10952 javascript optional node-output-file-sync_2.0.1-3.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmJWrMQACgkQ9tdMp8mZ 7umd4Q//VPwlhrcfUIyhf/9cTT06u6qdvTKUWOS+vMk6XardZ1bhyo8X63Vm42U9 /CY9WI6hAQQmJcjNBmXt49TNAFrigjhhh6xQniRY65oH3hk5ICYV6kW2AjOiWg1b ttwO/LXeiMIHFgQnR9BEoMZ+hCrR2bKeAWbtJOotYIqt+4tinXpguyua6y9eUh5F omSZbKuMr0kNP2rdU3ll2mphxzKbwIVKZ4IG+k9YsDoVDGVzgQUUC3Dajl4uxt3f TE9b1JSBbC70Vl0X5bk0pTAic/4fBCTqL3XwyVvqlFPlZM0QUcZ1Rz0xRNyOFfTi rguay0qSlJQuQuYnN4dMCIiGWZoYRMI7PwHZxpSM37HvDOAYBoiG6ggSkCCbqTEi XnVJVVqXgAWNPOBHJWob8f4x9a/TD7tYgk4ld+mdQJA6olMLwCe0MAzMIKxIzL4U AncWnlEFuVjXyUYxYViQ2Q3xl4tNJFkavhvhjt5P70KvTx8aAdtzvyww/7q087nd mvb1uSi+LNg3+p35Zk7+gqSiRMr9ZzFlqumzqwUWvobgNCG4h2m0eE+RAROfAIFv SJiswytqrHix5XOsjgLhO46JfR7VvfnYcHPm2xJMa9tVBJADGufeoKUKtuBhQ534 k4cQdbisY5OiDkUaPF7nG3hADF1a8gbBr+jC17yY5v03NclLaek= =kO8s -----END PGP SIGNATURE-----
--- End Message ---
