Closed
Description
Sorry, I'm sure this is a duplicate, but I can't find anything in the miriad of issues. I'm running on Ubuntu 14.04, nvm version 0.23.3, and I just recently installed nvm. I used to be on n
but I switched here in order to try out iojs, so it's possible that some residual n
is conflicting with nvm. I removed all the node versions with n
except 0.12.0, uninstalled n
, installed nvm
, and I properly sourced nvm as mentioned in issue #394. Then I ran into the following issue:
$ nvm current
v0.12.0
$ nvm install 0.10
######################################################################## 100.0%
Now using node v0.10.36
$ nvm current # NOTE: didn't change
v0.12.0
$ node -v
v0.12.0
$ nvm use 0.10
Now using node v0.10.36
$ nvm current
v0.12.0
$ node -v
v0.12.0
$ nvm install iojs
######################################################################## 100.0%
WARNING: checksums are currently disabled for io.js
Now using io.js v1.2.0
$ nvm current
iojs-v1.2.0
$ node -v # NOTE: didn't change AND different from nvm current
v0.12.0
This all works just fine when run in sudo su
, but when I exit that shell, it doesn't permeate.
More possible clues:
$ nvm run 0.10 -v
Running node v0.10.36
v0.12.0
$ nvm exec 0.10 node -v
Running node v0.10.36
v0.10.36
$ nvm run iojs -v
Running io.js v1.2.0
v1.2.0
Not sure how to proceed.
Metadata
Metadata
Assignees
Labels
No labels