You can clone with
HTTPS or Subversion.
I've created a test case in which you have a Rails project depending on gem A (through :git). This gem A depends on another gem B also through :git, and when running bundle update on the rails project, gem B isn't installed.
git clone email@example.com:ereslibre/emptyrails.git
Could not find gem 'gem-b (~> 0.0.1) ruby', which is required by gem 'gem-a (~> 0.0.1) ruby', in any of the sources.
Running bundle update in gem-a works, reporting:
Fetching source index for http://rubygems.org/
Using gem-b (0.0.1) from firstname.lastname@example.org:ereslibre/gem-b.git (at master)
Using gem-a (0.0.1) from source at /home/ereslibre/test/gem-a
Using bundler (1.0.21)
Your bundle is updated! Use `bundle show [gemname]` to see where a bundled gem is installed.
Right after that, doing bundle update again in the emptyrails project reports the same error:
That repo no longer exists. I am going to go ahead and assume the issue is now fixed.