You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's more of an issue of bundler, still when updating a single gem bundle check succeeds while printing info about missing gem on STDERR. Fixed it with set :bundle_check_before_install, false. Maybe we should add a notice to the README?
From my capistrano.log:
bundle check
DEBUG [aae77348] The following gems are missing
* rugged (1.5.0.1)
DEBUG [aae77348] Install missing gems with `bundle install`
DEBUG [aae77348] Finished in 1.202 seconds with exit status 0 (successful).
INFO The Gemfile's dependencies are satisfied, skipping installation
The text was updated successfully, but these errors were encountered:
Strange! I doubt this is a bundler issue. I found one upstream bug report but that ultimately was found to be due to a shell alias for bundler and not a bug in bundler itself: rubygems/rubygems#3233
Is it possible that bundle check is invoking an alias or wrapper script in your shell environment?
It's more of an issue of bundler, still when updating a single gem
bundle check
succeeds while printing info about missing gem on STDERR. Fixed it withset :bundle_check_before_install, false
. Maybe we should add a notice to the README?From my capistrano.log:
The text was updated successfully, but these errors were encountered: