Skip to content
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

Closed
jordansissel opened this issue Aug 21, 2012 · 8 comments
Closed

Gemfile pointed at a gemspec won't upgrade? #2072

jordansissel opened this issue Aug 21, 2012 · 8 comments

Comments

@jordansissel
Copy link

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? :)

@indirect
Copy link
Member

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.

@jordansissel
Copy link
Author

Yup, https://github.com/logstash/logstash

Relevant commits:

  • working (post hand-patch): ebb90d326b86143baff7e7bbd6b4409f951c613a
  • not working (pre hand-patch): 07c846e7869fb36e54f9888f73c26a944f4166f4

@jordansissel
Copy link
Author

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

@jordansissel
Copy link
Author

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
bundler (1.1.5)
bundler (1.1.5)

@jordansissel
Copy link
Author

seems to only affect jruby?

@jordansissel
Copy link
Author

% JRUBY_OPTS=--1.9 rvm 1.9.3,1.6.7 do gem --version                  
1.8.24
1.8.15

@jordansissel
Copy link
Author

Upgraded to rubygems 1.8.24 with no resolution

@xaviershay
Copy link
Contributor

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.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants