Rebuilding it with latest nodejs fails with:

AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:
+ actual - expected

  Comparison {
+   code: 'ERR_UNKNOWN_ENCODING',
+   message: 'Unknown encoding: buffer',
-   code: 'ERR_INVALID_ARG_TYPE',
-   message: 'Second argument must be a buffer',
    name: 'TypeError'
  }

    at Socket.<anonymous> (/build/reproducible-path/node-readable-stream-4.7.0+~cs9.0.2/test/parallel/test-stream-base-typechecking.js:17:16)
    at Socket.<anonymous> (/build/reproducible-path/node-readable-stream-4.7.0+~cs9.0.2/test/common/index.js:412:15)
    at Socket.wrapper (node:events:639:12)
    at Socket.emit (node:events:514:28)
    at afterConnect (node:net:1996:10)
    at afterConnectMultiple (node:net:2103:3) {
  generatedMessage: true,
  code: 'ERR_ASSERTION',
  actual: TypeError [ERR_UNKNOWN_ENCODING]: Unknown encoding: buffer
      at _write (node:internal/streams/writable:472:15)
      at Writable.write (node:internal/streams/writable:512:10)
      at assert.throws.name (/build/reproducible-path/node-readable-stream-4.7.0+~cs9.0.2/test/parallel/test-stream-base-typechecking.js:19:20)
      at getActual (node:assert:611:5)
      at ok.throws (node:assert:759:24)
      at Socket.<anonymous> (/build/reproducible-path/node-readable-stream-4.7.0+~cs9.0.2/test/parallel/test-stream-base-typechecking.js:17:16)
      at Socket.<anonymous> (/build/reproducible-path/node-readable-stream-4.7.0+~cs9.0.2/test/common/index.js:412:15)
      at Socket.wrapper (node:events:639:12)
      at Socket.emit (node:events:514:28)
      at afterConnect (node:net:1996:10) {
    code: 'ERR_UNKNOWN_ENCODING'
  },
  expected: {
    name: 'TypeError',
    code: 'ERR_INVALID_ARG_TYPE',
    message: 'Second argument must be a buffer'
  },
  operator: 'throws',
  diff: 'simple'
}

Hello,

Bug #1146899 in node-readable-stream reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/js-team/node-readable-stream/-/commit/dfa3488ca14a99b36f60138abd4e899795d3aa0e
------------------------------------------------------------------------
patch: fix test with node 24.20. Closes: #1146899.
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1146899

We believe that the bug you reported is fixed in the latest version of
node-readable-stream, 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 1146899@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jérémy Lal <kapouer@melix.org> (supplier of updated node-readable-stream 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 ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sun, 06 Sep 2026 22:24:05 +0200
Source: node-readable-stream
Architecture: source
Version: 4.7.0+~cs9.0.2-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers <pkg-javascript-devel@lists.alioth.debian.org>
Changed-By: Jérémy Lal <kapouer@melix.org>
Closes: 1146899
Changes:
 node-readable-stream (4.7.0+~cs9.0.2-7) unstable; urgency=medium
 .
   * patch: fix test with node 24.20. Closes: #1146899.
Checksums-Sha1:
 0432a127f3304931e07a8241e33196ddd5ed3341 3167 node-readable-stream_4.7.0+~cs9.0.2-7.dsc
 2b302fa0a179a33d51f9b5e9bc5748dd1a90112a 10496 node-readable-stream_4.7.0+~cs9.0.2-7.debian.tar.xz
 9fb4f1e9374f5f2a29ee388caa949e1e0291d580 26318 node-readable-stream_4.7.0+~cs9.0.2-7_source.buildinfo
Checksums-Sha256:
 d63839824afb5a3cabe4269e5041d76462728ffaca5172231c86b88919ae4eb2 3167 node-readable-stream_4.7.0+~cs9.0.2-7.dsc
 fb5e15d5ccd8d3550f134632627994798251264e24785a26bb99addad10f72b3 10496 node-readable-stream_4.7.0+~cs9.0.2-7.debian.tar.xz
 c1cb6581e8c4fd5d04ca08aadabf207323b81e408c18a4cc1fce94ad395f9c31 26318 node-readable-stream_4.7.0+~cs9.0.2-7_source.buildinfo
Files:
 e38e9d969a79646863d0105c10b364e8 3167 javascript optional node-readable-stream_4.7.0+~cs9.0.2-7.dsc
 0a9673d3a2d9266dfee2aa873e391e97 10496 javascript optional node-readable-stream_4.7.0+~cs9.0.2-7.debian.tar.xz
 009dc3e706b199ffd01b3c9730f50583 26318 javascript optional node-readable-stream_4.7.0+~cs9.0.2-7_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQJGBAEBCAAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAmqdy/gSHGthcG91ZXJA
bWVsaXgub3JnAAoJEGYRwF7dOfN04HwP/Ai39mRZTQdgCra+XUWsuy7xoB+Z/dRt
dHuwhyFCJnm/33I36Sl7JOGmWDzo0hnD3M19gqrN7i6BlivoLAeP8vIng1gp3Gt7
+xMjS8qeuI7T6YaAkvEDXhTatnZUpo2COtpUwEOAAvT+5T/ioWwJn1JoAoBFXX+/
OWj4vFwbyN1ZbRJVeVP4rHpIa2asnYavHX2U5e0vM5rBdCenXT+iSfiJU3djQIkw
nnXh6DSjheL5R20CHO+9juZVTeqacJ/aKAOxUMqFNMwQNIvaN9twp+Zh4SDXE5KW
2cLGeurlRXT1X5bqcECO8Vl0mq6/i7/BnY74g5/mUrBXZ3aSOzLmJDDROmdgC//N
mSXQOJekEAWq6kcjIbnqDvrPhd6j5LJUC7VaSkMDWISGxKSUwiVU0Wp7k3229PB4
X7ZGex/vc707J9YK8s340SVsVkByJVnGWJioQQP9iSuvC8v7H0QXD8GTDvvRcE4e
4iO29l3c8O2/L9mi0mE3MQPCDIV9al4G6ElEhD8yiZalkIROKpkwIroymDM/jVov
jmYtUzoY8PmUnSLXdHvp0x3JlawuwaSVkDRaijj3lN3fxHsTb17Nhr42ioRUo2Dr
7dP76eQ4B49VcR/T81pzCJs7nXairmyYHWVM6hNn4rNuiJ1Pm3vkmIJLe+SHRw7K
zY/kNyJMXXeT
=1sAX
-----END PGP SIGNATURE-----

Hi Jérémy,

Did this actually work?  I guess it did build, but
https://tracker.debian.org/pkg/node-readable-stream shows red across the
board for node-readable-stream's own autopkgtests, e.g.
https://ci.debian.net/packages/n/node-readable-stream/testing/amd64/75233399/.

Thanks,

Le mar. 8 sept. 2026 à 11:13, Colin Watson <cjwatson@debian.org> a écrit :

That's because it fails with nodejs in testing.
It should migrate to testing along with nodejs, though.

You'll need to get the release team's help for that, then.  (Or to add a
Breaks; but it looks as though it may be a test-only problem, in which
case manual intervention by the release team is probably better.)

Thanks,

Le 08/09/2026 à 11:20, Colin Watson a écrit :

Tomorrow (or maybe Thursday) we may have a big migration (babel 8,
typescript 6) - after node-rollup-plugin-typescript. This may fix a lot
of false-positive regressions in DebCI. Maybe this will help nodejs
migration.

Regards,
Xavier