Your message dated Mon, 10 Jun 2024 12:19:37 +0000
with message-id <e1sgdzt-00gqdg...@fasolo.debian.org>
and subject line Bug#1072602: fixed in node-parse-json 5.2.0+~cs5.1.7-2
has caused the Debian Bug report #1072602,
regarding node-parse-json: FTBFS: failing tests
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.)
--
1072602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-parse-json
Version: 5.2.0+~cs5.1.7-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
dh_auto_configure --buildsystem=nodejs
Link ./node_modules/@types/mocha -> /usr/share/nodejs/@types/mocha
Link lines-and-columns/node_modules/assert -> /usr/share/nodejs/assert
Link lines-and-columns/node_modules/@types/mocha ->
/usr/share/nodejs/@types/mocha
Link node_modules/lines-and-columns -> ../lines-and-columns
Link node_modules/@types/parse-json -> ../../types-parse-json
dh_auto_build --buildsystem=nodejs
No build command found, searching known files
Found debian/nodejs/lines-and-columns/build
cd ./lines-and-columns && sh -ex
../debian/nodejs/lines-and-columns/build
+ tsc --build tsconfig.build.json
+ mv build/index.js build/index.mjs
+ babeljs -o build/index.js --presets @babel/preset-env build/index.mjs
No build command found, searching known files
dh_auto_test --buildsystem=nodejs
ln -s ../. node_modules/parse-json
/bin/sh -ex debian/tests/pkg-js/test
+ tape test.js
TAP version 13
# main
ok 1 should be truthy
ok 2 should throw
not ok 3 should throw
---
operator: throws
expected: |-
'/Unexpected token "?}"?.*in foo\\.json/'
actual: |-
ErrorEXError { name: 'JSONError', codeFrame: ' 1 | {\n 2 | \t"foo": true,\n> 3 | }\n | ^',
fileName: 'foo.json', message: 'Expected double-quoted property name in JSON at position 16 while parsing
\'{\t"foo": true,}\' in foo.json \n\n 1 | {\n 2 | \t"foo": true,\n> 3 | }\n | ^\n' }
at: Test.<anonymous> (/<<PKGBUILDDIR>>/test.js:15:4)
stack: |-
JSONError: Expected double-quoted property name in JSON at position 16 while
parsing '{ "foo": true,}' in foo.json
1 | {
2 | "foo": true,
> 3 | }
| ^
at parseJson (/<<PKGBUILDDIR>>/index.js:29:21)
at /<<PKGBUILDDIR>>/test.js:17:4
at Test.throws (/usr/share/nodejs/tape/lib/test.js:630:3)
at Test.bound [as throws] (/usr/share/nodejs/tape/lib/test.js:95:17)
at Test.<anonymous> (/<<PKGBUILDDIR>>/test.js:15:4)
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 [as _onImmediate]
(/usr/share/nodejs/tape/lib/results.js:157:7)
at process.processImmediate (node:internal/timers:478:21)
...
not ok 4 should throw
---
operator: throws
expected: |-
'/Unexpected token "?}"?.*in foo\\.json/'
actual: |-
ErrorEXError { name: 'JSONError', fileName: 'foo.json', codeFrame: ' 1 | {\n 2 | \t"foo":
true,\n> 3 | }\n | ^', message: 'Expected double-quoted property name in JSON at position 16 while parsing
\'{\t"foo": true,}\' in foo.json \n\n 1 | {\n 2 | \t"foo": true,\n> 3 | }\n | ^\n' }
at: Test.<anonymous> (/<<PKGBUILDDIR>>/test.js:24:4)
stack: |-
JSONError: Expected double-quoted property name in JSON at position 16 while
parsing '{ "foo": true,}' in foo.json
1 | {
2 | "foo": true,
> 3 | }
| ^
at parseJson (/<<PKGBUILDDIR>>/index.js:29:21)
at /<<PKGBUILDDIR>>/test.js:25:3
at Test.throws (/usr/share/nodejs/tape/lib/test.js:630:3)
at Test.bound [as throws] (/usr/share/nodejs/tape/lib/test.js:95:17)
at Test.<anonymous> (/<<PKGBUILDDIR>>/test.js:24:4)
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 [as _onImmediate]
(/usr/share/nodejs/tape/lib/results.js:157:7)
at process.processImmediate (node:internal/timers:478:21)
...
not ok 5 should throw
---
operator: throws
expected: |-
'/Unexpected token "?}"?.*in foo\\.json/'
actual: |-
ErrorEXError { name: 'JSONError', fileName: 'foo.json', codeFrame: ' 1 | {\n 2 | \t"foo":
true,\n> 3 | }\n | ^', message: 'Expected double-quoted property name in JSON at position 16 while parsing
\'{\t"foo": true,}\' in foo.json \n\n 1 | {\n 2 | \t"foo": true,\n> 3 | }\n | ^\n' }
at: Test.<anonymous> (/<<PKGBUILDDIR>>/test.js:28:4)
stack: |-
JSONError: Expected double-quoted property name in JSON at position 16 while
parsing '{ "foo": true,}' in foo.json
1 | {
2 | "foo": true,
> 3 | }
| ^
at parseJson (/<<PKGBUILDDIR>>/index.js:29:21)
at /<<PKGBUILDDIR>>/test.js:30:4
at Test.throws (/usr/share/nodejs/tape/lib/test.js:630:3)
at Test.bound [as throws] (/usr/share/nodejs/tape/lib/test.js:95:17)
at Test.<anonymous> (/<<PKGBUILDDIR>>/test.js:28:4)
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 [as _onImmediate]
(/usr/share/nodejs/tape/lib/results.js:157:7)
at process.processImmediate (node:internal/timers:478:21)
...
# throws exported error error
ok 6 should throw
1..6
# tests 6
# pass 3
# fail 3
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/202406/
About the archive rebuild: The build was made on virtual machines
of type m6a.large and r6a.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 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.
--- End Message ---
--- Begin Message ---
Source: node-parse-json
Source-Version: 5.2.0+~cs5.1.7-2
Done: Yadd <y...@debian.org>
We believe that the bug you reported is fixed in the latest version of
node-parse-json, 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 1072...@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-parse-json 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: Mon, 10 Jun 2024 16:03:58 +0400
Source: node-parse-json
Architecture: source
Version: 5.2.0+~cs5.1.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
<pkg-javascript-de...@lists.alioth.debian.org>
Changed-By: Yadd <y...@debian.org>
Closes: 1072602
Changes:
node-parse-json (5.2.0+~cs5.1.7-2) unstable; urgency=medium
.
* Team upload
* Declare compliance with policy 4.7.0
* Fix test for nodejs 20 (Closes: #1072602)
Checksums-Sha1:
051bac1d73f771d5ec3e2192ca8f07453aafd60d 3031
node-parse-json_5.2.0+~cs5.1.7-2.dsc
7b0d2ed538cbd814eb9da9fcfea6144027c6aea8 5068
node-parse-json_5.2.0+~cs5.1.7-2.debian.tar.xz
Checksums-Sha256:
a594b8dc26741abffadd13357520e3a44ef43caccee53372f982978f9a460bd9 3031
node-parse-json_5.2.0+~cs5.1.7-2.dsc
1c8c3e3264c88e051fa42afeb387c31e320aa1b49183c3909b118b81f5165ae4 5068
node-parse-json_5.2.0+~cs5.1.7-2.debian.tar.xz
Files:
e9033f28ee128181d032d8a0b4bfacfb 3031 javascript optional
node-parse-json_5.2.0+~cs5.1.7-2.dsc
a09397a2c0007f3984631b000e985a2d 5068 javascript optional
node-parse-json_5.2.0+~cs5.1.7-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmZm6+kACgkQ9tdMp8mZ
7umsUg/9FJE457NoaRUdMx6dXu/LRorXb8w8Ym5xC/mCgTFiKxMUHU9s33Tay02O
nptTqFe8LO8d4fAfBuLFu0qjdAPSLJ7nKYV8WF/hVN8rXfJzZKfTgo3TiJ0Tjz4X
ZerMhws+NZKw3D4HGn+Ap+Eq9mEJrWyskNkhLxo/u7ynLS4JAtwCYEFElg9CAxCk
5bvL0kL/0Z/DsTmqb40YB++lK5tG2lHj7QHjzM3npwWHMJyzu05l+8QQ8xG20XJz
sYr9ziZOHAxJHnQRoitSEiy2kx3DOrUs5HrmdH81Vw5O5+lbRy5bYMaSeEG85M6S
I6Rdsq6ExM1EqZYz3i/W3kXbzSAEwkYEm0iKP8BOPHlieWV27z0jOT/YQgm+BvcX
fbk+ggtiUl1ZQX6MXabFSa92aIZm3U8b2qWVPMPoa93WC8s3S+jWEsnGmJAhW5CZ
Y+VzKcRSvBXPE0cDXogbFERdA5XGhETr/RROdamIkow0plL8MAlHohhluzBgkb7J
lJpQdHf0ATw1LywtxhY+piceQAPaV2cByLTc2prTANzUobMOivtTvxY/zQxDnwTZ
BpEEXo6ZKB6GnjGZsCHvOoXcXdY0JQvOnhgA+qE3PYtfS5EFuQsT/IzKi5I1DBBk
f/XAeE4lXSSwtcfEGkiVaUcqQhB/qLeGXZwAaShV8cDHRFjgdEM=
=uj+J
-----END PGP SIGNATURE-----
pgpm7g7QEYyRx.pgp
Description: PGP signature
--- End Message ---
