I have noticed that a bunch of javascript packages now have unsatisfiable 
build-dependencies in testing.

eslint
node-eslint-plugin-eslint-plugin
node-eslint-scope
node-espree
node-esquery
node-file-entry-cache
node-ip-address
node-lunr
node-mock-fs
node-node-rsa
node-serialize-javascript
node-solid-keychain
node-thenby
node-token-types
node-trust-json-document
node-trust-keyto
node-trust-webcrypto
node-v8flags

I looked through all of them and (unless I made a mistake) the missing
build-dependency in all cases is node-chai.

It seems that node-chai was formerly a virtual package provided by the
chai binary package (which in turn is built from the node-chai source
package) but this was dropped between the version in bullseye and the
version in bookworm/sid. The changelog makes no mention of this change.

Was this a deliberate change?

If this was a deliberate change do you want to deal with the reverse
dependencies in bulk or should I file individual bug reports against
them?


--
Pkg-javascript-devel mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Reply via email to