"already activated" error #758
Comments
Let me guess... you didn't remove all your config.gem declarations in your environment.rb? |
To elaborate slightly, if you're getting this error it means Bundler is trying to load rack 1.1.0 but something else other than Bundler has already loaded rack 1.0.1. Bundler obviously can't do anything about gems that are loaded before it itself is loaded, so you have an activation error. |
I unfortunately did remove all traces. If you note, I'm running "bundle exec script/console". I took the time to make a reproduction app:
|
They would be a thing of the past -- if your code didn't declare a dependency on rack ~>1.0.0, and then (at runtime) explicitly demand rack ~>1.1. That is, by definition, an activation error. Just look at your backtrace: action_controller.rb:54. http://github.com/bloom/rails/blob/adgear-next/actionpack/lib/action_controller.rb#L34 |
Ah, I see. Excellent, sorry for the bother. |
I thought those were supposed to be a thing of the past...
Gemfile and friends: http://gist.github.com/621491
We're using this in the context of a Rails application. 2.3.9 to be exact, with one patch applied, which is available here: http://github.com/bloom/rails/tree/adgear-next.
The text was updated successfully, but these errors were encountered: