Well it appears there is one more gem I needed to reinstall: 'rake.' Now it works.
Of course, now I have another issue... Ugh. On Feb 18, 2:20 pm, Todd <[email protected]> wrote: > Hi Luis, > > I did remove and reinstall each gem. It worked fine and only took a > few minutes. > > Now I have a new issue I hope someone can help me out with. I am > tried to upgrade from source (which I think may have been a mistake, > but it's what I'm used to). > > I can get the server to start but when I run 'rake' I get the > following. > > rake aborted! > Cipher is not a class > /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/ > 1.8/openssl/cipher.rb:22 > /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in > `gem_original_require' > /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `require' > *snip* > > I am guessing that, like my gems, the openssl lib is not compatible > with 1.8.7. Furthermore, Ruby is still looking in /System/Library/ > Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8 for libraries. > > Is this an issue? Is there an easy way to fix this openssl issue or > do more problems await me down the road? More generally, can I do a > clean, new install with the libs in, say, /usr/lib/ruby that way I > know that everything is up-to-date and compatible? > > Thanks, > Todd > > On Feb 18, 7:41 am, Luis Mcdoguall <[email protected]> > wrote: > > > Todd Siegel wrote: > > > Luis, > > > > Did you ever figure this out? I am in the same boat. > > > > Todd > > > > On Feb 9, 1:38 am, Frederick Cheung <[email protected]> > > > Todd, > > > I did try to research by looking into the forums but no one came with a > > better > > answer than Freds one. > > Since I was not in the mood to is one by one and I have other equipment > > I can use in the meanwhile, I resorted to a drastic solution. > > > Todd, this is probably not what you want to hear but is what I did: > > > 1. Clone my internal disk to an external > > 2. Re install (wipe clean first) Leopard > > 3. Got all Leopard updates installed > > 4. Used supper duper to create a "virgin backup" using sandbox. > > 5. Migrate the user from the clone . > > Now I can start playing with the installation and if something goes > > wrong I can restore that sandbox > > and go back to safe point. > > > The other options is to keep an eye on this post, I am starting to make > > the Ruby and Rails upgrade today to see if I can come up with a better > > technical solution. > > I will post my finding. > > > Good luck > > -Luis > > > -- > > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
