Phusion Passenger Error: You Have Activated Rack 1.2.1, But Your Gemfile Requires Rack 1.2.2

Phusion Passenger Error: You have activated rack 1.2.1, but your Gemfile requires rack 1.2.2

try to restart your server after edit in your Gemfile and put this: gem 'rack', '1.2.1'

You have already activated rack 1.6.1, but your Gemfile requires rack 1.5.5.

I turns out that I was using Rails 4.1.2 which used Rack 1.5.5. When I updated my Rails app to use Rails 4.2.6 the later version of rack was loaded and this conflict in the gems was solved.

You have already activated rack 1.6.0, but your Gemfile requires rack 1.6.4

you need to uninstall one version of rack which is not required.

Do this please

gem uninstall rack -v 1.6.0

Reference: How to force rack to work around the usual "You have already activated rack..." bug?

You have already activated X, but your Gemfile requires Y

Using bundle exec is the right way to do this.

Basically what's happening is that you've updated rake to 0.9.2 which now conflicts with the version specified in your Gemfile. Previously the latest version of rake you had matched the version in your Gemfile, so you didn't get any warning when simply using rake.

Yehuda Katz (one of the original Bundler developers) explains it all in this blog post.

To avoid typing bundle exec ... all the time, you could set up an alias or function in your shell for commands you commonly use with Bundler. For example this is what I use for Rake:

$ type bake
bake is a function
bake () 
{ 
    bundle exec rake "$@"
}

---

Related Topics