> > There's a fix in place for this now and gems are being deployed as 
> > usual.  There were several gems whose spec.full_name settings
> > prevented
> > them from being deployed; I'll contact those folks offline.
> 
> Tom, given that rake's gem tasks are almost always creating the file  
> in question, any idea how or why the file name differs from the  
> specification? In the case of the poisoning it was obviously renamed  
> before pushed up to rubyforge... but the 20 others? (I'd hate to  
> think they were all hand packaged--ugh)

Here's an example: "fxruby-1.6.2-ruby1.8.5-mswin32.gem".  Most of the
others are along the same lines... platform-specific renamings and that
kind of thing.

Yours,

tom