Skip to content
This repository has been archived by the owner on Apr 14, 2021. It is now read-only.

bundle update not performing correctly with git source #3300

Closed
BenMorganIO opened this issue Dec 10, 2014 · 6 comments
Closed

bundle update not performing correctly with git source #3300

BenMorganIO opened this issue Dec 10, 2014 · 6 comments

Comments

@BenMorganIO
Copy link
Contributor

Currently I am using the git method to link to a repo a pull down some specific gems as so:

git "https://github.com/spree/spree.git", branch: "2-4-stable" do
  gem "spree_core"
  gem "spree_api"
  gem "spree_backend"
  gem "spree_sample"
end

This happily install the four spree gems for me, but when I go to bundle update spree_core it doesn't actually update the gem. I end up having to comment out to block, bundle, add the block back in, and do another bundle.

Thoughts?

@indirect
Copy link
Member

Sounds like a bug! We’ll investigate when we get the chance.

On Dec 10, 2014, at 12:53 PM, Ben A. Morgan notifications@github.com wrote:

Currently I am using the git method to link to a repo a pull down some specific gems as so:

git "https://github.com/spree/spree.git", branch: "2-4-stable" do
gem "spree_core"
gem "spree_api"
gem "spree_backend"
gem "spree_sample"
end
This happily install the four spree gems for me, but when I go to bundle update it doesn't actually update the gems. I end up having to comment out to block, bundle, add the block back in, and do another bundle.

Thoughts?


Reply to this email directly or view it on GitHub #3300.

@TimMoore
Copy link
Contributor

@BenMorganIO could you help us out with some more info? Paste the output from bundle env into a gist and link to it here. If you are using any private gem servers you might need to check for private info to clean out of the output.

@zedtux
Copy link

zedtux commented Jan 10, 2015

I'm encountering this issue too. I have forked the cucumber gem, updated it this morning, and doing bundle update cucumber is not working.

Here is my bundle env

@zedtux
Copy link

zedtux commented Jan 10, 2015

Also here is the way I wrote the gem line in my Gemfile:

gem 'cucumber', github: 'zedtux/cucumber', branch: 'v1.3.x-bugfix'

@zedtux
Copy link

zedtux commented Jan 10, 2015

Changing to this fixed the issue:

gem 'cucumber', git: 'https://github.com/zedtux/cucumber.git', branch: 'v1.3.x-bugfix'

I don't know if it's a bug in the previous way of writing the gem line or if changing the Gemfile is forcing bundler to update the git repo...

@zedtux
Copy link

zedtux commented Jan 10, 2015

Arf... reverting to the github: 'zedtux/cucumber' and doing update also forced bundler to update the gem. I would say 'touching' the Gemfile make it working, so there is a bug.

indirect added a commit that referenced this issue Feb 8, 2015
If a gem is present in a git or path source, we can stop asking remotes
about it. If a gem is present in a Rubygems source, we still need to ask
all the other sources about it so that we can warn about gems that are
available from multiple sources.

Fixes #3368, #3377, #3300, #3381
@indirect indirect closed this as completed Feb 9, 2015
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

4 participants