Git repo as gem source fails on Heroku

[bensie]

Using the following in Gemfile:

git 'https://github.com/outoftime/sunspot.git' do
  gem 'sunspot'
  gem 'sunspot_rails'
end

When deploying to Heroku (cedar), the bundle/deploy appears to run fine, but when the application launches it crashes with:
https://github.com/outoftime/sunspot.git (at master) is not checked out. Please run 'bundle install'

/cc @hone

[hone]

I've identified this as a bug with bundle clean.

$ bundle clean
Removing  (sunspot 95f460904c3b)

We'll get this fixed in 1.1.pre.9

[hone]

fixed on master

[jmileham]

Just hit this too... is there any workaround til 1.1.pre.9 is out? A glance at the commit made me think probably not, but thought I'd ask anyway. And (off topic I know - sorry), is there a rough ETA for availability on cedar if not?

[hone]

I'm not sure of a workaround. You'd have to split off the nested gems into a separate git repo for now. As for timeline, I'm hoping for a release by the end of the week and cedar should follow soon after (same day or next business).

[jmileham]

Sounds good. Thanks.

[nixme]

@jmileham: Unpacking the repo, adding it to the git repo, and using path in the Gemfile worked as a workaround for me

[jmileham]

@nixme I've got a bunch of github forks backporting patches that haven't been released yet in stable versions (of rails for example), as well as a number of different apps that need to run those patched versions -- I ended up cutting .gem files with pirate version numbers (like 3.1.0.rc7is6 -- which satisfies "~> 3.1.0.rc6" while still being < 3.1.0.rc7) and setting up a tiny Geminabox host. Adding that as a source in my Gemfile lets Bundler continue to work its dependency magic.

Looking forward to going back to git when this is out, though -- the workflow of bundling unreleased gems from git repos is ideal.