Package: nodejs Version: 18.19.1+dfsg-6 Severity: important Tags: sid control: affects -1 src:openssl User: pkg-openssl-de...@lists.alioth.debian.org Usertags: openssl-3.2
Hi, I rebuilt nodejs in unstable against openssl 3.2 in experimental an a few tests failed: | Failed tests: | ./node /<<PKGBUILDDIR>>/test/parallel/test-crypto-rsa-dsa.js | ./node /<<PKGBUILDDIR>>/test/parallel/test-tls-alert-handling.js | ./node /<<PKGBUILDDIR>>/test/parallel/test-tls-client-auth.js | ./node /<<PKGBUILDDIR>>/test/parallel/test-tls-empty-sni-context.js | ./node --expose-internals /<<PKGBUILDDIR>>/test/parallel/test-tls-enable-trace.js | ./node --expose-internals /<<PKGBUILDDIR>>/test/parallel/test-tls-enable-trace-cli.js | ./node /<<PKGBUILDDIR>>/test/parallel/test-tls-getcipher.js | ./node /<<PKGBUILDDIR>>/test/parallel/test-tls-junk-server.js | ./node /<<PKGBUILDDIR>>/test/parallel/test-tls-psk-circuit.js | ./node /<<PKGBUILDDIR>>/test/parallel/test-tls-set-ciphers.js | ./node /<<PKGBUILDDIR>>/test/parallel/test-tls-junk-closes-server.js Any idea how to proceed? I've been reading https://github.com/nodejs/node/issues/51152 but I don't think 3.2 support has been integrated somewhere as they just discussed their fork part and so on. I've been looking at the errors and some are "error code changed". I *think* the trace errors changed also slightly. I don't know why get/set-ciphers failed. Sebastian