I just installed Leopard and I receive this error after running
script/server. Does anyone have any ideas on how to resolve this issue?
I have been looking all over for about 6 hours and I’m not sure where to
turn:
** Starting Rails with development environment…
Exiting
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems.rb:249:in
activate': can't activate rails (= 1.2.3), already activated rails-1.2.2] (Gem::Exception) from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:inrequire’
from
/Library/Ruby/Gems/1.8/gems/activesupport-1.4.1/lib/active_support/dependencies.rb:495:in
require' from /Library/Ruby/Gems/1.8/gems/activesupport-1.4.1/lib/active_support/dependencies.rb:342:innew_constants_in’
from
/Library/Ruby/Gems/1.8/gems/activesupport-1.4.1/lib/active_support/dependencies.rb:495:in
require' from /Library/Ruby/Gems/1.8/gems/rails-1.2.2/lib/commands/server.rb:39 from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:27:ingem_original_require’
from
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in
`require’
from script/server:3
joemar:trunk joeymarchy$ ruby -v
ruby 1.8.6 (2007-06-07 patchlevel 36) [universal-darwin9.0]
On Nov 14, 2007 9:58 PM, Joey M. [email protected]
wrote:
I just installed Leopard and I receive this error after running
script/server. Does anyone have any ideas on how to resolve this issue?
I have been looking all over for about 6 hours and I’m not sure where to
turn:
After I installed Leopard, I immediately updated to Rails 1.2.4 (one of
my
project is still specifically targeting that version). I haven’t had any
problems running script/server for it. All of my other projects are on
edge
Rails, and none of them exhibit any problems with script/server either.
I’m know that I’m not directly addressing your problem with 1.2.3, but
could
you just update to 1.2.4 or 1.2.5?
Craig
Craig,
I don’t want to upgrade Rails. I am worried about the application
breaking in a newer version of Rails.
On Nov 15, 2007 10:20 AM, Joey M. [email protected]
wrote:
Craig,
I don’t want to upgrade Rails. I am worried about the application
breaking in a newer version of Rails.
Understood. However, there aren’t very many changes from 1.2.3 to 1.2.4
to
1.2.5. The changes are minor bug fixes and some deprecation warnings in
preparation for 2.0.
It sounds like your app might be tied to the Rails version installed via
RubyGems. If so, it’s easy to try your app with a new version of Rails
and
use the older version if the newer one doesn’t work well. In
config/environment.rb of your project, you should be able to tweak the
RAILS_GEM_VERSION. Here’s an example from one of my projects:
Specifies gem version of Rails to use when vendor/rails is not present
RAILS_GEM_VERSION = ‘1.2.5’ unless defined? RAILS_GEM_VERSION
You could install 1.2.4 via RubyGems
$ sudo gem install -y rails -v 1.2.4
Then you could set RAILS_GEM_VERSION in your app to 1.2.4. If that
doesn’t
work well, you could change it back to 1.2.3.
Could that work for you?
Regards,
Craig
On Nov 15, 2007 12:26 PM, Joey M. [email protected]
wrote:
I’ll give it a try. I was concerned that it was a ruby issue (due to the
error message) having to do with the new installation of Ruby on
Leopard. Thanks! If you think it might be a Rails compatibility issue
that is a little comforting. Thanks!
It could very well be an issue with your install of Ruby/RubyGems/Rails
1.2.3 on Leopard. Given that and the very minor differences from 1.2.3
to
1.2.4 to 1.2.5, I thought it made sense to try installing multiple
versions
of Rails via RubyGems and binding your app to each one to see if the
behavior changed. Please let us know how it went.
Regards,
Craig
I’ll give it a try. I was concerned that it was a ruby issue (due to the
error message) having to do with the new installation of Ruby on
Leopard. Thanks! If you think it might be a Rails compatibility issue
that is a little comforting. Thanks!