Severity: important
Tags: moreinfo
Le mar. 17 mars 2020 à 14:45, Josh de Kock <j...@itanimul.li> a écrit :
>
> Hi,
>
> This still occurs for me. I have a armhf chroot of Sid. It seems to be
> using a node path relative to the current directory (as far as I can
> tell). These paths should probably be /usr prefixed (and not relative to
> cwd), but I wouldn't know where to begin fixing this.
>
Yes, they should.
I don't understand how this chroot ends up with those paths either.
How did you set it up ?
I tried a buster armhf chroot:
- nodejs 10.21.0
- npm 5.8.0+ds6-4+deb10u1
a sid ppc64el chroot:
- nodejs 12.18.3
- npm 6.14.6+ds-1
in both cases, i got correct resolve paths, and this works:
node -e "require('y18n');"
Since most of the report talk about node-y18n i suppose it was this module
that was affected during a transition of /usr/lib/nodejs to
/usr/share/nodejs.
To keep things simple i'll leave it here open (without reassigning) for a
while,
unless someone reproduces it again.
Jérémy
