[Rubygems-developers] Warning: Don't upload gems made with the beta yet

Tom Copeland tom at infoether.com
Sat Oct 27 00:07:32 EDT 2007


On Sat, 2007-10-27 at 00:01 -0400, Tom Copeland wrote:
> On Fri, 2007-10-26 at 21:56 -0600, Daniel Berger wrote:
> > All,
> > 
> > I uploaded a gem (for win32-api) using the current beta.
> > 
> > Do NOT do that!!!
> > 
> > Now people are seeing this error:
> > 
> > $ gem list --remote rails
> > *** REMOTE GEMS ***
> > Bulk updating Gem source index for: http://gems.rubyforge.org
> > ERROR:  While executing gem ... (TypeError) can't instantiate 
> > uninitialized class
> > 
> > I've deleted the gems and Tom is recreating the index as I write this.
> > 
> > Just shoot me.
> 
> Actually, maybe it's my fault - Eric, I'm using the indexer from a
> RubyGems trunk checkout from a few weeks ago; if I do an "svn up" will
> that help?
> 

In the meantime, I've disabled gem index rebuilds on RubyForge, so no
new gems will be deployed there until we sort this out.  That way at
least the current index will stay up...

Yours,

tom




More information about the Rubygems-developers mailing list