Skip to content

Instantly share code, notes, and snippets.

@ryanstevens
Created December 9, 2013 19:55
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save ryanstevens/7879673 to your computer and use it in GitHub Desktop.
Save ryanstevens/7879673 to your computer and use it in GitHub Desktop.
npm WARN package.json bufferpack@0.0.6 No readme data.
npm ERR! tar.unpack untar error /home/ryan/tmp/npm-17888/1386617568447-0.15539880678988993/tmp.tgz
npm ERR! tar.unpack untar error /home/ryan/tmp/npm-17888/1386617568447-0.15539880678988993/tmp.tgz
npm ERR! Error: invalid tar file
npm ERR! at Extract.Parse._startEntry (/usr/local/lib/node_modules/npm/node_modules/tar/lib/parse.js:144:13)
npm ERR! at Extract.Parse._process (/usr/local/lib/node_modules/npm/node_modules/tar/lib/parse.js:125:12)
npm ERR! at BlockStream.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/tar/lib/parse.js:46:8)
npm ERR! at BlockStream.EventEmitter.emit (events.js:96:17)
npm ERR! at BlockStream._emitChunk (/usr/local/lib/node_modules/npm/node_modules/block-stream/block-stream.js:145:10)
npm ERR! at BlockStream.resume (/usr/local/lib/node_modules/npm/node_modules/block-stream/block-stream.js:58:15)
npm ERR! at Extract.Reader.resume (/usr/local/lib/node_modules/npm/node_modules/fstream/lib/reader.js:252:34)
npm ERR! at Entry.Parse._startEntry._entry (/usr/local/lib/node_modules/npm/node_modules/tar/lib/parse.js:256:8)
npm ERR! at Entry.EventEmitter.emit (events.js:93:17)
npm ERR! at Entry.inherits.resume (/usr/local/lib/node_modules/npm/node_modules/tar/lib/entry.js:91:10)
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-220.4.1.el6.x86_64
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! cwd /mnt/data/jenkins/jobs/bandpage-node-admin/workspace
npm ERR! node -v v0.8.26
npm ERR! npm -v 1.2.30
@sam-github
Copy link

try again. if that doesn't work, do npm view bufferpack, confirm that it looks like it should, mostly, that the versions are listed, and the attachment tarball URLs can be downloaded with curl. you could also take a look at the tmp.tgz, make sure it isn't a 404 error page instead of a tarball. if that doesn't work, wait, could be temporary, if that doesn't work... you'll have to report as bug and poke people on irc. good luck. we've run into things like this a fair bit, recently.

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