Use https:// instead of git:// on GitHub URL's

[fuadsaud]

See #1820

[gnufied]

Awesome. thank you so much. While we are at it, can we also update source :rubygems to source "https://rubygems.org" ? It keeps throwing deprecation warnings in spec runs. @fuadsaud

[indirect]

@gnufied outside the scope of this pull, but fixing deprecations inside our own spec suite sounds like a good idea. :)

[gnufied]

okay, cool. agreed lets merge this.

[fuadsaud]

@gnufied mock calls are also making RSpec go crazy on warnings.

[indirect]

Separate pull request for that was merged yesterday.

On Mon, Jul 29, 2013 at 11:57 AM, Fuad Saud [email protected]
wrote:

mock calls are also making RSpec go crazy on warnings.

Reply to this email directly or view it on GitHub:
#2569 (comment)

[indirect]

As far as I can tell, this doesn't break any backwards compatibility, and it is following github's suggestions for more efficient transfer of repos. 👍

[fuadsaud]

@indirect nice, thanks!

[jgarber]

So, we bundled using 1.4.0.pre.1 and committed the resulting change to Gemfile.lock. Then when we deployed with bundler 1.3.5, we got this:

bundle install --path=vendor/bundle --deployment --without development test cucumber staging production --binstubs ----
STDOUT: 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.

You have added to the Gemfile:
* source: git://github.com/sporkrb/spork-rails.git (at master)
* source: git://github.com/belighted/masq.git (at rails_4)

You have deleted from the Gemfile:
* source: https://github.com/belighted/masq.git (at rails_4)
* source: https://github.com/sporkrb/spork-rails.git (at master)

You have changed in the Gemfile:
* masq from `git://github.com/belighted/masq.git (at rails_4)` to `no specified
source`
* spork-rails from `git://github.com/sporkrb/spork-rails.git (at master)` to `no
specified source`

[indirect]

Yeah, the change isn't backwards compatible and has been reverted from Bundler 1.4. Please install 1.4.pre.2, which goes back to using git URLs. Bundler 2.0 will make the breaking change to HTTPS.

[jgarber]

Awesome! Thanks!

[schlamar]

@indirect Ah nice, exactly what I am needing (git port is blocked by proxy). Any ETA for Bundler 2.0?

[indirect]

you can just use :git => "https..."

On Sun, Sep 8, 2013 at 11:52 PM, Marc Schlaich [email protected]
wrote:

@indirect Ah nice, exactly what I am needing (git port is blocked by proxy). Any ETA for Bundler 2.0?

Reply to this email directly or view it on GitHub:
#2569 (comment)

[schlamar]

Yes, I know. But that is not a perfect solution for shared repositories.

[c9s]

we should allow ssh+git protocol to be configured for GitHub. With https you have to enter the username password for the private repository.
and with ssh+git clone, it is actually faster than https