On May 18, 2013, at 1:19 PM, John Merlino wrote:
> 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.
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
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/325181DC-ECFE-414C-9BD1-75BF78D50F47%40wdstudio.com?hl=en-US.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment