...followed by a backtrace, memory map and more. Fix The culprit seems to be Bundler 1.14 when used with Ruby 1.8.7. Downgrade to the maximum version that is compatible...
...are trying to install in deployment mode after changing *** [err :: some-host.makandra.de] your Gemfile. Run `bundle install` elsewhere and add the *** [err :: some-host.makandra.de] updated Gemfile.lock to version control. *** [err :: some-host.makandra.de]
...have deleted from the Gemfile: *** [err :: some-host.makandra.de] * We found out a newer version of bundler runs on the machines to be deployed to (see bundle -v, it was 2.0.1 in...
...need to run bin/rake to use them. On older projects, you want to run "bundle exec rake" to avoid those ugly "already activated rake x.y.z" errors that hit you when...
...plain rake command which uses a binstubbed bin/rake if available and falls back to bundle exec rake if necessary. Try it To see if it works for you, run the...
...comparators like >= or ~>. That way it is possible to fetch the latest version of Bundler 1 with this command: gem install bundler -v '~>1' How to install bundler for Ruby...
...is a common usecase where you might need Bundler...
If bundle install shows the following message for you ... Error Bundler::HTTPError during request to dependency API ... upgrade to Bundler ≥ 1.2.4: gem install bundler Apparently, it just hides the message...
...command line tools. When your tests involve a Rails test application, your tool's Bundler environment will shadow that of the test application. To fix this, just call unset_bundler...
...now any command run through Aruba (e.g. via #run_simple) will have a clean Bundler environment. module Customization # Improve the internal #run method provided by Aruba::Api to run commands...
Add gem 'license_finder' to the develoment dependencies of your project and run bundle install Add spec/license_finder_spec.rb with describe 'license_finder' do describe 'action_items' do before :all do...
...package_managers = @stdout.scan(/^LicenseFinder::(\w+).*is active/).flatten expect(package_managers).to contain_exactly 'Bundler', 'Please list all expected package managers here' end it 'has no dependencies with unapproved licenses...
...install RubyGems from the repository but install the version from the webpage instead. Get Bundler: sudo gem install bundler Rails and other gems for a project should now be installed...
...via bundle install from the project directory. If you need Rails and don't have a Gemfile you can do it old-school: sudo gem install rails -v=2.3.12.
...ran into trouble on a fairly fresh installed VM, running Ubuntu. I tried to bundle install and got this stacktrace: Fetching gem metadata from https://rubygems.org/.Unfortunately, a fatal error...
...has occurred. Please see the Bundler troubleshooting documentation at http://bit.ly/bundler-issues. Thanks! /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:36:in `gem_original_require': no such file to load -- net/https (LoadError) from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:36:in...
...results in deploys not working when running with old deploy.rb files. So let's bundle it. Put capistrano into your Gemfile, like this: # Gemfile group :deploy do gem 'capistrano'
...capistrano_colors' end It's possible you need to do a bundle update net-ssh to get things running. Now double check that all your custom hooks are actually still...
You can specify the version of bundler to execute a command (most often you need an older version of bundler, but don't want to uninstall newer ones):
Bundler version 1.0.10 An example is rails 3.2, which freezes bundler at version ~> 1.0: Bundler could not find compatible versions for gem "bundler": In Gemfile: rails (~> 3.2) was resolved...
Use bundler > 1.15 to fix Gem::LOADED_SPECS_MUTEX (NameError). Given the following project: ruby -v ruby 1.8.7 bundler -v Bundler version 1.13.7 gem -v 1.8.30 rails -v
...LOADED_SPECS_MUTEX (NameError) The previous settings described in Maximum version of Rubygems and Bundler for Ruby 1.8.7 and Rails 2.3 (even the rails version was rails 3.2 and not...
Even when you're using bundler, it might be significant in which order your gems are listed in your Gemfile. This can happen when gems are running around calling require...
...tests/gherkin/runtime_logger Error creating formatter: ParallelTests::Gherkin::RuntimeLogger (LoadError) This will happen when you upgrade Bundler to version 1.13.x and appears to be "by design" since there is a Bundler...
...by setting that flag. You should commit the resulting config file into the repository! bundle config --local disable_exec_load true There is a GitHub issue that you can follow...
...the libxml2 extension source. gem 'nokogiri', force_ruby_platform: true If you are on Bundler < 2.3.18, either upgrade Bundler (if possible) or use the alternative approaches from the nokogiri docs...
All servers and developer machines at makandra are already configured using the global Bundler configuration. You need to specify that using the Bundler configuration, either globally, or locally (per...
If you just upgraded to Bundler 10.0.10 you might get the following error when bringing up Rails: /usr/lib/ruby/1.9.1/psych.rb:148:in `parse': couldn't parse YAML at line 17 column...
...by Rails localization files (en.yml, de.yml, etc.) using symbols for various translation strings, and Bundler 10.0.10 defaults to a new YAML engine which cannot handle symbols. You can switch back...
...called seed in term of tests. With Cucumber you can run tests like this: bundle exec cucumber --order random features # The test outout Randomized with seed 19497
...call bundle exec cucumber --order random:19497 features now, the scenarios are run in the same order. In case you use ParallelTests it might be useful to get a final...
When running an executable, ALWAYS use bundle exec. In some cases, running executables without bundle exec may work, if the executable happens to be installed in your system and does...
...not pull in any gems that conflict with your bundle. However, this is unreliable and is the source of considerable pain. Even if it looks like it works, it may...
Given you use Capistrano together with bundler to automatically install your gems when deploying. I recently had the problem that Capistrano stalled like this: [err :: host.name.tld] Username:
...installed, something is seriously wrong and needs to be fixed. If you accidently executed bundle install some_gem although you wanted bundle update some_gem What is wrong
...Gemfile asks for some-gem which you can see when running gem list but bundle show some-gem just gives you an error: Could not find gem 'some-gem', in...
Bundler 1.1 has been released. With this version you no longer need to wait for this: Fetching source index… The new Bundler is smarter and can fetch required metadata in...
You can install the new version by saying: sudo gem install bundler
Confusingly, RVM installs the bundler gem into the @global gemset, which is available to all gemsets and Rubies. You can get around this and install a particular bundler version like...
rvm @global do gem uninstall bundler rvm @global do gem install bundler -v...
When you are calling Bundler from your shell scripts, you might find it useful that a failed bundle call returns a different error code depending on the type of problem...
...a recent version of Rubygems You installed some gems that install a binary (like bundle, rake or rails) with code that only works with modern Rubygems versions You downgraded Rubygems...
...gem pristine --all Fixing an existing Ruby installation (fallback method) Uninstall all gems (including bundler) or remove and re-install the Ruby version Upgrade/downgrade to the version you want using...