From: Jim Weirich <jim@...>
Date: 2005-09-06T20:42:54+09:00
Subject: Re: Rake 0.6.0 Released

On Tuesday 06 September 2005 01:21 am, Joel VanderWerf wrote:
> Jim Weirich wrote:
> > On Tuesday 06 September 2005 12:00 am, Joel VanderWerf wrote:
> >>I do have libssl 0.9.7 installed, and the earlier rake installed ok.
> >>What could be causing this?
> >
> > Sounds like a gem issue.  The Rake gem is signed, but RubyGems is pretty
> > careful about continuing even when the ssl libraries are not available.
> >
> > Try running the gem command with the --backtrace option so we can get a
> > stacktrace and locate the code causing the error.

Yeah, its the fact that the gem is signed and RubyGems is insisting on having 
SSL available.  I think it should only do that if the security policy 
requires it, but that's a gems issue that needs looking into.

So, what to do? 

(1) If you thought you had SSL, and you don't, then you probably should look 
into that.

(2) If you want the latest rake no matter what, I put out an unsigned version 
of the gem on my betagem site labelled version 0.6.1.  You can get it with:

    gem install rake --source http://onestepback.org/betagems

-- 
-- Jim Weirich    jim@weirichhouse.org     http://onestepback.org
-----------------------------------------------------------------
"Beware of bugs in the above code; I have only proved it correct, 
not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas)