$ skynet console
/usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:319:in `activate': can't activate activesupport (= 2.0.2), already activated
activesupport-2.1.0] (Gem::Exception)
        from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:337:in `activate'
        from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:336:in `each'
        from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:336:in `activate'
        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/skynet-0.9.3/bin/../lib/skynet.rb:29
        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/skynet-0.9.3/bin/skynet:28
        from /usr/local/bin/skynet:19:in `load'
        from /usr/local/bin/skynet:19

Date: 2009-04-15 17:10
Sender: Peter Gengler

Hi,

I'm having a similar issue; in my case I'm running a rails 2.2.2
and rails 2.3.2 app on the same machine, so both sets of gems
are installed at the same time.  Each rails app respects the
version I set for them, but it seems like Skynet is loading the
2.3.2 ActiveSupport gem before it loads environment.rb, which
is trying to get at the 2.2.2 gem and giving the "already
activated ..." error message.  Any pointers on how to get
skynet to use only the rails version specified in the actual app?

Thanks.

Date: 2008-06-14 01:12
Sender: slitz ferrari

i just found the problem!

when i installed the skynet gem, rubygems updated my activesupport
to 2.1.0 version while activerecord gem stayed in 2.0.2 just
needed to update activerecord gem to 2.1.0

(gem update will do the trick)

Date: 2008-06-14 01:06
Sender: slitz ferrari

same problem here.

i have the following activerecord and activesupport versions

activesupport (2.1.0, 2.0.2)
activerecord (2.0.2)

do you need some more info on my setup?

Date: 2008-06-07 23:42
Sender: Bryan Helmkamp

I ran into the same problem. I think it's because we use Rails
frozen in vendor/rails, and skynet is trying to load the real
gem rails versions when it starts.

Date: 2008-06-02 19:44
Sender: Ruslan Roo

i type "gem uninstall activesupport"
and choose version 2.0.2
then work's fine

Date: 2008-06-02 19:25
Sender: Adam Pisoni

That's interesting.   It's in fact trying to require ActiveRecord,
which must be attempting to require ActiveSupport.

Can you tell me more about your setup?