Hi. Last week we started getting this error on Heroku Cedar during deployment:
You are trying to install in deployment mode after changing
your Gemfile. Run bundle install elsewhere and add the
updated Gemfile.lock to version control.
If this is a development machine, remove the Gemfile freeze
by running bundle install --no-deployment.
bundle install --no-deployment
You have added to the Gemfile:
You have changed in the Gemfile:
source at vendor/engines
I have filed a support ticket with Heroku but it's going on 5 days and no help yet. We cannot deploy bug fixes and feature releases for our clients until we resolve this issue.
The problem only seems to be with 1.1, the --deployment option and with gems that have :path => '' specified
I've tried everything in the troubleshooting README and I've tried bundle install/update and --deployment locally. The Gemfile.lock file has been deleted, regenerated, committed, pushed and deployed... No dice.
The problem persists locally with the --deployment option but it's absolutely fine with --no-deployment.
Also, this happens with RefineryCMS 1.0.x but not RefineryCMS 2.0.x
It didn't used to happen at all with Bundler 1.0.x
This issue seems fixed by changing the Gemfile like so:
path 'vendor/engines' do
And removing the '~> version' bits
@joemsak can you post the whole Gemfile or the relevant part that reproduces the bug just to ensure we will chase the proper bug? Thanks for your report.
the bottom part is all that's changed