Deactivate a Gem - "You Have Already Activated Rake 0.9.3.Beta.1, But My Gemfile Requires Rake 0.9.2"

You have already activated rake 0.9.0, but your Gemfile requires rake 0.8.7

I thank to Dobry Den, cheers dude. but little more I had to do.
here is solution (works for me).
I had added

gem 'rake','0.8.7'

on Gemfile, which was not there, but my new version of rails automatically install rake(0.9.0).

after I had delete rake0.9.0 by gem uninstall rake
and after doing bundle update rake , I can create and migrate database.

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

Use bundle exec infront of your command

bundle exec rake assets:precompile

This will solve your issue.

I always recommend to use "bundle exec" before any such kind of commands.

can't activate rake (= 0.9.2.2, runtime) for [], already activated rake-10.0.2 for []

You can either :

• run bundle exec rake to use the version of rake listed on your Gemfile.lock if you don't want to update it
• Update the version of rake used in your Gemfile.lock by running bundle update rake and then you will be able to use the command rake again !

already activated spring 1.4.0, but Gemfile requires spring 1.3.3[error]

I fixed it using this.

bundle update spring

Different versions of the same gem in Gemfile - possible?

No, It is disallowed in bundler

premailer - undefined method create_border_shorthand

Are you using Bundler (ie. do you have a Gemfile)?

If so, try adding this:
gem 'css_parser', '1.2.5'

Then bundle install and try again. That will rule out the problem on the github issue report.

---

Related Topics