`npm publish` fails #4653

Closed
yyx990803 opened this Issue Feb 11, 2014 · 5 comments

Comments

Projects
None yet
7 participants
@yyx990803
Contributor

yyx990803 commented Feb 11, 2014

I have previously successfully done npm publish -f on the current version. But now npm publish -f have the following result. I have also unpublished v0.8.5, then trying a normal publish, still the same.

npm http PUT https://registry.npmjs.org/vue
npm http 409 https://registry.npmjs.org/vue
npm http GET https://registry.npmjs.org/vue
npm http 200 https://registry.npmjs.org/vue
npm http PUT https://registry.npmjs.org/vue
npm http 403 https://registry.npmjs.org/vue
npm http PUT https://registry.npmjs.org/vue
npm http 403 https://registry.npmjs.org/vue
npm ERR! Error: forbidden 0.8.5 time should not be modified 1: vue
npm ERR!     at RegClient.<anonymous> (/Users/evan/.nvm/v0.11.11/lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:275:14)
npm ERR!     at Request.self.callback (/Users/evan/.nvm/v0.11.11/lib/node_modules/npm/node_modules/request/request.js:123:22)
npm ERR!     at Request.EventEmitter.emit (events.js:107:17)
npm ERR!     at Request.<anonymous> (/Users/evan/.nvm/v0.11.11/lib/node_modules/npm/node_modules/request/request.js:893:14)
npm ERR!     at Request.EventEmitter.emit (events.js:126:20)
npm ERR!     at IncomingMessage.<anonymous> (/Users/evan/.nvm/v0.11.11/lib/node_modules/npm/node_modules/request/request.js:844:12)
npm ERR!     at IncomingMessage.EventEmitter.emit (events.js:126:20)
npm ERR!     at _stream_readable.js:896:16
npm ERR!     at process._tickCallback (node.js:664:11)
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/isaacs/npm/issues>

npm ERR! System Darwin 13.0.2
npm ERR! command "/Users/evan/.nvm/v0.11.11/bin/node" "/Users/evan/.nvm/v0.11.11/bin/npm" "publish" "-f"
npm ERR! cwd /Users/evan/Personal/vue
npm ERR! node -v v0.11.11
npm ERR! npm -v 1.3.25
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/evan/Personal/vue/npm-debug.log
npm ERR! not ok code 0
@RobertWHurst

This comment has been minimized.

Show comment Hide comment
@RobertWHurst

RobertWHurst Feb 12, 2014

I've done essentially the same actions as @yyx990803. I can confirm this bug:

npm ERR! Error: forbidden 1.5.11 time should not be modified 1: viceroy
npm ERR!     at RegClient.<anonymous> (/Users/roberthurst/.nvm/v0.10.25/lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:275:14)
npm ERR!     at Request.self.callback (/Users/roberthurst/.nvm/v0.10.25/lib/node_modules/npm/node_modules/request/request.js:123:22)
npm ERR!     at Request.EventEmitter.emit (events.js:98:17)
npm ERR!     at Request.<anonymous> (/Users/roberthurst/.nvm/v0.10.25/lib/node_modules/npm/node_modules/request/request.js:893:14)
npm ERR!     at Request.EventEmitter.emit (events.js:117:20)
npm ERR!     at IncomingMessage.<anonymous> (/Users/roberthurst/.nvm/v0.10.25/lib/node_modules/npm/node_modules/request/request.js:844:12)
npm ERR!     at IncomingMessage.EventEmitter.emit (events.js:117:20)
npm ERR!     at _stream_readable.js:920:16
npm ERR!     at process._tickCallback (node.js:415:13)
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/isaacs/npm/issues>

npm ERR! System Darwin 13.0.0
npm ERR! command "/Users/roberthurst/.nvm/v0.10.25/bin/node" "/Users/roberthurst/.nvm/v0.10.25/bin/npm" "publish" "-f"
npm ERR! cwd /Users/roberthurst/Developer/Companies/Battlefy/JavaScript/Libraries/Viceroy
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.24
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/roberthurst/Developer/Companies/Battlefy/JavaScript/Libraries/Viceroy/npm-debug.log
npm ERR! not ok code 0

I've done essentially the same actions as @yyx990803. I can confirm this bug:

npm ERR! Error: forbidden 1.5.11 time should not be modified 1: viceroy
npm ERR!     at RegClient.<anonymous> (/Users/roberthurst/.nvm/v0.10.25/lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:275:14)
npm ERR!     at Request.self.callback (/Users/roberthurst/.nvm/v0.10.25/lib/node_modules/npm/node_modules/request/request.js:123:22)
npm ERR!     at Request.EventEmitter.emit (events.js:98:17)
npm ERR!     at Request.<anonymous> (/Users/roberthurst/.nvm/v0.10.25/lib/node_modules/npm/node_modules/request/request.js:893:14)
npm ERR!     at Request.EventEmitter.emit (events.js:117:20)
npm ERR!     at IncomingMessage.<anonymous> (/Users/roberthurst/.nvm/v0.10.25/lib/node_modules/npm/node_modules/request/request.js:844:12)
npm ERR!     at IncomingMessage.EventEmitter.emit (events.js:117:20)
npm ERR!     at _stream_readable.js:920:16
npm ERR!     at process._tickCallback (node.js:415:13)
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/isaacs/npm/issues>

npm ERR! System Darwin 13.0.0
npm ERR! command "/Users/roberthurst/.nvm/v0.10.25/bin/node" "/Users/roberthurst/.nvm/v0.10.25/bin/npm" "publish" "-f"
npm ERR! cwd /Users/roberthurst/Developer/Companies/Battlefy/JavaScript/Libraries/Viceroy
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.24
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/roberthurst/Developer/Companies/Battlefy/JavaScript/Libraries/Viceroy/npm-debug.log
npm ERR! not ok code 0
@chaaz

This comment has been minimized.

Show comment Hide comment
@chaaz

chaaz Feb 12, 2014

Same here:

npm http PUT https://registry.npmjs.org/cloudelements-cmtool
npm http 409 https://registry.npmjs.org/cloudelements-cmtool
npm http GET https://registry.npmjs.org/cloudelements-cmtool
npm http 200 https://registry.npmjs.org/cloudelements-cmtool
npm http PUT https://registry.npmjs.org/cloudelements-cmtool
npm http 403 https://registry.npmjs.org/cloudelements-cmtool
npm http PUT https://registry.npmjs.org/cloudelements-cmtool
npm http 403 https://registry.npmjs.org/cloudelements-cmtool
npm ERR! Error: forbidden 0.1.1 time should not be modified 1: cloudelements-cmtool
npm ERR!     at RegClient.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:276:14)
npm ERR!     at Request.self.callback (/usr/local/lib/node_modules/npm/node_modules/request/request.js:123:22)
npm ERR!     at Request.EventEmitter.emit (events.js:98:17)
npm ERR!     at Request.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/request/request.js:893:14)
npm ERR!     at Request.EventEmitter.emit (events.js:117:20)
npm ERR!     at IncomingMessage.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/request/request.js:844:12)
npm ERR!     at IncomingMessage.EventEmitter.emit (events.js:117:20)
npm ERR!     at _stream_readable.js:920:16
npm ERR!     at process._tickCallback (node.js:415:13)
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/isaacs/npm/issues>

npm ERR! System Darwin 13.0.0
npm ERR! command "node" "/usr/local/bin/npm" "publish" "cmtool"
npm ERR! cwd /Users/ozchaz/Documents/Projects/gits
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.26
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/ozchaz/Documents/Projects/gits/npm-debug.log
npm ERR! not ok code 0

This happened after I unpublished the 0.1.1 version. As a workaround, I bumped the version number to 0.1.2 (which had never been published) and published; everything worked fine. This might be an option for anyone who can publish a new version.

chaaz commented Feb 12, 2014

Same here:

npm http PUT https://registry.npmjs.org/cloudelements-cmtool
npm http 409 https://registry.npmjs.org/cloudelements-cmtool
npm http GET https://registry.npmjs.org/cloudelements-cmtool
npm http 200 https://registry.npmjs.org/cloudelements-cmtool
npm http PUT https://registry.npmjs.org/cloudelements-cmtool
npm http 403 https://registry.npmjs.org/cloudelements-cmtool
npm http PUT https://registry.npmjs.org/cloudelements-cmtool
npm http 403 https://registry.npmjs.org/cloudelements-cmtool
npm ERR! Error: forbidden 0.1.1 time should not be modified 1: cloudelements-cmtool
npm ERR!     at RegClient.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:276:14)
npm ERR!     at Request.self.callback (/usr/local/lib/node_modules/npm/node_modules/request/request.js:123:22)
npm ERR!     at Request.EventEmitter.emit (events.js:98:17)
npm ERR!     at Request.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/request/request.js:893:14)
npm ERR!     at Request.EventEmitter.emit (events.js:117:20)
npm ERR!     at IncomingMessage.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/request/request.js:844:12)
npm ERR!     at IncomingMessage.EventEmitter.emit (events.js:117:20)
npm ERR!     at _stream_readable.js:920:16
npm ERR!     at process._tickCallback (node.js:415:13)
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/isaacs/npm/issues>

npm ERR! System Darwin 13.0.0
npm ERR! command "node" "/usr/local/bin/npm" "publish" "cmtool"
npm ERR! cwd /Users/ozchaz/Documents/Projects/gits
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.26
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/ozchaz/Documents/Projects/gits/npm-debug.log
npm ERR! not ok code 0

This happened after I unpublished the 0.1.1 version. As a workaround, I bumped the version number to 0.1.2 (which had never been published) and published; everything worked fine. This might be an option for anyone who can publish a new version.

@jprichardson

This comment has been minimized.

Show comment Hide comment
@jprichardson

jprichardson Feb 13, 2014

Yup, same bug for me too.

Yup, same bug for me too.

@MarcDiethelm

This comment has been minimized.

Show comment Hide comment
@MarcDiethelm

MarcDiethelm Feb 21, 2014

See here: npm/npmjs.org#148

@othiym23

This comment has been minimized.

Show comment Hide comment
@othiym23

othiym23 Nov 26, 2014

Contributor

Hey, all. This was due to an issue in the registry that has since been resolved. I'm closing it as such, but we do take integrity issues with the registry seriously, so file a new issue if you see something like this again. Thanks for your patience, and sorry it took us so long to get around to this!

Contributor

othiym23 commented Nov 26, 2014

Hey, all. This was due to an issue in the registry that has since been resolved. I'm closing it as such, but we do take integrity issues with the registry seriously, so file a new issue if you see something like this again. Thanks for your patience, and sorry it took us so long to get around to this!

@othiym23 othiym23 closed this Nov 26, 2014

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