n latest works but n io latest fail with cp: cannot stat

Created on 29 Jul 2015 · 18Comments · Source: tj/n

OS: Kubuntu 15.04

cp: cannot stat ‘/usr/local/n/versions/io//bin’: No such file or directory
cp: cannot stat ‘/usr/local/n/versions/io//lib’: No such file or directory
cp: cannot stat ‘/usr/local/n/versions/io//share’: No such file or directory

Source

tuananh

Most helpful comment

@tuananh Upgrade OpenSSL first of all. Thanks @maxrimue.

1__seanwang_192_____zsh_

Sean-Wang on 18 Dec 2015

👍2

All 18 comments

Does n io ls get you any output?

maxrimue on 29 Jul 2015

@maxrimue n io ls gives me a blank line

tuananh on 29 Jul 2015

Try to upgrade OpenSSL

maxrimue on 29 Jul 2015

i have OpenSSL 1.0.1f 6 Jan 2014. sudo apt-get update and upgrade do nothing as everything is updated.

tuananh on 29 Jul 2015

@tuananh I have no idea why Ubuntu offers you no newer version of OpenSSL, but the version you run, 1.0.1f, is really old. In this version, the heartbleed bug wasn't yet fixed, which is why some servers don't work with an OpenSSL version below 1.0.1g. I'll try to find out what's going on here

maxrimue on 29 Jul 2015

@tuananh Does apt-get dist-upgrade upgrade OpenSSL?

maxrimue on 29 Jul 2015

@maxrimue that one does nothing as well.

tuananh on 29 Jul 2015

curl -Is https://iojs.org/ | head -n 1 should get you HTTP/1.1 200 OK, if not, it's definitely something wrong with your system rather than n or your installation of n

maxrimue on 31 Jul 2015

On Ubuntu 14.04:

sudo n latest sometime gives:

$ sudo n latest
cp: cannot stat ‘/usr/local/n/versions/node//bin’: No such file or directory
cp: cannot stat ‘/usr/local/n/versions/node//lib’: No such file or directory
cp: cannot stat ‘/usr/local/n/versions/node//share’: No such file or directory

sometime gives:

$ sudo n latest

     install : node-v0.12.7
       mkdir : /usr/local/n/versions/node/0.12.7
       fetch : https://nodejs.org/dist/v0.12.7/node-v0.12.7-linux-x64.tar.gz

sometime gives:

$ sudo n latest

     install : node-v4.0.0
       mkdir : /usr/local/n/versions/node/4.0.0
       fetch : https://nodejs.org/dist/v4.0.0/node-v4.0.0-linux-x64.tar.gz

husless on 12 Sep 2015

👍1

@husless What do you mean by 'sometimes'? Did you do anything to change the output or behaviour of the program or your system?

maxrimue on 13 Sep 2015

@maxrimue Sorry, I did not discribe it clearly. I did not change the anything of the program or the system. I wanted to upgrade node to node-v4.0.0, and executed commands in terminal:

sudo npm install -g n
sudo n latest

I tried sudo n latest at least 5 times sequently. It gave me either the cp: cannot stat ... error or installing node-v0.12.7.

I've finally upgraded node to node-v4.0.0 using sudo n latest.

husless on 15 Sep 2015

So node and io have merged. We need to look at filter logic for latest and stable to make sure everything is good now that the major version for node is not zero.

ghost on 15 Sep 2015

@tedgaydos I think there won't be any more test builds that aren't completely stable (like 0.11.x), so I think we could just pull the stable option completely and let latest just pull the latest (so from https://nodejs.org/dist/latest/)

maxrimue on 17 Sep 2015

But aside from that, I don't think that the 4.x.x release is causing @husless's issue as n latest installed v4.0.0 for me just fine

maxrimue on 17 Sep 2015

From the first error listed, it looks like a problem with curl reading the url. I am not able to reproduce those results on Ubuntu or Linux Mint.

ghost on 17 Sep 2015

@tedgaydos As it works now, it seems like the issue was related to the system rather. The last time I've seen outputs like cp: cannot stat ‘/usr/local/n/versions/node//bin’: No such file or directory, it was due to curl which couldn't connect to the servers when it was outdated (due to Heartbleed)

maxrimue on 17 Sep 2015

@tuananh Upgrade OpenSSL first of all. Thanks @maxrimue.

1__seanwang_192_____zsh_

Sean-Wang on 18 Dec 2015

👍2

i'm came cross the same problem