You can clone with
HTTPS or Subversion.
Apologies if the title of this ticket is confusing, I don't really know how to describe it ;)
Short story: I couldn't figure out how to tell bundler to upgrade the version of the gemspec it was pointed at. I had to hand-edit the Gemfile.lock to resolve this situation. Yes, I am aware that hand-editing of this file is not supported. I am interested in what solution I can use next time this happens.
Specific data and reproducing it: https://gist.github.com/49e37182c5bec863d18e
Me hand-patching my Gemfile.lock: elastic/logstash@ebb90d3
Bug? PEBCAK? :)
Sorry, this is going to be hard for me to reproduce without access to the logstash git repo... is that public somewhere? There are some other comments that might be useful (although honestly probably not) in ISSUES.
Tested again with Ruby 1.9.3 and JRuby 1.6.7 -
sandwich(~/projects/logstash) % rvm 1.9.3 do bundle install
Using cinch (2.0.3)
Using excon (0.14.3)
Using metaclass (0.0.1)
Using mocha (0.11.4)
Using shoulda-context (1.0.0)
Using shoulda-matchers (1.0.0)
Using shoulda (3.0.1)
Using bundler (1.1.5)
Your bundle is complete! It was installed into ./vendor/bundle
sandwich(~/projects/logstash) % JRUBY_OPTS=--1.9 rvm 1.6.7 do bundle install
Fetching gem metadata from http://rubygems.org/.......
Fetching gem metadata from http://rubygems.org/..
Could not find logstash-1.1.1.rc3-java in any of the sources
Both tests were using bundler 1.1.5
% JRUBY_OPTS=--1.9 rvm 1.9.3,1.6.7 do gem list bundler | grep bundler
seems to only affect jruby?
% JRUBY_OPTS=--1.9 rvm 1.9.3,1.6.7 do gem --version
Upgraded to rubygems 1.8.24 with no resolution
Closing, stale. Please do re-open with a repro on recent bundler, script like this one preferred: https://gist.github.com/xaviershay/6207550