[Pkg-javascript-devel] broken build-dependencies in testing on node-chai.

[Jonas Smedegaard]

Quoting Peter Green (2021-09-04 23:19:58)
> 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?

Not a coordinated change (as far as I am aware), but possibly the change is sensible regardless.

I suggest file as an RC bugreport against mocha, and have the maintainer 
of mocha handle it from there - e.g. file bugreports as appropriate and 
aassess if appropriate to reinstate the virtual package until those 
other bugreports are addresses.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20210905/0aece5d7/attachment.sig>