Have you tried to freeze rails into the project?
On Apr 14, 2:26 am, hei <[email protected]> wrote:
> I did so, details below:
> original:
> gem 1.2.0
> rails 2.0.2
> one application(call it OLD) running well
> now:
> gem 1.3.1(for rails 2.3.2's needs)
> rails 2.0.2, 2.3.2(both exists)
> another application(just a test application, almost blank, call it
> NEW) meet errors:
>
> /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:149:in `activate':
> can't activate activerecord (= 2.0.2, runtime),
> already activated activerecord-2.3.2 (Gem::Exception)
>
> Notice: I can't run gem cleanup, and I don't want change any of OLD
> (including rake rails:freeze:edge RELEASE=2.0.2)
> so I just freeze New, but still get errors.
> Can anyone help me ? Thanks a lot!
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
