Initializing Adhearsion with multiple ActiveSupport versions causes an explosion
Reported by Jay Phillips | November 9th, 2007 @ 02:24 PM
I'm getting this problem when initializing Adhearsion on trunk revision 584:
~/Desktop/0.8.0 $ rake
(in /Users/jicksta/Desktop/0.8.0)
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems.rb:249:in `activate': can't activate activesupport (= 1.4.2), already activated activesupport-1.4.4] (Gem::Exception)
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems.rb:267:in `activate'
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems.rb:266:in `each'
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems.rb:266:in `activate'
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require'
from /Library/Ruby/Gems/1.8/gems/activesupport-1.4.4/lib/active_support/dependencies.rb:495:in `require'
from /Library/Ruby/Gems/1.8/gems/activesupport-1.4.4/lib/active_support/dependencies.rb:342:in `new_constants_in'
from /Library/Ruby/Gems/1.8/gems/activesupport-1.4.4/lib/active_support/dependencies.rb:495:in `require'
from ./spec/initializer/test_loading.rb:4
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require'
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `require'
from /Library/Ruby/Gems/1.8/gems/activesupport-1.4.4/lib/active_support/dependencies.rb:495:in `require'
from /Library/Ruby/Gems/1.8/gems/activesupport-1.4.4/lib/active_support/dependencies.rb:342:in `new_constants_in'
from /Library/Ruby/Gems/1.8/gems/activesupport-1.4.4/lib/active_support/dependencies.rb:495:in `require'
from -e:1
rake aborted!
Command failed with status (1): [/System/Library/Frameworks/Ruby.framework/...]
(See full trace by running task with --trace)
~/Desktop/0.8.0 $
Comments and changes to this ticket
-
Jay Phillips November 9th, 2007 @ 02:40 PM
- State changed from “new” to “resolved”
Fixed this issue. It was caused by my gems being only partially up to date.
When I updated Rubigen, it updated ActiveSupport on its own, but when another file required ActiveRecord, it was trying to pull in an older version of it. Hence the error above of ActiveSupport being required twice.
If anyone else has this issue, you now know the cause. :)
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Jay Phillips