[Rubygems-developers] Gem indexing problem on RubyForge

Eric Hodel drbrain at segment7.net
Mon Jan 15 15:58:38 EST 2007


On Jan 14, 2007, at 18:40, Tom Copeland wrote:
> You've probably all seen the ruby-talk traffic about the
> RubyForge problem that cropped up this weekend.  Someone released a  
> gem
> with a spec.full_name (hoe-1.1.7) that didn't match the filename
> (devotion-0.1.gem) and got itself placed in the gem index in the place
> of hoe.  Sadness ensued.
>
> I figure the easiest way to fix this - at least temporarily, so we can
> restart the RubyForge gem deployment cronjob - is to disallow  
> deploying
> any gem where full_name != file name:
>
> ----------------
> file_name = "/var/www/gems/gems/foo-4.2.gem"
> spec = Gem::Format.from_file_by_path(file_name).spec
> deploy if file_name =~ /\/#{spec.full_name}.gem$/
> ----------------

Could the regex be relaxed to /\/#{spec.full_name}.*\.gem$/ ?

(As part of the platform fix, I'm imagining making a non-ruby gems'  
full name include their platform, something like "myproj-1.0- 
mswin32.gem")

> This is going to affect about 40 gems.  I've attached the test program
> and the list to the bottom of this email.  Looks like it's mostly
> operating-system-specific gems.

I count 28 apparently non-platform gems.  Is it easy to tell how  
active these projects are?  Can the authors be persuaded to  
rerelease?  Can the gems be renamed without harm?

> BAD: /var/www/gems/gems/payment-1.0.0.gem
> BAD: /var/www/gems/gems/rdf-redland-ruby-0.5.gem
> BAD: /var/www/gems/gems/crypt-isaac_0.9.1.gem
> BAD: /var/www/gems/gems/rubilicious-0.1.4.gem
> BAD: /var/www/gems/gems/marc-0.1.gem
> BAD: /var/www/gems/gems/imlib2-ruby-0.5.1.gem
> BAD: /var/www/gems/gems/re-0.9.gem
> BAD: /var/www/gems/gems/fam-ruby-0.1.4.gem
> BAD: /var/www/gems/gems/rubidium-0.2.0.gem
> BAD: /var/www/gems/gems/ruby_ex-0.4_alpha1.gem
> BAD: /var/www/gems/gems/rubilicious-0.2.0.gem
> BAD: /var/www/gems/gems/freshmeat-ruby-0.1.0.gem
> BAD: /var/www/gems/gems/fam-ruby-0.2.0.gem
> BAD: /var/www/gems/gems/mb-ruby-0.2.1.gem
> BAD: /var/www/gems/gems/ajax_scaffold-2.2.1.gem
> BAD: /var/www/gems/gems/joystick-ruby-0.1.0.gem
> BAD: /var/www/gems/gems/xmms-ruby-0.1.2.gem
> BAD: /var/www/gems/gems/uttk-0.3_alpha1.gem
> BAD: /var/www/gems/gems/rubilicious-0.1.5.gem
> BAD: /var/www/gems/gems/iterator-0.5fix.gem
> BAD: /var/www/gems/gems/pippin-0.1b.gem
> BAD: /var/www/gems/gems/activesalesforce-0.0.1.gem
> BAD: /var/www/gems/gems/mb-ruby-0.3.0.gem
> BAD: /var/www/gems/gems/imlib2-ruby-0.4.3.gem
> BAD: /var/www/gems/gems/mb-ruby-0.1.0.gem
> BAD: /var/www/gems/gems/syndic8-ruby-0.2.0.gem
> BAD: /var/www/gems/gems/evdbapi-current.gem
> BAD: /var/www/gems/gems/evdb-current.gem

-- 
Eric Hodel - drbrain at segment7.net - http://blog.segment7.net

YOU LIT MY GEM ON FIRE!



More information about the Rubygems-developers mailing list