I'm getting an error trying to install version 5.6.0, specifically trying to unpack the tar file on Ubuntu Linux. The problem seems to be that some VCS conflict files were left behind in the readable-stream module which contain colons in the file name, and tar if trying to interpret these as a remote file.
Technically, I'm still able to unpack the remaining files, but the tar command exits with a non-zero exit code as a result, so automated installations (such as nvm) fail.
Here are commands that reproduce this:
$ wget https://nodejs.org/dist/v5.6.0/node-v5.6.0-linux-x64.tar.xz
4 unxz node-v5.6.0-linux-x64.tar.xz
$ tar -xf node-v5.6.0-linux-x64.tar >/dev/null
tar: node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/LICENSE~8d21794... deps\: upgrade npm to 3.6.0: Cannot open: Protocol error
tar: node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/LICENSE~8d21794... deps\: upgrade npm to 3.6.0_0: Cannot open: Protocol error
tar: node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/duplex.js~8d21794... deps\: upgrade npm to 3.6.0: Cannot open: Protocol error
tar: node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/writable.js~8d21794... deps\: upgrade npm to 3.6.0: Cannot open: Protocol error
tar: node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/.npmignore~8d21794... deps\: upgrade npm to 3.6.0: Cannot open: Protocol error
tar: node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/node_modules/string_decoder/index.js~8d21794... deps\: upgrade npm to 3.6.0: Cannot open: Protocol error
tar: node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/node_modules/string_decoder/README.md~8d21794... deps\: upgrade npm to 3.6.0: Cannot open: Protocol error
tar: node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/node_modules/string_decoder/LICENSE~8d21794... deps\: upgrade npm to 3.6.0: Cannot open: Protocol error
tar: node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/node_modules/string_decoder/.npmignore~8d21794... deps\: upgrade npm to 3.6.0: Cannot open: Protocol error
tar: node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/node_modules/core-util-is/README.md~8d21794... deps\: upgrade npm to 3.6.0: Cannot open: Protocol error
tar: node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/node_modules/core-util-is/float.patch~8d21794... deps\: upgrade npm to 3.6.0: Cannot open: Protocol error
tar: node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/node_modules/core-util-is/lib/util.js~8d21794... deps\: upgrade npm to 3.6.0: Cannot open: Protocol error
tar: node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/node_modules/isarray/index.js~8d21794... deps\: upgrade npm to 3.6.0: Cannot open: Protocol error
tar: node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/node_modules/isarray/README.md~8d21794... deps\: upgrade npm to 3.6.0: Cannot open: Protocol error
tar: node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/node_modules/isarray/component.json~8d21794... deps\: upgrade npm to 3.6.0: Cannot open: Protocol error
tar: node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/passthrough.js~8d21794... deps\: upgrade npm to 3.6.0: Cannot open: Protocol error
tar: node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/transform.js~8d21794... deps\: upgrade npm to 3.6.0: Cannot open: Protocol error
To be explicit, here is the collection of filenames that contain colons, that are causing tar to have problems:
$ tar tf ./node-v5.6.0-linux-x64.tar | grep 'readable-stream[^:]*:'
node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/LICENSE~8d21794... deps: upgrade npm to 3.6.0
node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/LICENSE~8d21794... deps: upgrade npm to 3.6.0_0
node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/duplex.js~8d21794... deps: upgrade npm to 3.6.0
node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/writable.js~8d21794... deps: upgrade npm to 3.6.0
node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/.npmignore~8d21794... deps: upgrade npm to 3.6.0
node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/node_modules/string_decoder/index.js~8d21794... deps: upgrade npm to 3.6.0
node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/node_modules/string_decoder/README.md~8d21794... deps: upgrade npm to 3.6.0
node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/node_modules/string_decoder/LICENSE~8d21794... deps: upgrade npm to 3.6.0
node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/node_modules/string_decoder/.npmignore~8d21794... deps: upgrade npm to 3.6.0
node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/node_modules/core-util-is/README.md~8d21794... deps: upgrade npm to 3.6.0
node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/node_modules/core-util-is/float.patch~8d21794... deps: upgrade npm to 3.6.0
node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/node_modules/core-util-is/lib/util.js~8d21794... deps: upgrade npm to 3.6.0
node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/node_modules/isarray/index.js~8d21794... deps: upgrade npm to 3.6.0
node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/node_modules/isarray/README.md~8d21794... deps: upgrade npm to 3.6.0
node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/node_modules/isarray/component.json~8d21794... deps: upgrade npm to 3.6.0
node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/passthrough.js~8d21794... deps: upgrade npm to 3.6.0
node-v5.6.0-linux-x64/lib/node_modules/npm/node_modules/readable-stream/transform.js~8d21794... deps: upgrade npm to 3.6.0
I'm getting an error trying to install version 5.6.0, specifically trying to unpack the tar file on Ubuntu Linux. The problem seems to be that some VCS conflict files were left behind in the
readable-streammodule which contain colons in the file name, andtarif trying to interpret these as a remote file.Technically, I'm still able to unpack the remaining files, but the
tarcommand exits with a non-zero exit code as a result, so automated installations (such as nvm) fail.Here are commands that reproduce this:
To be explicit, here is the collection of filenames that contain colons, that are causing tar to have problems: