You have already activated rake 10.0.4, but your Gemfile requires rake 10.0.3

Rails
1

I’m careful to create separate gemsets for each project, so when I run
bundle install, it only installs gems for that gemset. This way gems
dont creep into the wrong projects. Now I just pulled a project from
github. I made sure I was in the correct gemset, and then I run bundle
install and it works fine. but then when I use rake to create the
database “rake db:create”. I get this error:

You have already activated rake 10.0.4, but your Gemfile requires rake
10.0.3.

What does it mean “you already activated rake 10.0.4”? All that should
be installed for this gemset is whatever is in Gemfile.

2

On May 18, 2013, at 1:19 PM, John M. wrote:

What does it mean “you already activated rake 10.0.4”? All that should
be installed for this gemset is whatever is in Gemfile.

Did you declare rake in your Gemfile? Also, did you try bundle exec rake
db:create?

I think maybe rake is loaded before your gemset has a chance to assert
itself.

Walter

3

Bundler is present in the global gemset. What I usually do is rvm gemset
use @global and then do a gem uninstall bundler

4

I guess you have installed rake in your global gemset for the ruby
version you are using.
Go outside the project and run rvm use <ruby version>@global and then
gem list. If you see rake in the list, that means you have it in the
global gemset. No matter which gemset you use with the ruby version, the
gems in the global gemset will be available.