I have a Rails app that is currently running in production on Rails v1.2.2. Since I didn't have control of the server that runs the production copy of this app, I have put off upgrading to v2.x. However, I recently read about freezing Rails to your app, making it independent of the version of Rails installed on the server so I upgraded my app to v2.3.4. On my development machine everything worked great after freezing Rails to my upgraded app, (presumably because I have Rails v2.3.4 installed locally). As a test of the freezing process, I copied my frozen app to an old PC that only has Rails v2.0.2 installed and tried starting up a Mongrel server . This is unsuccessful, and causes the following error...
E:/Ruby/lib/ruby/site_ruby/1.8/rubygem.rb:246: in 'activate': can't activate actionpack (= 2.0.2), already activated actionpack-2.3.4] (Gem::Exception) If I go to the gems directory on this box and rename the actionpack-2.0.2 directory (such as adding a -) and try starting mongrel again I get a similar error message... E:/Ruby/lib/ruby/site_ruby/1.8/rubygem.rb:246: in 'activate': can't activate rails (= 2.0.2), already activated rails-2.3.4] (Gem::Exception) I checked my controllers for includes that might be causing this, but nothing seemed suspicious (only includes were for 'date', 'net/http', and 'uri') Any help with this would be greatly appreciated. Freezing seemed so straightforward, don't know why it's causing me so many problems. Thanks for any nuggets of insight / wisdom that come my way... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
