bundle update for gem with git source does not fetch new git ref if it is cached

[Stefan Wrobel]

Ok, that was a very lengthy subject line, but the issue is that bundle update <gemname> does not seem to fetch the latest from a git source if that gem is already cached in vendor/cache. The only way to get it to update seems to be to manually set the ref in the Gemfile and then bundle update, or to remove the cached version and run bundle update. Using bundler 1.5.2.

Am I missing something here? Shouldn't bundle update always fetch the latest from the proper source and update if necessary, unless I pass --local?

[André Arko]

Sounds like an actual bug. Please report it following https://github.com/bundler/bundler/blob/master/ISSUES.md. Thanks!

On Sat, Jan 18, 2014 at 1:09 PM, Stefan Wrobel <swr...@gmail.com> wrote:

Ok, that was a very lengthy subject line, but the issue is that bundle update <gemname> does not seem to fetch the latest from a git source if that gem is already cached in vendor/cache. The only way to get it to update seems to be to manually set the ref in the Gemfile and then bundle update, or to remove the cached version and run bundle update. Using bundler 1.5.2.

Am I missing something here? Shouldn't bundle update always fetch the latest from the proper source and update if necessary, unless I pass --local?

--
You received this message because you are subscribed to the Google Groups "ruby-bundler" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ruby-bundler...@googlegroups.com.
To post to this group, send email to ruby-b...@googlegroups.com.
Visit this group at http://groups.google.com/group/ruby-bundler.
For more options, visit https://groups.google.com/groups/opt_out.