Jim Weirich wrote:
> 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.

That's it. My openssl.so was not installed correctly. It built ok in
ext/openssl, but I had to disable the RUBYOPT=rubygems for it to install
(and then gem update was able to install rake-0.6.0). With
RUBYOPT=rubygems, I was getting this:

$ make install
/usr/local/lib/ruby/site_ruby/1.8/rubygems/security.rb:18: uninitialized
constant OpenSSL::Digest::SHA1 (NameError)
        from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:397:in `require'
        from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:397
        from /usr/local/lib/ruby/site_ruby/1.8/ubygems.rb:4:in `require'
        from /usr/local/lib/ruby/site_ruby/1.8/ubygems.rb:4
make: *** [/usr/local/lib/ruby/site_ruby/1.8/i686-linux/openssl.so] Error 1

-- 
      vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407