Updating issue && can't uninstall iojs-v2.0

[reggi]

Couple of issues let me run through them, I had nvm installed already and I just tried to update it I ran the install script again and opened up the terminal.

This is one terminal instance:

npm info it worked if it ends with ok
npm info using npm@2.14.3
npm info using node@v4.1.0
npm info ok 

Every time I open a new terminal window I get this bit above.
Here I reinstall again for kicks, to see if it'll self-correct.

thomas@workstation:~$ curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.29.0/install.sh | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  7731  100  7731    0     0  22508      0 --:--:-- --:--:-- --:--:-- 22539
=> nvm is already installed in /Users/thomas/.nvm, trying to update using git
=> 
=> Source string already in /Users/thomas/.bashrc
npm info it worked if it ends with ok
npm info using npm@2.14.3
npm info using node@v4.1.0
npm info ok 

Note the same bit of npm output that the console opens with???
This bit below is a bit confusing because I already have it installed so this is completely irrelevant?

=> You currently have modules installed globally with `npm`. These will no
=> longer be linked to the active version of Node when you install a new node
=> with `nvm`; and they may (depending on how you construct your `$PATH`)
=> override the binaries of modules installed with `nvm`:

/Users/thomas/.nvm/versions/node/v4.1.0/lib
├── babel@5.8.23
├── babel-eslint@4.1.3
├── evalmd@0.0.16
├── gulp@3.9.0
├── jotter@0.0.3
├── mocha@2.3.3
├── parallelshell@2.0.0
├── release-it@2.3.1
├── standard@5.3.1
└── structor@0.1.1

=> If you wish to uninstall them at a later point (or re-install them under your
=> `nvm` Nodes), you can remove them from the system Node as follows:

     $ nvm use system
     $ npm uninstall -g a_module

=> Close and reopen your terminal to start using nvm

The whole reason I wanted to update was to see if I could get rid of iojs-v2.0.0 because I just cleared out a whole bunch of old versions and I couldn't uninstall iojs-v2.0.0.

thomas@workstation:~$ nvm ls
    iojs-v2.0.0
->       v4.1.0
         system
default -> v4.1.0
node -> stable (-> v4.1.0) (default)
stable -> 4.1 (-> v4.1.0) (default)
iojs -> iojs-v2.0 (-> iojs-v2.0.0) (default)
thomas@workstation:~$ nvm uninstall iojs-v2.0.0
Uninstalled io.js v2.0.0
thomas@workstation:~$ nvm ls

Didn't work it's still there.

    iojs-v2.0.0
->       v4.1.0
         system
default -> v4.1.0
node -> stable (-> v4.1.0) (default)
stable -> 4.1 (-> v4.1.0) (default)
iojs -> iojs-v2.0 (-> iojs-v2.0.0) (default)

[reggi]

hmm I just renamed ~/.nvm considering starting from scratch, I think it'll clear everything up.

[ljharb]

It's likely permissions issues - you may have used sudo at some point. With nvm, you never need sudo, nor should use it. Certainly starting with a fresh NVM_DIR should fix it.

As for the npm info, what's in ~/.npmrc? (Please do NOT post your auth token, just the settings)

[reggi]

Here's the content of ~/.npmrc without the tokens.

_auth={private}
loglevel=info
registry=http://registry.npmjs.org/
email={private}
color=always

[_token]
AuthSession={private}
version=1
expires=1388415695997
path=/
httponly=true

[reggi]

Just to clarify it's all good now, I reset everything :)

[ljharb]

I think loglevel is the reason that extra info was printed out. I'll see if I can fix that, and I'll leave this open in the meantime.

The rest, I'd bet, were permissions issues. Thanks for confirming!

[ljharb]

Fixed in the next release.