usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:246:in `activate': can't activate activesupport (= 1.4.2), already activated activesupport-1.4.0] (Gem::Exception)
from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
from /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.15.1/lib/active_re cord.rb:30
from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require'
from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require'
from /usr/local/lib/ruby/gems/1.8/gems/rails-1.2.1/lib/initializer.rb:16 2:in `require_frameworks'
from /usr/local/lib/ruby/gems/1.8/gems/rails-1.2.1/lib/initializer.rb:16 2:in `each'
from /usr/local/lib/ruby/gems/1.8/gems/rails-1.2.1/lib/initializer.rb:16 2:in `require_frameworks'
from /usr/local/lib/ruby/gems/1.8/gems/rails-1.2.1/lib/initializer.rb:83 :in `process'
from /usr/local/lib/ruby/gems/1.8/gems/rails-1.2.1/lib/initializer.rb:43 :in `send'
from /usr/local/lib/ruby/gems/1.8/gems/rails-1.2.1/lib/initializer.rb:43 :in `run'
from ./../config/environment.rb:13
from ./dispatch.fcgi:21:in `require'
from ./dispatch.fcgi:21
so my assumption was that something on the server changed to cause this. I commented out the line
RAILS_GEM_VERSION = '1.2.1'
in my environment config and the site sprang back to life. Is it safe for me to leave this line commented out?
