From: Ryan Davis <ryand-ruby@...>
Date: 2007-01-18T02:55:43+09:00
Subject: Re: Hoe poisoned in Rubyforge


On Jan 17, 2007, at 6:44 AM, Tom Copeland wrote:

> 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)