[Pkg-javascript-devel] Bug#930034: Bug#930034: nodejs: yarnpkg unable to install files with node 10.15
Jérémy Lal
kapouer at melix.org
Wed Jun 5 19:02:13 BST 2019
Le mer. 5 juin 2019 à 18:15, Hubert Chathi <hubert at uhoreg.ca> a écrit :
> Package: nodejs
> Version: 10.15.2~dfsg-2
> Severity: important
>
> When using nodejs 10.15.2, yarnpkg is unable to copy files to install
> dependencies. eg:
>
> ~/tmp$ mkdir foo
> ~/tmp$ cd foo/
> ~/tmp/foo$ yarnpkg init
> yarn init v1.13.0
> question name (foo):
> question version (1.0.0):
> question description:
> question entry point (index.js):
> question repository url:
> question author:
> question license (MIT):
> question private:
> success Saved package.json
> Done in 14.00s.
> ~/tmp/foo $ yarnpkg add leftpad
> yarn add v1.13.0
> info No lockfile found.
> [1/4] Resolving packages...
> warning leftpad at 0.0.1: Use the built-in String.padStart function instead
> [2/4] Fetching packages...
> [3/4] Linking dependencies...
> error An unexpected error occurred: "EINVAL: invalid argument, copyfile
> '/home/hubert/.cache/yarn/v4/npm-leftpad-0.0.1-86b1a4de4face180ac545a83f1503523d8fed115/node_modules/leftpad/CHANGELOG.md'
> -> '/home/hubert/tmp/foo/node_modules/leftpad/CHANGELOG.md'".
> info If you think this is a bug, please open a bug report with the
> information provided in "/home/hubert/tmp/foo/yarn-error.log".
> info Visit https://yarnpkg.com/en/docs/cli/add for documentation about
> this command.
>
> It works correctly with nodejs 8.11.1 from stretch-backports, hence
> filing this issue against nodejs rather than yarnpkg. (But FWIW, the
> yarnpkg version is 1.13.0-1).
>
> The yarn-error.log doesn't seem to include any useful information, but
> I've attached it for completeness.
>
> -- System Information:
> Debian Release: 9.9
>
I can't reproduce on debian 10 a.k.a. Buster, which is the version of debian
that distributes nodejs 10.15.2.
Also there is no backport available (that i know of) on debian 9.9.
I would also like to point out that if you found a bug installing a node
module,
the bug it probably in either of:
- the node module itself
- node-gyp if the module is an addon
- yarnpkg, npm
Jérémy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20190605/d45031dc/attachment.html>
More information about the Pkg-javascript-devel
mailing list