Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

can't activate activesupport #1

Closed
kuroda opened this issue Apr 26, 2009 · 7 comments
Closed

can't activate activesupport #1

kuroda opened this issue Apr 26, 2009 · 7 comments
Labels

Comments

@kuroda
Copy link
Contributor

kuroda commented Apr 26, 2009

When I run the annotate script against my application based on Rails 2.2.2, it halted with following error message:
/usr/lib/ruby/site_ruby/1.8/rubygems.rb:149:in `activate': can't activate activesupport (= 2.2.2, runtime), already activated activesupport-2.3.2 (Gem::Exception)

I have installed both Rails 2.2.2 and Rails 2.3.2.

@ctran
Copy link
Owner

ctran commented Apr 27, 2009

Does your app start normally?

@kuroda
Copy link
Contributor Author

kuroda commented Apr 28, 2009

Yes, I think so.

Here is full backtrace:

/usr/local/lib/site_ruby/1.8/rubygems.rb:149:in `activate': can't activate activesupport (= 2.2.2, runtime), already activated activesupport-2.3.2 (Gem::Exception)
from /usr/local/lib/site_ruby/1.8/rubygems.rb:165:in `activate'
from /usr/local/lib/site_ruby/1.8/rubygems.rb:164:in `each'
from /usr/local/lib/site_ruby/1.8/rubygems.rb:164:in `activate'
from /usr/local/lib/site_ruby/1.8/rubygems.rb:49:in `gem'
from ./config/boot.rb:59:in `load_rails_gem'
from ./config/boot.rb:53:in `load_initializer'
from ./config/boot.rb:38:in `run'
from ./config/boot.rb:11:in `boot!'
from ./config/boot.rb:109
from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
from ./Rakefile:4
from /usr/lib/ruby/gems/1.8/gems/ctran-annotate-2.0.0/lib/annotate.rb:9:in `load'
from /usr/lib/ruby/gems/1.8/gems/ctran-annotate-2.0.0/lib/annotate.rb:9
from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
from /usr/lib/ruby/gems/1.8/gems/ctran-annotate-2.0.0/bin/annotate:4
from /usr/bin/annotate:19:in `load'
from /usr/bin/annotate:19

Thanks for your reply.

@kuroda
Copy link
Contributor Author

kuroda commented Apr 28, 2009

I confirmed that my app starts normally on another machine.

I have installed two versions of Rails:

$ gem list rails
*** LOCAL GEMS ***

rails (2.3.2, 2.2.2)

My app started normally:
$ ./script/server
=> Booting Mongrel (use 'script/server webrick' to force WEBrick)
=> Rails 2.2.2 application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
** Starting Mongrel listening at 0.0.0.0:3000
** Starting Rails with development environment...
** Rails loaded.
** Loading any Rails specific GemPlugins
** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart).
** Rails signals registered. HUP => reload (without restart). It might not work well.
** Mongrel 1.1.5 available at 0.0.0.0:3000
** Use CTRL-C to stop.

@ctran
Copy link
Owner

ctran commented Apr 28, 2009

I was able to replicate this on my machine.

@ctran
Copy link
Owner

ctran commented Apr 30, 2009

Can you give it a try by installing from this branch?

http://github.com/ctran/annotate_models/tree/v2_0_2

@ctran
Copy link
Owner

ctran commented May 1, 2009

I pushed out a 2.0.2 version to rubyforge so give it a try. Don't know when github will rebuild the gem.

@ctran
Copy link
Owner

ctran commented Aug 4, 2009

I assume this is already working for you. Closing.

jmcnevin pushed a commit to fastpencil/annotate_models that referenced this issue Oct 21, 2013
Fix incorrect behaviour for spec annotating.
ctran pushed a commit that referenced this issue Feb 24, 2014
Fixed gemspec files attribute
@ctran ctran added the released label Dec 17, 2016
bradfeehan pushed a commit to bradfeehan/annotate_models that referenced this issue Apr 7, 2024
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants