After reinstalling System and nodejs I get locked message #4802

Closed
jonasdk opened this Issue Feb 28, 2014 · 3 comments

Comments

Projects
None yet
4 participants
@jonasdk

jonasdk commented Feb 28, 2014

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

This comment has been minimized.

Show comment
Hide comment
@robertkowalski

robertkowalski Feb 28, 2014

Member

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

Member

robertkowalski commented Feb 28, 2014

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

@dgm

This comment has been minimized.

Show comment
Hide comment
@dgm

dgm Apr 7, 2014

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

dgm commented Apr 7, 2014

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 Sep 24, 2014

@othiym23

This comment has been minimized.

Show comment
Hide comment
@othiym23

othiym23 Sep 24, 2014

Contributor

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!

Contributor

othiym23 commented Sep 24, 2014

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 Sep 24, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment