gistfile1.txt

% gem install logstash
ERROR:  Error installing logstash:
        invalid gem format for /home/jls/.rvm/gems/ruby-1.9.3-p0/cache/logstash-1.1.0.gem

% rm /home/jls/.rvm/gems/ruby-1.9.3-p0/cache/logstash-1.1.0.gem
% gem install logstash
Fetching: logstash-1.1.0.gem (100%)
ERROR:  Error installing logstash:
        invalid gem format for /home/jls/.rvm/gems/ruby-1.9.3-p0/cache/logstash-1.1.0.gem

I'll indulge your desire to debug this right now, but I do think I'm done with rubygems. This past year has been a constant source of problems with rubygems that I don't have the energy or patience to suffer.

Anyway, I'll upload the original gem somewhere, too.

Pretty sure this is the original:

carrera(~/projects/logstash) % md5sum logstash-1.1.0.gem
d6ffa39f6cb366039c1d906bb13e8061  logstash-1.1.0.gem

carrera(~/projects/logstash) % gem unpack ./logstash-1.1.0.gem
ERROR:  While executing gem ... (Gem::Package::FormatError)
    corrupt gem (Gem::Package::TarInvalidError: tar is corrupt, name contains null byte) in ./logstash-1.1.0.gem

Quite curious if this is a JRuby bug. At least I this verifies that rubygems.org/CloudFront didn't mangle the gem.

Unpacking the data.tar.gz:

% tar -ztf data.tar.gz
lib/logstash/util/buftok.rb
lib/logstash/certs/cacert.pem
tar: Skipping to next header
tar: Exiting with failure status due to previous errors

Rebuilding it with 'gem build blah.gemspec' produces a working gem.

I don't remember what ruby was used to build the gem, for what it's worth.

rather, above, rebuilding I tried with ruby 1.9.3-p0

mass yank of logstash complete: https://gist.github.com/1720739

This seems like an overreaction that will do nothing but disservice your users, especially with 17,000+ downloads. Not saying it's not your choice to pull the gem, but it just feels to me like there's some other problem at work here.

I wish I could help more, sorry dude.

I literally don't have the energy to deal with rubygems problems anymore. I greatly respect and appreciate the folks involved and the problems being solved, but I can't deal with the frequent problems anymore.

I appreciate your efforts in debugging this, but I don't think there's anything left for me to do here. Using rubygems is a disservice to logstash users with the rubygems problems. New users will equate 'gem install' problems to poor release quality, and that hurts logstash.

Honestly, I should've introduced myself to the rubygems ticket system and community before I got burned out dealing with rubygems problems.

Thanks for your efforts.