If you are using Bundler 1.1 or later you can use bundle clean, just as you imagined you could. This is redundant if you’re using bundle install –path (Bundler manages the location you specified with –path, so takes responsibility for removing outdated gems), but if you’ve used Bundler to install the gems as system gems … Read more
bundle exec executes a command in the context of your bundle. That means it uses the gems specified in your Gemfile. Much of the time, running bundle exec rake foo has the same results as if you just ran rake foo, especially if you have the same gems installed systemwide as in your Gemfile. However, … Read more
Here is the way I fix the “invalid date format in specification” error: 1.) Go to the specifications folder located at: /usr/local/lib/ruby/gems/1.8/specifications/ 2.) Find the spec that is causing the problem. 3.) Change s.date = %q{2011-05-21 00:00:00.000000000Z} to s.date = %q{2011-05-21} That’s a WIN for me! Good Luck
THIS ANSWER IS OUTDATED Take a look at –without option: bundle install –without development test By default Bundler installs all gems and your application uses the gems that it needs. Bundler itself knows nothing about Rails and the current environment.
Try the following commands: gem uninstall bundler gem install bundler –version ‘1.0.0’
This is not possible, and likely never will be because it would be rather heavy-handed for RubyGems to allow gem developers to require that users have a specific version control system installed to access a gem. Gems should be self-contained with a minimal number of dependencies so that people can use them in as wide … Read more
This is the purpose of the Gemfile.lock file – running bundle install with a Gemfile.lock present only installs using the dependencies listed in there; it doesn’t re-resolve the Gemfile. To update dependencies / update gem versions, you then have to explicitly do a bundle update, which will update your Gemfile.lock file. If there wasn’t a … Read more
If you want to find out where a particular gem is stored you can run bundle info <gem-name>. For example: user@host$ bundle info rake /var/bundle/ruby/2.1.0/gems/rake-10.4.2 For older versions of rake, the command could be bundle show <gem_name>.
The error message you’re getting regarding Gemfile.lock may be because your Gemfile and Gemfile.lock don’t agree with each other. It sounds like you’ve changed something in your Gemfile since you last ran bundle install (or update). When you bundle install, it updates your Gemfile.lock with any changes you’ve made to Gemfile. Make sure you run … Read more
Bundler version 2 introduced a new feature to automatically use the version of Bundler specified in the Gemfile.lock of your project. Thus, if you have an existing Gemfile.lock with a line like this at the bottom BUNDLED WITH 1.17.3 Bundler will try to run with a Bundler version < 2.0. Since you just have Bundler … Read more