Your message dated Sun, 12 Apr 2015 11:49:48 +0000
with message-id <[email protected]>
and subject line Bug#781710: fixed in nodejs 0.10.29~dfsg-2
has caused the Debian Bug report #781710,
regarding nodejs FTBFS in jessie. test-crypto-stream.js fails (again)
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 [email protected]
immediately.)


-- 
781710: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781710
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nodejs
Severity: serious
Version: 0.10.29~dfsg-1.1

nodejs is failing to build with failure of the test "test-crypto-stream.js"

http://buildd.raspbian.org/status/fetch.php?pkg=nodejs&arch=armhf&ver=0.10.29~dfsg-1.1&stamp=1427831511

[02:22|%  13|+  82|-   0]: release test-crypto-stream

=== release test-crypto-stream ===
Path: simple/test-crypto-stream
assert.js:92
  throw new assert.AssertionError({
        ^
AssertionError: false == true
    at Decipheriv.end (/«PKGBUILDDIR»/test/simple/test-crypto-stream.js:73:5)
    at Decipheriv.<anonymous>  (/«PKGBUILDDIR»/test/common.js:198:15)
    at Decipheriv.emit (events.js:117:20)
    at done (_stream_transform.js:190:19)
    at _stream_transform.js:131:9
    at Decipheriv.Cipher._flush (crypto.js:269:5)
    at Decipheriv.<anonymous>  (_stream_transform.js:130:12)
    at Decipheriv.g (events.js:180:16)
    at Decipheriv.emit (events.js:117:20)
    at finishMaybe (_stream_writable.js:360:12)
Command: out/Release/node /«PKGBUILDDIR»/test/simple/test-crypto-stream.js



This failure was initially seen on a raspbian jessie autobuilder but I was able to reproduce it locally on Debian jessie armhf and Debian jessie i386 so it's not a raspbian specific issue.

I have not tested whether this also happens in sid. I have not tested on architectures other than armhf and i386.

I suspect this is caused by recent updates to openssl.

Given that this is the second time this has happened recently I wonder if the test in question is too specific in what it expects.

I tried looking at the code of the test but didn't get anywhere (it doesn't help that my javascript knowlage is very very low).
--- End Message ---
--- Begin Message ---
Source: nodejs
Source-Version: 0.10.29~dfsg-2

We believe that the bug you reported is fixed in the latest version of
nodejs, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jérémy Lal <[email protected]> (supplier of updated nodejs 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 [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 12 Apr 2015 01:59:43 +0200
Source: nodejs
Binary: nodejs-dev nodejs nodejs-dbg nodejs-legacy
Architecture: source all amd64
Version: 0.10.29~dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 
<[email protected]>
Changed-By: Jérémy Lal <[email protected]>
Description:
 nodejs     - evented I/O for V8 javascript
 nodejs-dbg - evented I/O for V8 javascript (debug)
 nodejs-dev - evented I/O for V8 javascript (development files)
 nodejs-legacy - evented I/O for V8 javascript (legacy symlink)
Closes: 781710
Changes:
 nodejs (0.10.29~dfsg-2) unstable; urgency=medium
 .
   * Update 2015_fix_test_crypto_stream.patch with a less strict
     check for that test - coming from upstream. Also use DEP-3 format.
     Closes: #781710.
Checksums-Sha1:
 b577fc680581169e59947731c26501fe7a29024f 2377 nodejs_0.10.29~dfsg-2.dsc
 11bace3bc229274b6e59c4f262287ee4dd1a4e09 40340 
nodejs_0.10.29~dfsg-2.debian.tar.xz
 09df177623423cb20fa221a5ea0231d60700f437 80366 
nodejs-legacy_0.10.29~dfsg-2_all.deb
 beb71881a679ace13d89922c0cea405c6704d1ca 248284 
nodejs-dev_0.10.29~dfsg-2_amd64.deb
 9572aaddb9ac9644ceee37865e01408d42c5c2fa 648096 nodejs_0.10.29~dfsg-2_amd64.deb
 1cbe6cb19e32dbc2b48e0b6f2913c22ef2d5ae56 1026964 
nodejs-dbg_0.10.29~dfsg-2_amd64.deb
Checksums-Sha256:
 5496484b75278c631e25cd3b1c862179faf1a2c57fc6be415abe19363dc68259 2377 
nodejs_0.10.29~dfsg-2.dsc
 210a22bcd7271be149d0d34c672a284f97a14b0f7c928b3a74a3aade3689e81a 40340 
nodejs_0.10.29~dfsg-2.debian.tar.xz
 1c1927d9f15fe76bc0220af8de62e31b1bdef2932af44a27a22bdde3eed9df5a 80366 
nodejs-legacy_0.10.29~dfsg-2_all.deb
 1ddca42b9f87c77c3da120f777d7501edc945157bd1a4396536fbf9839c8ae63 248284 
nodejs-dev_0.10.29~dfsg-2_amd64.deb
 50e8e6abf43322a4f2d37be2613c3ef6fa78c2b5db3a6849bc015c7a69443075 648096 
nodejs_0.10.29~dfsg-2_amd64.deb
 1ba1136046501f989af40da4e69e25c6fd01ec5b45ead746891479e33d970c03 1026964 
nodejs-dbg_0.10.29~dfsg-2_amd64.deb
Files:
 89b87a7426a77f58da69c23686210b1d 2377 web extra nodejs_0.10.29~dfsg-2.dsc
 3d97794de2f81a539491f459864fb02a 40340 web extra 
nodejs_0.10.29~dfsg-2.debian.tar.xz
 a7e9775e881f46a6df338325448ce035 80366 web extra 
nodejs-legacy_0.10.29~dfsg-2_all.deb
 20f5f2b3b1cf41f02533d4da7e4f5364 248284 devel extra 
nodejs-dev_0.10.29~dfsg-2_amd64.deb
 986c48560acaba4c55a7b0972feaa710 648096 web optional 
nodejs_0.10.29~dfsg-2_amd64.deb
 68bea3519e159486d7130bf505f87e4f 1026964 debug extra 
nodejs-dbg_0.10.29~dfsg-2_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJVKboDAAoJEGYRwF7dOfN0GnAQAK8PY/IinjxkALam/86geQ6y
5ELDWz6v2wecy6fbLkk6mGsLagee5mih8uF41wWCHoSv1f59AaPy8jG3rxSwCfMV
9hkoHtip21nArFDwbHRDxabn1Ga1fNt9pROtp10HFJWKiPbs33sDbM+DeJe6GYuG
OfgnIXxHKxhhgDA5TJjtlg6tDXCS8MwZUs47WVidjnwP/sH0yaHQ2NsBKMfZXkxT
LqZPFO7dMyP+w22SHrt7w2ugtvWGwGcPsCbkaNQ/TQRN5656fa34Dm6YYSwUNd6a
nNxLBzQ4FFnPAomXf546An0xux+tuZGXOLgq7l59v2kc9c3rLyVuW8xGVBbpSfDq
uElwmfoQ/8F7g31Pn4xARyLCddsA/cL3e4Zl8k6irINmUjktmot+KOIqnSRyBouz
9M3F4LgEmtImTta8p/ndn3IiBfBCucJqCk2up0EfAChvjhG/wlYlF+hpaFF83T88
AzYl+xybpa4e2XlnL1ZTccxkwXE4hjg8w6e94swYmXFdTDrXLXaRwFIKVLiAJLd7
kdUFZDpUPPUbm8mbo9VftGITlb3CbRK2Ldvgh3L+0y78fsodXPQbxKyeCQSneJ8V
35UqfACnoEyj9pUFnZbM/gzwKyXm7O/OAOgsmYRGSvBvSqPSaEJqIszSfzuMZfhM
NnAAjt59dwOacN1fZvZJ
=Tt6w
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to