This repository has been archived by the owner on Apr 14, 2021. It is now read-only.
Gemfile pointed at a gemspec won't upgrade? #2072
Comments
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. |
Yup, https://github.com/logstash/logstash Relevant commits:
|
Tested again with Ruby 1.9.3 and JRuby 1.6.7 -
|
Both tests were using bundler 1.1.5
|
seems to only affect jruby? |
|
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 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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? :)
The text was updated successfully, but these errors were encountered: