Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

After reinstalling System and nodejs I get locked message #4802

Closed
jonasdk opened this Issue · 3 comments

4 participants

@jonasdk

After doing a reinstall of my system and nodejs and a lot of other things I arrive at installing bower - but it is said to be locked.

Anybody have a key for that lock?

Here is my log

jonas$ npm install -g bower

npm ERR! Error: Attempt to unlock bower, which hasn't been locked
npm ERR!     at unlock (/usr/local/lib/node_modules/npm/lib/cache.js:1304:11)
npm ERR!     at cb (/usr/local/lib/node_modules/npm/lib/cache.js:866:5)
npm ERR!     at /usr/local/lib/node_modules/npm/lib/cache.js:883:20
npm ERR!     at /usr/local/lib/node_modules/npm/lib/cache.js:1290:7
npm ERR!     at /usr/local/lib/node_modules/npm/node_modules/lockfile/lockfile.js:167:38
npm ERR!     at OpenReq.Req.done (/usr/local/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:144:5)
npm ERR!     at OpenReq.done (/usr/local/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:64:22)
npm ERR!     at Object.oncomplete (fs.js:107:15)
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! System Darwin 13.1.0
npm ERR! command "node" "/usr/local/bin/npm" "install" "-g" "bower"
npm ERR! cwd /Users/jonas
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.3
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/jonas/npm-debug.log
npm ERR! not ok code 0
@robertkowalski
Collaborator

Uhm, is that the whole error log? Can you post the npm-debug.log in a gist?

@dgm
dgm commented

I just had similar types of errors, I think because HOME wasn't set to match the user my script was running as.

@othiym23 othiym23 added the support label
@othiym23
Owner

I believe this issue has been addressed by the resolution to #6043, which is included in the latest stable version of npm, npm@2.0.0. Please upgrade npm and this problem should go away. Thanks for your patience!

@othiym23 othiym23 closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.