Your message dated Mon, 09 Mar 2026 22:27:55 +0000
with message-id <[email protected]>
and subject line Bug#1123414: fixed in node-crypto-browserify 3.12.0-8
has caused the Debian Bug report #1123414,
regarding node-crypto-browserify: 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 [email protected]
immediately.)
--
1123414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1123414
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:node-crypto-browserify
Version: 3.12.0-7
Severity: serious
Tags: ftbfs forky sid
Dear maintainer:
During a rebuild of all packages in unstable, this package failed to build.
Below you will find the last part of the build log (probably the most
relevant part, but not necessarily). If required, the full build log
is available here:
https://people.debian.org/~sanvila/build-logs/202512/
About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.
If you cannot 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 add an affects on src:node-crypto-browserify, so that this is still
visible in the BTS web page for this package.
Thanks.
--------------------------------------------------------------------------------
[...]
debian/rules clean
dh clean
dh_auto_clean --buildsystem=nodejs
rm -rf ./node_modules/.cache ./.nyc_output
rm ./node_modules/.cache
rm ./node_modules/.cache
dh_clean
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/crypto-browserify
/bin/sh -ex debian/tests/pkg-js/test
+ node test/index.js
(node:52) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security
and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or
Buffer.from() methods instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
TAP version 13
# createHash in crypto-browserify test sha1 against test vectors
# createHash in crypto-browserify test sha224 against test vectors
# createHash in crypto-browserify test sha256 against test vectors
# createHash in crypto-browserify test sha384 against test vectors
# createHash in crypto-browserify test sha512 against test vectors
# createHash in crypto-browserify test md5 against test vectors
# create-hash/browser test sha1 against test vectors
# create-hash/browser test sha224 against test vectors
# create-hash/browser test sha256 against test vectors
# create-hash/browser test sha384 against test vectors
# create-hash/browser test sha512 against test vectors
# create-hash/browser test md5 against test vectors
# createHmac in crypto-browserify hmac(sha1)
# hmac(sha1)
# createHmac in crypto-browserify hmac(sha224)
# hmac(sha224)
# createHmac in crypto-browserify hmac(sha256)
# hmac(sha256)
# createHmac in crypto-browserify hmac(sha384)
# hmac(sha384)
# createHmac in crypto-browserify hmac(sha512)
# hmac(sha512)
# createHmac in crypto-browserify hmac(md5)
# hmac(md5)
# create-hmac/browser hmac(sha1)
# hmac(sha1)
# create-hmac/browser hmac(sha224)
# hmac(sha224)
# create-hmac/browser hmac(sha256)
# hmac(sha256)
# create-hmac/browser hmac(sha384)
# hmac(sha384)
# create-hmac/browser hmac(sha512)
# hmac(sha512)
# create-hmac/browser hmac(md5)
# hmac(md5)
# pbkdf2
ok 1 should be strictly equal
ok 2 should be strictly equal
ok 3 should be strictly equal
ok 4 should be strictly equal
ok 5 should be strictly equal
# createECDH: secp256k1 uncompressed
ok 6 diff public keys
ok 7 equal secrets
# createECDH: secp256k1 compressed
ok 8 diff public keys
ok 9 equal secrets
# createECDH: secp256k1 set stuff
ok 10 same private key
ok 11 same public keys, uncompressed
ok 12 same public keys compressed
ok 13 same public keys hybrid
ok 14 equal secrets
# createECDH: secp224r1 uncompressed
ok 15 diff public keys
ok 16 equal secrets
# createECDH: secp224r1 compressed
ok 17 diff public keys
ok 18 equal secrets
# createECDH: secp224r1 set stuff
ok 19 same private key
ok 20 same public keys, uncompressed
ok 21 same public keys compressed
ok 22 same public keys hybrid
ok 23 equal secrets
# createECDH: prime256v1 uncompressed
ok 24 diff public keys
ok 25 equal secrets
# createECDH: prime256v1 compressed
ok 26 diff public keys
ok 27 equal secrets
# createECDH: prime256v1 set stuff
ok 28 same private key
ok 29 same public keys, uncompressed
ok 30 same public keys compressed
ok 31 same public keys hybrid
ok 32 equal secrets
# createECDH: prime192v1 uncompressed
ok 33 diff public keys
ok 34 equal secrets
# createECDH: prime192v1 compressed
ok 35 diff public keys
ok 36 equal secrets
# createECDH: prime192v1 set stuff
ok 37 same private key
ok 38 same public keys, uncompressed
ok 39 same public keys compressed
ok 40 same public keys hybrid
ok 41 equal secrets
# publicEncrypt/privateDecrypt
# can decrypt
ok 42 decrypt it properly
ok 43 decrypt it properly
# can round trip
ok 44 round trip it
ok 45 round trip it
# privateEncrypt/publicDecrypt
# can round trip
ok 46 round trip it
ok 47 round trip it
# get error message
ok 48 should be truthy
# randomBytes
ok 49 should be strictly equal
ok 50 should be truthy
ok 51 null
ok 52 should be strictly equal
ok 53 should be truthy
# randomBytes seem random
[116.77199928749558,126.068,139.22800071250444]
ok 54 should be truthy
ok 55 should be truthy
# get error message
ok 56 should be truthy
# pseudoRandomBytes
ok 57 should be strictly equal
ok 58 should be truthy
ok 59 null
ok 60 should be strictly equal
ok 61 should be truthy
# pseudoRandomBytes seem random
[116.58413384801662,130.322,139.41586615198338]
ok 62 should be truthy
ok 63 should be truthy
# rsa with sha256
# js sign and verify
ok 64 validates
# node sign and verify
ok 65 validates
# node sign and js verify
ok 66 validates
# js sign and node verify
ok 67 validates
# ec with sha1
# js sign and verify
ok 68 validates
# node sign and verify
skipping unsupported scheme ecdsa-with-SHA1
# node sign and js verify
skipping unsupported scheme ecdsa-with-SHA1
# js sign and node verify
skipping unsupported scheme ecdsa-with-SHA1
# get error message
ok 69 should be truthy
# randomfill
ok 70 should be strictly equal
ok 71 should be truthy
ok 72 null
ok 73 should be strictly equal
ok 74 should be truthy
# seems random
[116.44837673744507,133.44,139.55162326255493]
ok 75 should be truthy
ok 76 should be truthy
# run: 1
# ciphers: des3
ok 77 should be strictly equal
# run: 1
# ciphers: des-ede3-cbc
ok 78 should be strictly equal
# run: 1
# ciphers: des-ede3
ok 79 should be strictly equal
# run: 1
# ciphers: des-ede-cbc
ok 80 should be strictly equal
# run: 1
# ciphers: des-ede
ok 81 should be strictly equal
# run: 1
# ciphers: aes-128-ecb
ok 82 should be strictly equal
# run: 1
# ciphers: aes-192-ecb
ok 83 should be strictly equal
# run: 1
# ciphers: aes-256-ecb
ok 84 should be strictly equal
# run: 1
# ciphers: aes-128-cbc
ok 85 should be strictly equal
# run: 1
# ciphers: aes-192-cbc
ok 86 should be strictly equal
# run: 1
# ciphers: aes-256-cbc
ok 87 should be strictly equal
# run: 1
# ciphers: aes128
ok 88 should be strictly equal
# run: 1
# ciphers: aes192
ok 89 should be strictly equal
# run: 1
# ciphers: aes256
ok 90 should be strictly equal
# run: 1
# ciphers: aes-128-cfb
ok 91 should be strictly equal
# run: 1
# ciphers: aes-192-cfb
ok 92 should be strictly equal
# run: 1
# ciphers: aes-256-cfb
ok 93 should be strictly equal
# run: 1
# ciphers: aes-128-cfb8
ok 94 should be strictly equal
# run: 1
# ciphers: aes-192-cfb8
ok 95 should be strictly equal
# run: 1
# ciphers: aes-256-cfb8
ok 96 should be strictly equal
# run: 1
# ciphers: aes-128-cfb1
ok 97 should be strictly equal
# run: 1
# ciphers: aes-192-cfb1
ok 98 should be strictly equal
# run: 1
# ciphers: aes-256-cfb1
ok 99 should be strictly equal
# run: 1
# ciphers: aes-128-ofb
ok 100 should be strictly equal
# run: 1
# ciphers: aes-192-ofb
ok 101 should be strictly equal
# run: 1
# ciphers: aes-256-ofb
ok 102 should be strictly equal
# run: 1
# ciphers: aes-128-ctr
ok 103 should be strictly equal
# run: 1
# ciphers: aes-192-ctr
ok 104 should be strictly equal
# run: 1
# ciphers: aes-256-ctr
ok 105 should be strictly equal
# run: 1
# ciphers: aes-128-gcm
ok 106 should be strictly equal
# run: 1
# ciphers: aes-192-gcm
ok 107 should be strictly equal
# run: 1
# ciphers: aes-256-gcm
ok 108 should be strictly equal
# getCiphers
ok 109 get ciphers returns an array
# through crypto browserify works
/<<PKGBUILDDIR>>/test/aes.js:41
var crypter = crypto.createCipher(cipher, password)
^
TypeError: crypto.createCipher is not a function
at Test.<anonymous> (/<<PKGBUILDDIR>>/test/aes.js:41:24)
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:485:21)
Node.js v22.21.1
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
--------------------------------------------------------------------------------
--- End Message ---
--- Begin Message ---
Source: node-crypto-browserify
Source-Version: 3.12.0-8
Done: Yadd <[email protected]>
We believe that the bug you reported is fixed in the latest version of
node-crypto-browserify, 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.
Yadd <[email protected]> (supplier of updated node-crypto-browserify 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: Mon, 09 Mar 2026 22:32:46 +0100
Source: node-crypto-browserify
Architecture: source
Version: 3.12.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
<[email protected]>
Changed-By: Yadd <[email protected]>
Closes: 1123414
Changes:
node-crypto-browserify (3.12.0-8) unstable; urgency=medium
.
* Team upload
* Declare compliance with policy 4.7.3
* Drop "Rules-Requires-Root: no"
* debian/watch version 5
* Add fix for Nodejs 22 (Closes: #1123414)
Checksums-Sha1:
c9bbe76a79c0e49e56d55c374767d08107ce8e42 2387
node-crypto-browserify_3.12.0-8.dsc
9342bb6b57a54b96816bc2048b09a2af4a356f5f 5140
node-crypto-browserify_3.12.0-8.debian.tar.xz
Checksums-Sha256:
70f0dcf2602ce90232e16de9aa23cc186ab876c9dcc7fef16d6af826d3c657c8 2387
node-crypto-browserify_3.12.0-8.dsc
6f9354cf481200b0937e99cef69710bc59bd3d543343c8f5a9d6ad0f4c075371 5140
node-crypto-browserify_3.12.0-8.debian.tar.xz
Files:
abebb0b0521b413db948841bbf4822f0 2387 javascript optional
node-crypto-browserify_3.12.0-8.dsc
a3ad2506a0bc9d0579826318cf646726 5140 javascript optional
node-crypto-browserify_3.12.0-8.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmmvPUYACgkQ9tdMp8mZ
7ukA1Q/+NIjysS6Nnq69DW4OT17FKTFZY+ViwMntAvKrPjeGh5+QwOuZCGGe3PTJ
UQlRZCng9wpt2GbqWFFkZulsKJWCg0Z0WzJe6rk7GglX3jH6hn7Gow1F/xoWQj8e
+GVbn0MFDQ3HHpRR/iqWaDcNaZydFvKMS7jz89PDQeSI6PKzAlwOqyrTu9R1WQs2
zo0IBIJKYIrC35ih3qDFHZhGTuTSeXD63v+ntzzohmBfJ9gHA3bwhjzf4YTbb74P
87XWsOKsgu5qUXdSVNS9hiavIpCB9+lsuYhaAIGsA7Xysogb++HpIoUqJuPoT8oj
GWF9kEsb4gK0Yupdjj6rBT40aKiYNFK4QjcggL4bZy188BUp6s3E89f4yyDthXHy
/fqTxvSYzszuV15y4F+t7w/bAE7A6AEPMCmnzsqYfYPmMoHGSzj7C+nM/tD6Rbfm
LxPkjdO7o+gV0Z/G1SJXYZdz24Imb2aH9uesg5JsCocZhoKfNhmH8rBwTTBL1RDR
jXcTim0NKiCBbONph9dBaDaYBWK2JGtnOhj0kOWWyiB0DoL4muwzD1dqt8yIkz9I
sfORQ2iYO7C3r5Duu1fc7Bj09pES1ajaN/lGdMo/SaMF0TL92+3sxxbfh0bUO1RK
Q1ucK6TJkrB7Gz/TqK2nEjK2LehljhZqOazsuedwcFir88b7hZU=
=OZEu
-----END PGP SIGNATURE-----
pgpanMq_uJRG2.pgp
Description: PGP signature
--- End Message ---
