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

Yadd yadd at debian.org
Sun Sep 5 10:32:42 BST 2021


Le 05/09/2021 à 10:03, Jonas Smedegaard a écrit :
> 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.

Hi,

thanks for the report. Found and fixed in node-chai 4.3.0+ds+~4.2.14-3

Cheers,
Yadd



More information about the Pkg-javascript-devel mailing list