Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Unable to publish or unpublish a package #131

Closed
rickihastings opened this Issue · 5 comments

3 participants

Ricki Hastings Nicolas Chambrier Terin Stock
Ricki Hastings

I've pushed up the version number plenty of times, tried using --force and I can't publish my package. Noted that the package is a complete re-write and is using an updated package.json, can't see it being too of a big deal though? These are my errors;

npm WARN using --force I sure hope you know what you are doing.
npm http PUT http://registry.npmjs.org/irc-factory
npm http 409 http://registry.npmjs.org/irc-factory
npm http GET http://registry.npmjs.org/irc-factory
npm http 200 http://registry.npmjs.org/irc-factory
npm http PUT http://registry.npmjs.org/irc-factory/-/irc-factory-1.0.0.tgz/-rev/46-49a0fe4d5a14f178acda89b50e081ec3
npm http 409 http://registry.npmjs.org/irc-factory/-/irc-factory-1.0.0.tgz/-rev/46-49a0fe4d5a14f178acda89b50e081ec3
npm WARN publish Forced publish over irc-factory@1.0.0
npm http GET http://registry.npmjs.org/irc-factory
- irc-factory@1.0.0
npm http PUT http://registry.npmjs.org/irc-factory
npm http 200 http://registry.npmjs.org/irc-factory
npm http 409 http://registry.npmjs.org/irc-factory
npm http GET http://registry.npmjs.org/irc-factory
npm http 200 http://registry.npmjs.org/irc-factory
npm http PUT http://registry.npmjs.org/irc-factory/-/irc-factory-1.0.0.tgz/-rev/46-49a0fe4d5a14f178acda89b50e081ec3
npm http 409 http://registry.npmjs.org/irc-factory/-/irc-factory-1.0.0.tgz/-rev/46-49a0fe4d5a14f178acda89b50e081ec3
npm ERR! publish fail Cannot publish over existing version.
npm ERR! publish fail Update the 'version' field in package.json and try again.
npm ERR! publish fail
npm ERR! publish fail If the previous version was published in error, see:
npm ERR! publish fail     npm help unpublish
npm ERR! publish fail
npm ERR! publish fail To automatically increment version numbers, see:
npm ERR! publish fail     npm help version

npm ERR! System Linux 2.6.32-5-686
npm ERR! command "node" "/usr/local/bin/npm" "publish" "--force"
npm ERR! cwd /home/ricki/shared/irc-factory
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.15
npm ERR! code EPUBLISHCONFLICT
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /home/ricki/shared/irc-factory/npm-debug.log
npm ERR! not ok code 0

So I tried unpublishing the entire package or the previous version, and I get these errors below;

npm WARN using --force I sure hope you know what you are doing.
npm http GET http://registry.npmjs.org/irc-factory
npm http 200 http://registry.npmjs.org/irc-factory
npm http DELETE http://registry.npmjs.org/irc-factory/-rev/46-49a0fe4d5a14f178acda89b50e081ec3
npm http 409 http://registry.npmjs.org/irc-factory/-rev/46-49a0fe4d5a14f178acda89b50e081ec3
npm ERR! Error: conflict Document update conflict.: irc-factory/-rev/46-49a0fe4d5a14f178acda89b50e081ec3
npm ERR!     at RegClient.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:272:14)
npm ERR!     at Request.self.callback (/usr/lib/node_modules/npm/node_modules/request/request.js:129:22)
npm ERR!     at Request.EventEmitter.emit (events.js:98:17)
npm ERR!     at Request.<anonymous> (/usr/lib/node_modules/npm/node_modules/request/request.js:873:14)
npm ERR!     at Request.EventEmitter.emit (events.js:117:20)
npm ERR!     at IncomingMessage.<anonymous> (/usr/lib/node_modules/npm/node_modules/request/request.js:824: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 log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Linux 2.6.32-5-686
npm ERR! command "node" "/usr/local/bin/npm" "unpublish" "irc-factory" "--force"
npm ERR! cwd /home/ricki/shared/irc-factory
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.15
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /home/ricki/shared/irc-factory/npm-debug.log
npm ERR! not ok code 0
Ricki Hastings

I'm now getting this response when trying to unpublish;

npm WARN using --force I sure hope you know what you are doing.
npm http PUT http://registry.npmjs.org/irc-factory
npm http 409 http://registry.npmjs.org/irc-factory
npm http GET http://registry.npmjs.org/irc-factory
npm http 200 http://registry.npmjs.org/irc-factory
npm http PUT http://registry.npmjs.org/irc-factory/-/irc-factory-1.0.0.tgz/-rev/47-b6d6b8f7656e04fe164fa2fd6c9cca36
npm http 409 http://registry.npmjs.org/irc-factory/-/irc-factory-1.0.0.tgz/-rev/47-b6d6b8f7656e04fe164fa2fd6c9cca36
npm WARN publish Forced publish over irc-factory@1.0.0
npm http GET http://registry.npmjs.org/irc-factory
npm http DELETE http://registry.npmjs.org/irc-factory/-rev/1-1ea58b9f7271de44eef99e6b87c3e7c5
npm http 200 http://registry.npmjs.org/irc-factory
npm http 200 http://registry.npmjs.org/irc-factory/-rev/1-1ea58b9f7271de44eef99e6b87c3e7c5
- irc-factory@1.0.0
npm http PUT http://registry.npmjs.org/irc-factory
npm http 409 http://registry.npmjs.org/irc-factory
npm http GET http://registry.npmjs.org/irc-factory
npm http 404 http://registry.npmjs.org/irc-factory
npm ERR! 404 'irc-factory' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, or http url, or git url.

npm ERR! System Linux 2.6.32-5-686
npm ERR! command "node" "/usr/local/bin/npm" "publish" "--force"
npm ERR! cwd /home/ricki/shared/irc-factory
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.15
npm ERR! code E404
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /home/ricki/shared/irc-factory/npm-debug.log
npm ERR! not ok code 0

So I try to publish again;

ricki@debian:~/shared$ npm publish irc-factory --force
npm WARN using --force I sure hope you know what you are doing.
npm http PUT http://registry.npmjs.org/irc-factory
npm http 409 http://registry.npmjs.org/irc-factory
npm http GET http://registry.npmjs.org/irc-factory
npm http 404 http://registry.npmjs.org/irc-factory
npm ERR! 404 'irc-factory' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, or http url, or git url.

npm ERR! System Linux 2.6.32-5-686
npm ERR! command "node" "/usr/local/bin/npm" "publish" "irc-factory" "--force"
npm ERR! cwd /home/ricki/shared
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.15
npm ERR! code E404
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /home/ricki/shared/npm-debug.log
npm ERR! not ok code 0
Nicolas Chambrier

Same here, unable to publish a package :( I tried changing name, so we have corrupted packages in index for rc-cli, rc-bin and rccli (tried with only [a-z], just in case).

When trying to publish, I first got 409 (silent), then a 404 when npm checks for published module. Now I get a PUT 201, then GET 404:

0 info it worked if it ends with ok
1 verbose cli [ '/home/nchambrier/.nvm/v0.10.22/bin/node',
1 verbose cli   '/home/nchambrier/.nvm/v0.10.22/bin/npm',
1 verbose cli   'publish' ]
2 info using npm@1.3.14
3 info using node@v0.10.22
4 verbose publish [ '.' ]
5 verbose cache add [ '.', null ]
6 verbose cache add name=undefined spec="." args=[".",null]
7 verbose parsed url { protocol: null,
7 verbose parsed url   slashes: null,
7 verbose parsed url   auth: null,
7 verbose parsed url   host: null,
7 verbose parsed url   port: null,
7 verbose parsed url   hostname: null,
7 verbose parsed url   hash: null,
7 verbose parsed url   search: null,
7 verbose parsed url   query: null,
7 verbose parsed url   pathname: '.',
7 verbose parsed url   path: '.',
7 verbose parsed url   href: '.' }
8 silly lockFile 3a52ce78- .
9 verbose lock . /home/nchambrier/.npm/3a52ce78-.lock
10 verbose tar pack [ '/home/nchambrier/tmp/npm-31194-bfOefhhl/1386689959850-0.36759674246422946/tmp.tgz',
10 verbose tar pack   '.' ]
11 verbose tarball /home/nchambrier/tmp/npm-31194-bfOefhhl/1386689959850-0.36759674246422946/tmp.tgz
12 verbose folder .
13 info prepublish rccli@0.0.1
14 silly lockFile 1f1177db-tar tar://.
15 verbose lock tar://. /home/nchambrier/.npm/1f1177db-tar.lock
16 silly lockFile 1aefd63e-9850-0-36759674246422946-tmp-tgz tar:///home/nchambrier/tmp/npm-31194-bfOefhhl/1386689959850-0.36759674246422946/tmp.tgz
17 verbose lock tar:///home/nchambrier/tmp/npm-31194-bfOefhhl/1386689959850-0.36759674246422946/tmp.tgz /home/nchambrier/.npm/1aefd63e-9850-0-36759674246422946-tmp-tgz.lock
18 silly lockFile 1f1177db-tar tar://.
19 silly lockFile 1f1177db-tar tar://.
20 silly lockFile 1aefd63e-9850-0-36759674246422946-tmp-tgz tar:///home/nchambrier/tmp/npm-31194-bfOefhhl/1386689959850-0.36759674246422946/tmp.tgz
21 silly lockFile 1aefd63e-9850-0-36759674246422946-tmp-tgz tar:///home/nchambrier/tmp/npm-31194-bfOefhhl/1386689959850-0.36759674246422946/tmp.tgz
22 verbose tar unpack /home/nchambrier/tmp/npm-31194-bfOefhhl/1386689959850-0.36759674246422946/tmp.tgz
23 silly lockFile 65ceff72-9850-0-36759674246422946-package tar:///home/nchambrier/tmp/npm-31194-bfOefhhl/1386689959850-0.36759674246422946/package
24 verbose lock tar:///home/nchambrier/tmp/npm-31194-bfOefhhl/1386689959850-0.36759674246422946/package /home/nchambrier/.npm/65ceff72-9850-0-36759674246422946-package.lock
25 silly lockFile 1aefd63e-9850-0-36759674246422946-tmp-tgz tar:///home/nchambrier/tmp/npm-31194-bfOefhhl/1386689959850-0.36759674246422946/tmp.tgz
26 verbose lock tar:///home/nchambrier/tmp/npm-31194-bfOefhhl/1386689959850-0.36759674246422946/tmp.tgz /home/nchambrier/.npm/1aefd63e-9850-0-36759674246422946-tmp-tgz.lock
27 silly gunzTarPerm modes [ '755', '644' ]
28 silly gunzTarPerm extractEntry package.json
29 silly gunzTarPerm extractEntry index.js
30 silly gunzTarPerm extractEntry bin/rc.js
31 silly lockFile 65ceff72-9850-0-36759674246422946-package tar:///home/nchambrier/tmp/npm-31194-bfOefhhl/1386689959850-0.36759674246422946/package
32 silly lockFile 65ceff72-9850-0-36759674246422946-package tar:///home/nchambrier/tmp/npm-31194-bfOefhhl/1386689959850-0.36759674246422946/package
33 silly lockFile 1aefd63e-9850-0-36759674246422946-tmp-tgz tar:///home/nchambrier/tmp/npm-31194-bfOefhhl/1386689959850-0.36759674246422946/tmp.tgz
34 silly lockFile 1aefd63e-9850-0-36759674246422946-tmp-tgz tar:///home/nchambrier/tmp/npm-31194-bfOefhhl/1386689959850-0.36759674246422946/tmp.tgz
35 verbose tar pack [ '/home/nchambrier/.npm/rccli/0.0.1/package.tgz',
35 verbose tar pack   '/home/nchambrier/tmp/npm-31194-bfOefhhl/1386689959850-0.36759674246422946/package' ]
36 verbose tarball /home/nchambrier/.npm/rccli/0.0.1/package.tgz
37 verbose folder /home/nchambrier/tmp/npm-31194-bfOefhhl/1386689959850-0.36759674246422946/package
38 silly lockFile 65ceff72-9850-0-36759674246422946-package tar:///home/nchambrier/tmp/npm-31194-bfOefhhl/1386689959850-0.36759674246422946/package
39 verbose lock tar:///home/nchambrier/tmp/npm-31194-bfOefhhl/1386689959850-0.36759674246422946/package /home/nchambrier/.npm/65ceff72-9850-0-36759674246422946-package.lock
40 silly lockFile 68d6c41d-rier-npm-rccli-0-0-1-package-tgz tar:///home/nchambrier/.npm/rccli/0.0.1/package.tgz
41 verbose lock tar:///home/nchambrier/.npm/rccli/0.0.1/package.tgz /home/nchambrier/.npm/68d6c41d-rier-npm-rccli-0-0-1-package-tgz.lock
42 silly lockFile 65ceff72-9850-0-36759674246422946-package tar:///home/nchambrier/tmp/npm-31194-bfOefhhl/1386689959850-0.36759674246422946/package
43 silly lockFile 65ceff72-9850-0-36759674246422946-package tar:///home/nchambrier/tmp/npm-31194-bfOefhhl/1386689959850-0.36759674246422946/package
44 silly lockFile 68d6c41d-rier-npm-rccli-0-0-1-package-tgz tar:///home/nchambrier/.npm/rccli/0.0.1/package.tgz
45 silly lockFile 68d6c41d-rier-npm-rccli-0-0-1-package-tgz tar:///home/nchambrier/.npm/rccli/0.0.1/package.tgz
46 silly lockFile 159b3566-hambrier-npm-rccli-0-0-1-package /home/nchambrier/.npm/rccli/0.0.1/package
47 verbose lock /home/nchambrier/.npm/rccli/0.0.1/package /home/nchambrier/.npm/159b3566-hambrier-npm-rccli-0-0-1-package.lock
48 silly lockFile 159b3566-hambrier-npm-rccli-0-0-1-package /home/nchambrier/.npm/rccli/0.0.1/package
49 silly lockFile 159b3566-hambrier-npm-rccli-0-0-1-package /home/nchambrier/.npm/rccli/0.0.1/package
50 verbose tar unpack /home/nchambrier/.npm/rccli/0.0.1/package.tgz
51 silly lockFile c6d92693-hambrier-npm-rccli-0-0-1-package tar:///home/nchambrier/.npm/rccli/0.0.1/package
52 verbose lock tar:///home/nchambrier/.npm/rccli/0.0.1/package /home/nchambrier/.npm/c6d92693-hambrier-npm-rccli-0-0-1-package.lock
53 silly lockFile 68d6c41d-rier-npm-rccli-0-0-1-package-tgz tar:///home/nchambrier/.npm/rccli/0.0.1/package.tgz
54 verbose lock tar:///home/nchambrier/.npm/rccli/0.0.1/package.tgz /home/nchambrier/.npm/68d6c41d-rier-npm-rccli-0-0-1-package-tgz.lock
55 silly gunzTarPerm modes [ '755', '644' ]
56 silly gunzTarPerm extractEntry package.json
57 silly gunzTarPerm extractEntry index.js
58 silly gunzTarPerm extractEntry bin/rc.js
59 silly lockFile c6d92693-hambrier-npm-rccli-0-0-1-package tar:///home/nchambrier/.npm/rccli/0.0.1/package
60 silly lockFile c6d92693-hambrier-npm-rccli-0-0-1-package tar:///home/nchambrier/.npm/rccli/0.0.1/package
61 silly lockFile 68d6c41d-rier-npm-rccli-0-0-1-package-tgz tar:///home/nchambrier/.npm/rccli/0.0.1/package.tgz
62 silly lockFile 68d6c41d-rier-npm-rccli-0-0-1-package-tgz tar:///home/nchambrier/.npm/rccli/0.0.1/package.tgz
63 verbose chmod /home/nchambrier/.npm/rccli/0.0.1/package.tgz 644
64 verbose chown /home/nchambrier/.npm/rccli/0.0.1/package.tgz [ 1000, 1000 ]
65 silly lockFile 3a52ce78- .
66 silly lockFile 3a52ce78- .
67 silly publish { name: 'rccli',
67 silly publish   version: '0.0.1',
67 silly publish   description: 'Display configuration from merged rc-files (example: \'rc npm\').',
67 silly publish   main: 'index.js',
67 silly publish   scripts: { test: 'echo "Error: no test specified" && exit 1' },
67 silly publish   bin: { rc: './bin/rc.js' },
67 silly publish   preferGlobal: true,
67 silly publish   author:
67 silly publish    { name: 'Nicolas Chambrier',
67 silly publish      email: 'naholyr@gmail.com',
67 silly publish      url: 'http://naholyr.fr/' },
67 silly publish   license: 'BSD-2-Clause',
67 silly publish   dependencies: { rc: '~0.3.2' },
67 silly publish   readme: 'ERROR: No README data found!',
67 silly publish   _id: 'rccli@0.0.1',
67 silly publish   dist: { shasum: 'c0132dfd55fc66d59d55ba775341413516825c1e' },
67 silly publish   _from: '.' }
68 verbose url raw rccli
69 verbose url resolving [ 'https://registry.npmjs.org/', './rccli' ]
70 verbose url resolved https://registry.npmjs.org/rccli
71 info trying registry request attempt 1 at 16:39:19
72 http PUT https://registry.npmjs.org/rccli
73 http 201 https://registry.npmjs.org/rccli
74 verbose url raw rccli
75 verbose url resolving [ 'https://registry.npmjs.org/', './rccli' ]
76 verbose url resolved https://registry.npmjs.org/rccli
77 info trying registry request attempt 1 at 16:39:21
78 http GET https://registry.npmjs.org/rccli
79 http 404 https://registry.npmjs.org/rccli
80 error 404 'rccli' is not in the npm registry.
80 error 404 You should bug the author to publish it
80 error 404
80 error 404 Note that you can also install from a
80 error 404 tarball, folder, or http url, or git url.
81 error System Linux 3.11.0-15-generic
82 error command "/home/nchambrier/.nvm/v0.10.22/bin/node" "/home/nchambrier/.nvm/v0.10.22/bin/npm" "publish"
83 error cwd /home/nchambrier/Bureau/rc-cli
84 error node -v v0.10.22
85 error npm -v 1.3.14
86 error code E404
87 verbose exit [ 1, true ]

npm unpublish rccli responds with 404

npm show rccli responds with 200, empty response

And https://npmjs.org/package/rccli shows an invalid package.

Same for rc-cli and rc-bin I'll now stop polluting npm registry until fixed :)

Ricki Hastings

Mine was basically doing the same, I left it overnight came back and tried to publish again this afternoon and it worked. Not sure why.

Nicolas Chambrier

Worked today, voodoo-driven-publishing :)

Terin Stock
Collaborator

Since this is 3 months old, looks to be resolved, and deals with registry.npmjs.org rather than this project, I'm closing.

Terin Stock terinjokes 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.