[Pkg-javascript-devel] help understanding autopkgtest failures for node-eslint-visitor-keys

[Nilesh Patra]

On 3/1/22 2:34 AM, Jonas Smedegaard wrote:
>> Simple solution is to create a temporary dir; or use $AUTOPKGTEST_TMP
>> (latter is best)
>>
>> I have attached a patch that fixes this, please apply and upload.
>>
>> Hope that helps.
> 
> Thanks, very helpful.
> 
> Do you happen to know where this behaviour is documented upstream?

Unfortunately not. Actually, a few months back, I saw this in another package (IIRC, that was yours too)
I just fiddled around a bit and found out back then.

I "guess" it might not be even documented since AFAICS, the usual upstream way of vendoring
npm/yarn modules would not do a 'require' locally w/o building the package, 'within the source code itself'
that'd be quite unusual to do.

The way it happens in debian with ('/usr/share' ; '/usr/lib/') especially with the autopkgtest environment
is somewhat special/different.

> I ask because I experience another possibly similar error with failure
> locating chai for node-eslint-visitor-keys 3.3.0+~0.0.51, where it is
> not an option to switch directory.

I think in such a case you can do either:

a) Remove package.json/interfering stuff in autopkgtest environment and then run a 'require'
b) Copy relevant/required files/dirs to $AUTOPKGTEST_TMP, change directory and then do a 'require' there

Hope that helps again.

Regards,
Nilesh

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20220301/517233b6/attachment.sig>