I’ve just been battling with a deployment to heroku.
The error that stopped me for ages was
“You have already activated rake 0.9.2.2, but your Gemfile requires rake
0.9.2. Using bundle exec may solve this.”
I eventually managed to solve this by uninstaling rake 0.9.2
adding rake 0.9.2.2 to my gem file
then prompted by the command line a ran:
bundle update rake
“bundle update rake” Seemed to do a lot of things I wasn’t expecting,
going through all gems in the app, updating / installing newer versions
of them. This did solve the deployment problem, but I noticed the
printout from heroku indicated a lot of new installs of gems on the
server as well, updating to newer versions.
So far I haven’t noticed anything going wrong, but the fact that so many
gems have been updated / re installed worries me.
How do people go about making sure that when rails decides to update
everything things don’t break? I’ve definitely had new versions of gems
break apps before.
I’ve read that some processes depend on earlier versions of rake, can
anywhere tell me what depends on this, so I can check if it’s going to
Any advice / approaches on the constant update turmoil would really be