1.1 --deployment option fails with :path => '' gems during Heroku cedar push #1782

Closed
joemsak opened this Issue Mar 19, 2012 · 5 comments

Comments

Projects
None yet
3 participants

joemsak commented Mar 19, 2012

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.

You have added to the Gemfile:

  • source: source at vendor/engines

You have changed in the Gemfile:

  • refinerycms-portfolio_entries from source at vendor/engines to source at vendor/engines
  • refinerycms-blog from source at vendor/engines to source at vendor/engines
  • refinerycms-news from source at vendor/engines to source at vendor/engines
  • refinerycms-search from source at vendor/engines to 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.

joemsak commented Mar 19, 2012

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

joemsak commented Mar 19, 2012

This issue seems fixed by changing the Gemfile like so:

path 'vendor/engines' do
  gem 'refinerycms-portfolio_entries'
end

And removing the '~> version' bits

hone was assigned Mar 19, 2012

Contributor

josevalim commented Mar 20, 2012

@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.

joemsak commented Mar 20, 2012

the bottom part is all that's changed

hone closed this in d24e788 Mar 21, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment