bundler 1.7.15 → 1.8.0.pre

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 87c0e0f8a86277370e75de2355fc489fcafc1cc5
-  data.tar.gz: db0d05676f078159a3387ea000fe20ef755603b7
+  metadata.gz: 479faa1691c86039ec5e869bad6dcce4d5ccf4fc
+  data.tar.gz: 5292b6135750e581aeb3007b8a8675f7530b3e2a
 SHA512:
-  metadata.gz: 918b79b442b84c1ea8b128dc3ac1016d31402e17fe5e083c5cc923f4adea219abc1b8eb3485fcba2bef465f68ff0cf19d89fa1a2a213e437ec8583743a161e2a
-  data.tar.gz: 74ca32121adf3f19442d2815deec3186dca5ecc434ca9337df4445a0107b59e8c8516f768f50551554b4011b81a0d057eb9fc1566b9693611d8816cd0ab52683
+  metadata.gz: cb0d50e7108d2175c806dc8e3057243ba7f69ca53d17d7c7acb23da574339eaba836811a7287060c83f4143edeeee461b27fa5bc868b8c623391a88dc0a91d48
+  data.tar.gz: d90bbeeca48a52828aa24304b71a3f68e4ced97001a13ea404262b4ae2c28ca99af70f3c2bfa62330090fd562b40a98d9da673768d5f37360ebc3824972b1426

data/.gitignore

@@ -3,23 +3,14 @@
 # https://help.github.com/articles/ignoring-files and find useful gitignore
 # samples at https://github.com/github/gitignore
 
-# system crap
-.DS_Store
-.*.swp
-
 # files created by running the specs
-tmp/
-
-# built gems
-pkg/
-*.gem
+/tmp/
 
-# rubinius bytecode
-*.rbc
-.rbx/
+# gems built by `rake build`
+/pkg/
 
 # output from ronn
-lib/bundler/man/
+/lib/bundler/man/
 
 # output from ci_reporter
-spec/reports/
+/spec/reports/

data/.rspec

@@ -1,2 +1,3 @@
 --format documentation
 --color
+--warnings

data/.travis.yml

@@ -1,9 +1,11 @@
 language: ruby
 script: rake spec:travis
 before_script: travis_retry rake spec:travis:deps
+
 branches:
   only:
     - master
+    - 1-8-stable
     - 1-7-stable
     - 1-6-stable
     - 1-5-stable
@@ -11,38 +13,49 @@ branches:
     - 1-2-stable
     - 1-1-stable
     - 1-0-stable
+
 notifications:
   email:
     # andre
     - secure: "bCcvqJT7YrBawtkXXwHhT+jOFth7r2Qv/30PkkbhQxk6Jb3xambjCOJ3U6vJ\ngYmiL50exi5lUp3oc3SEbHN5t2CrZqOZDQ6o7P8EAmB5c0oH2RrYaFOkI5Gt\nul/jGH/96A9sj0aMwG7JfdMSfhqj1DUKAm2PnnbXPL853VfmT24="
     # terence
     - secure: "MQ8eA5Jb8YzEpAo58DRGfVJklAPcEbAulpBZnTxp0am6ldneDtJHbQk21w6R\nj5GsDHlzr/lMp/GHIimtUZ7rLohfND8fj/W7fs1Dkd4eN02/ERt98x3pHlqv\nvZgSnZ39uVYv+OcphraE24QaRaGWLhWZAMYQTVe/Yz50NyG8g1U="
-  campfire:
+  slack:
     on_success: change
     on_failure: always
     rooms:
-      # Bundler Ops
-      secure: MNTSGIySYwHia5gIgRiZxXtPMPDIP9KmzQk7Kq2ZoVvP3mIk8W1TMkvcyFkEf6uCasyVZZixzUBfY+E0BlHAz1ycQpTh1jvSpuIpEVYW48ShJldJ+8W8xfzafyOHii3z7VrDaomEffmMDdmHRsbQAfekMjdR4bTpXtT9V+wOXlg=
+      - secure: JxBi7DDJGkIF/7f/FSN/HUHpvV4EKfQccZHTPd1b2pNJn3GXo6u+tNVbAw2WjxYzPyPQI3ZcYBCU9SEXp/i7VmG8uMzh8Kyildw+miSKYKVb90uYqcsXWzbxwyNBgJLvyDkzST45H5lgnyAicee3WkFes/WDZikIajbH7ztdb04=
+
 rvm:
-  - 2.1.1
+  - 2.1
   - 2.0.0
   - 1.9.3
   - 1.8.7
+
 # Rubygems versions MUST be available as rake tasks
 # see Rakefile:66 for the list of possible RGV values
 env:
   # We need to know if changes to rubygems will break bundler on release
   - RGV=master
   # Test the latest rubygems release with all of our supported rubies
-  - RGV=v2.2.2
+  - RGV=v2.4.4
+
 matrix:
+  fast_finish: true
   include:
+    # Ruby 2.1, Rubygems 2.2.2 and up
+    - rvm: 2.1
+      env: RGV=v2.2.2
     # Ruby 2.0.0, Rubygems 2.0 and up
+    - rvm: 2.0.0
+      env: RGV=v2.2.2
     - rvm: 2.0.0
       env: RGV=v2.1.11
     - rvm: 2.0.0
       env: RGV=v2.0.14
     # Ruby 1.9.3, Rubygems 1.5.3 and up
+    - rvm: 1.9.3
+      env: RGV=v2.2.2
     - rvm: 1.9.3
       env: RGV=v2.1.11
     - rvm: 1.9.3
@@ -57,7 +70,7 @@ matrix:
       env: RGV=v1.5.3
     # Ruby 1.8.7, Rubygems 1.3.6 and up
     - rvm: 1.8.7
-      env: RGV=v2.1.11
+      env: RGV=v2.2.2
     - rvm: 1.8.7
       env: RGV=v2.0.14
     - rvm: 1.8.7
@@ -82,20 +95,14 @@ matrix:
     # Ruby 1.9.2 sanity check
     # (but it's just too slow and sometimes goes over the Travis limit)
     - rvm: 1.9.2
-      env: RGV=v2.2.2
+      env: RGV=v2.3.0
     # Ruby-head (we want to know how we're doing, but not fail the build)
     - rvm: ruby-head
       env: RGV=master
-    # JRuby, the latest (not maintained, but good to know)
-    - rvm: jruby
-      env: RGV=v2.2.2
-    # Rubinius, the latest (not maintained, but good to know)
-    - rvm: rbx
-      env: RGV=v2.2.2
   allow_failures:
     - rvm: 1.8.7
-      env: RGV=2.1.11
+      env: RGV=v2.1.11
     - rvm: 1.9.2
     - rvm: ruby-head
     - rvm: jruby
-    - rvm: rbx
+    - rvm: rbx-2

data/CHANGELOG.md

@@ -1,23 +1,36 @@
-## 1.7.15 (2015-04-29)
+## 1.8.0.pre (2015-01-26)
 
-Bugfixes:
-
-  - Respect Gemfile sources when installing a gem present in two sources (#3585, @tmoore)
+Features:
 
-## 1.7.14 (2015-03-30)
+  - add metadata allowed_push_host to new gem template (#3002, @juanitofatas)
+  - adds a `--no-install` flag to `bundle package` (@d-reinhold)
+  - add `bundle config auto_install true` to install automatically (@smashwilson)
+  - add `bundle viz --without` to exclude gem groups from resulting graph (@fnichol)
+  - prevent whitespace in gem declarations with clear messaging (@benlakey)
+  - tries to find a `bundler-<command>` executable on your path for non-bundler commands (@andremedeiros)
+  - tries to find `gems.rb` and it's new counterpart, `gems.locked` (@andremedeiros)
+  - change the initial version of new gems from `0.0.1` to `0.1.0` (@petedmarsh)
+  - add `package --all-platforms` to cache gems for each known platform (@ccutrer)
+  - speed up `exec` when running commands on the $PATH (@kirs)
+  - add gem code of conduct file and option (@kirs)
+  - add config settings for gem license and tests (@kirs)
+  - add `bin/setup` and `bin/console` to new gems (@indirect)
+  - include configured user-agent in network requests (@indirect)
+  - support `github`, `gist`, and `bitbucket` options on git gems (@indirect)
+  - add `package --cache-path` and `config cache_path` for cache location (@jnraine)
+  - allow `config` to work even when a Gemfile is not present (@dholdren)
+  - add `config gemfile /path` for other Gemfile locations (@dholdren)
 
 Bugfixes:
 
-  - Keep gems locked when updating another gem from the same source (#3250, @indirect)
-  - Don't add extra quotes around long, quoted config values (@aroben, #3338)
+  - reduce memory usage with threaded parallel workers (@Who828)
+  - support read-only git gems (@pmahoney)
+  - various resolver performance improvements (@dubek)
+  - untaint git gem paths for Rubygems compatibility (@tdtds)
 
-## 1.7.13 (2015-02-07)
-
-Bugfixes:
+Documentation:
 
-  - Look up installed gems in remote sources (#3300, #3368, #3377, #3380, #3381, @indirect)
-  - Look up gems across all sources to satisfy dependencies (#3365, @keiths-osc)
-  - Request dependencies for no more than 100 gems at a time (#3367, @segiddins)
+  - add missing Gemfile global `path` explanation (@agenteo)
 
 ## 1.7.12 (2015-01-08)
 
@@ -121,6 +134,22 @@ Bugfixes:
 
   - Warn on ambiguous gems available from more than one source (@TimMoore)
 
+## 1.6.7 (2014-10-19)
+
+Features:
+
+  - warn to upgrade when using useless source blocks (@danfinnie)
+
+Documentation:
+
+  - explain how to use gem server credentials via ENV (@hwartig)
+
+## 1.6.6 (2014-08-23)
+
+Bugfixes:
+
+  - restore Gemfile credentials to Gemfile.lock (@indirect)
+
 ## 1.6.5 (2014-07-23)
 
 Bugfixes:
@@ -202,6 +231,7 @@ Features:
   - `bundle show --verbose` Add gem summary to the output (@lardcanoe)
   - `bundle gem GEM --ext` now generates a skeleton for a C extension (@superdealloc)
   - Avoid using threequals operator where possible (@as-cii)
+  - Add `bundle update --group` to update specific group (#2731 @banyan)
 
 Documentation:
 

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,40 @@
+# Bundler Code of Conduct
+
+The Bundler project strongly values contributors from anywhere, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. As a result, the Bundler team has agreed to and enforces this code of conduct in order to provide a harassment-free experience for everyone who participates in the development of Bundler.
+
+### Summary
+
+Harassment in code and discussion or violation of physical boundaries is completely unacceptable anywhere in the Bundler project’s codebases, issue trackers, IRC channel, Campfire, mailing lists, meetups, and other events. Violators will be warned and then blocked or banned by the core team at or before the 3rd violation.
+
+### In detail
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images, deliberate intimidation, stalking, sustained disruption, and unwelcome sexual attention.
+
+Individuals asked to stop any harassing behavior are expected to comply immediately.
+
+Maintainers, including the core team, are also subject to the anti-harassment policy.
+
+If anyone engages in harassing behavior, including maintainers, we may take appropriate action, up to and including warning the offender, deletion of comments, removal from the project’s codebase and communication systems, and escalation to Github support.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of [the core team](http://bundler.io/contributors.html) or [email the core team](mailto:team@bundler.io) immediately.
+
+We expect everyone to follow these rules anywhere in the Bundler project’s codebases, issue trackers, IRC channel, group chat, and mailing lists.
+
+Finally, don't forget that it is human to make mistakes! We all do. Let’s work together to help each other, resolve issues, and learn from the mistakes that we will all inevitably make from time to time.
+
+
+### Thanks
+
+Thanks to the [JSConf Code of Conduct](http://jsconf.com/codeofconduct.html) and [Fedora Code of Conduct](http://fedoraproject.org/code-of-conduct) for inspiration and ideas. Additional thanks to [Contributor Covenant](http://contributor-covenant.org) for the [default code of conduct](https://github.com/bundler/bundler/blob/master/lib/bundler/templates/newgem/CODE_OF_CONDUCT.md.tt) included in generated gems.
+
+
+### License
+
+<p class="license" xmlns:dct="http://purl.org/dc/terms/" xmlns:vcard="http://www.w3.org/2001/vcard-rdf/3.0#">
+  To the extent possible under law, <a rel="dct:publisher" href="http://bundler.io">The Bundler Team</a> has waived all copyright and related or neighboring rights to the <span property="dct:title">Bundler Code of Conduct</span>. This work is published from the <span property="vcard:Country" datatype="dct:ISO3166" content="US" about="http://bundler.io">United States.</span>
+  <br>
+  <br>
+  <a rel="license" href="http://creativecommons.org/publicdomain/zero/1.0/">
+    <img src="http://i.creativecommons.org/p/zero/1.0/88x31.png" style="border-style: none;" alt="CC0">
+  </a>
+</p>

data/CONTRIBUTING.md

@@ -2,18 +2,20 @@
 
 Bundler welcomes contributions from *everyone*. While contributing, please follow the project [code of conduct](http://bundler.io/conduct.html), so that everyone can be included.
 
-Here are some ways you can contribute:
-
-  - by using prerelease versions
-  - by reporting bugs
-  - by suggesting new features
-  - by writing or editing documentation
-  - by closing issues
-  - by reviewing patches
-  - by refactoring code
-  - by writing code (no patch is too small! fix typos or bad whitespace)
-
-If you'd like to help make Bundler better, you totally rock! Please check out the [DEVELOPMENT](https://github.com/bundler/bundler/blob/master/DEVELOPMENT.md) file for an introduction to the project, guidelines for contributing, and details about what would be helpful.
+If you'd like to help make Bundler better, you totally rock! Here are some ways you can contribute:
+
+  - by using prerelease versions (run `gem install bundler --pre`)
+  - by [reporting bugs you encounter](https://github.com/bundler/bundler/issues/new)
+  - by [suggesting new features](https://github.com/bundler/bundler-features/issues/new)
+  - by adding to or editing [the Bundler documentation website](http://bundler.io) and [Bundler man pages](http://bundler.io/man/bundle.1.html)
+  - by [checking issues for completeness](https://github.com/bundler/bundler/blob/master/DEVELOPMENT.md#bug-triage)
+  - by closing issues that are not complete
+  - by adding a failing test for reproducible [reported bugs](https://github.com/bundler/bundler/issues)
+  - by reviewing [pull requests](https://github.com/bundler/bundler/pulls) and suggesting improvements
+  - by improving existing code, including [suggestions from PullReview](https://www.pullreview.com/github/bundler/bundler/reviews/master)
+  - by [writing code](https://github.com/bundler/bundler/blob/master/DEVELOPMENT.md) (no patch is too small! fix typos or bad whitespace)
+
+If you need help getting started, check out the [DEVELOPMENT](https://github.com/bundler/bundler/blob/master/DEVELOPMENT.md) file for steps that will get you up and running.
 
 Thanks for helping us make Bundler better.
 

data/DEVELOPMENT.md

@@ -2,7 +2,7 @@ Great to have you here! Here are a few ways you can help out with [Bundler](http
 
 # Where should I start?
 
-You can start learning about Bundler by reading [the documentation](http://bundler.io). If you want, you can also read a (lengthy) explanation of [why Bundler exists and what it does](http://bundler.io/v1.5/rationale.html). You can also check out discussions about Bundler on the [Bundler mailing list](https://groups.google.com/group/ruby-bundler) and in the [Bundler IRC channel](http://webchat.freenode.net/?channels=%23bundler), which is #bundler on Freenode.
+You can start learning about Bundler by reading [the documentation](http://bundler.io). If you want, you can also read a (lengthy) explanation of [why Bundler exists and what it does](http://bundler.io/rationale.html). You can also check out discussions about Bundler on the [Bundler mailing list](https://groups.google.com/group/ruby-bundler) and in the [Bundler IRC channel](http://webchat.freenode.net/?channels=%23bundler), which is #bundler on Freenode. Please note that this project is released with a contributor [code of conduct](http://bundler.io/conduct.html). By participating in this project you agree to abide by its terms.
 
 ## Your first commits
 
@@ -70,7 +70,7 @@ Finally, the ticket may be a duplicate of another older ticket. If you notice a
 
 If you would like to add a new feature to Bundler, please follow these steps:
 
-  1. [Create an issue](https://github.com/bundler/bundler-features/issues/new) to discuss your feature.
+  1. [Create an issue](https://github.com/bundler/bundler-features/issues/new) in the bundler-features repo to discuss your feature.
   2. Base your commits on the master branch, since we follow [SemVer](http://semver.org) and don't add new features to old releases.
   3. Commit the code and at least one test covering your changes to a feature branch in your fork.
   4. Put a line in the [CHANGELOG](https://github.com/bundler/bundler/blob/master/CHANGELOG.md) summarizing your changes under the next release under the "Features" heading.
@@ -115,3 +115,5 @@ Finally, sharing your experiences and discoveries by writing them up is a valuab
 Examples of how Bundler is used help everyone, and we’ve discovered that people already use it in ways that we never imagined when we were writing it. If you’re still not sure what to write about, there are also several projects doing interesting things based on Bundler. They could probably use publicity too.
 
 If you let someone on the core team know you wrote about Bundler, we will add your post to the list of Bundler resources on the Github project wiki.
+
+Finally, participate carefully in the  all contributors to the Bundler project must agree to the contributor [code of conduct](http://bundler.io/conduct.html). By participating in this project you agree to abide by its terms.

data/ISSUES.md

@@ -10,7 +10,7 @@ discuss features. The bundler issue tracker is only for bugs.**
 
 Instructions for common Bundler uses can be found on the [Bundler documentation site](http://bundler.io/).
 
-Detailed information about each Bundler command, including help with common problems, can be found in the [Bundler man pages](http://bundler.io/v1.3/man/bundle.1.html).
+Detailed information about each Bundler command, including help with common problems, can be found in the [Bundler man pages](http://bundler.io/man/bundle.1.html).
 
 ## Troubleshooting
 

data/README.md

@@ -1,9 +1,11 @@
-[![Code Climate](https://img.shields.io/codeclimate/github/bundler/bundler.svg)](https://codeclimate.com/github/bundler/bundler)
-[![Build Status](https://img.shields.io/travis/bundler/bundler/master.svg)](https://travis-ci.org/bundler/bundler)
-[![Version     ](https://img.shields.io/gem/v/bundler.svg)](https://rubygems.org/gems/bundler)
+[![Version     ](https://img.shields.io/gem/v/bundler.svg?style=flat)](https://rubygems.org/gems/bundler)
+[![Build Status](https://img.shields.io/travis/bundler/bundler/master.svg?style=flat)](https://travis-ci.org/bundler/bundler)
+[![Code Climate](https://img.shields.io/codeclimate/github/bundler/bundler.svg?style=flat)](https://codeclimate.com/github/bundler/bundler)
+[![Inline docs ](http://inch-ci.org/github/bundler/bundler.svg?style=flat)](http://inch-ci.org/github/bundler/bundler)
 
 # Bundler: a gem to bundle gems
-Bundler keeps ruby applications running the same code on every machine.
+
+Bundler makes sure Ruby applications run the same code on every machine.
 
 It does this by managing the gems that the application depends on. Given a list of gems, it can automatically download and install those gems, as well as any other gems needed by the gems that are listed. Before installing gems, it checks the versions of every gem to make sure that they are compatible, and can all be loaded at the same time. After the gems have been installed, Bundler can help you update some or all of them when new versions become available. Finally, it records the exact versions that have been installed, so that others can install the exact same gems.
 
@@ -23,18 +25,12 @@ See [bundler.io](http://bundler.io) for the full documentation.
 
 For help with common problems, see [ISSUES](https://github.com/bundler/bundler/blob/master/ISSUES.md).
 
-### Contributing
-
-If you'd like to contribute to Bundler, that's awesome, and we <3 you. There's a guide to contributing to Bundler (both code and general help) over in [DEVELOPMENT](https://github.com/bundler/bundler/blob/master/DEVELOPMENT.md)
-
-The `master` branch contains our current progress towards version 1.5. Versions 1.0-1.3 each have their own stable branches. Please submit bugfixes as pull requests to the stable branch for the version you would like to fix.
-
-### Core Team
-
-The Bundler core team consists of André Arko ([@indirect](http://github.com/indirect)), Terence Lee ([@hone](http://github.com/hone)), and Jessica Lynn Suttles ([@jlsuttles](http://github.com/jlsuttles)), with support and advice from original Bundler author Yehuda Katz ([@wycats](http://github.com/wycats)).
-
 ### Other questions
 
 To see what has changed in recent versions of Bundler, see the [CHANGELOG](https://github.com/bundler/bundler/blob/master/CHANGELOG.md).
 
 Feel free to chat with the Bundler core team (and many other users) on IRC in the  [#bundler](irc://irc.freenode.net/bundler) channel on Freenode, or via email on the [Bundler mailing list](http://groups.google.com/group/ruby-bundler).
+
+### Contributing
+
+If you'd like to contribute to Bundler, that's awesome, and we <3 you. There's a guide to contributing to Bundler (both code and general help) over in [DEVELOPMENT](https://github.com/bundler/bundler/blob/master/DEVELOPMENT.md)

data/Rakefile

@@ -1,10 +1,10 @@
 # -*- encoding: utf-8 -*-
 $:.unshift File.expand_path("../lib", __FILE__)
-require 'rubygems'
 require 'shellwords'
 require 'benchmark'
 
 RUBYGEMS_REPO = File.expand_path("tmp/rubygems")
+BUNDLER_SPEC = Gem::Specification.load("bundler.gemspec")
 
 def safe_task(&block)
   yield
@@ -30,8 +30,7 @@ end
 namespace :spec do
   desc "Ensure spec dependencies are installed"
   task :deps do
-    spec = Gem::Specification.load("bundler.gemspec")
-    deps = Hash[spec.development_dependencies.map do |d|
+    deps = Hash[BUNDLER_SPEC.development_dependencies.map do |d|
       [d.name, d.requirement.to_s]
     end]
 
@@ -65,7 +64,7 @@ namespace :spec do
         # https://github.com/rubygems/rubygems/issues/784
         sh "gem update --system 2.1.11"
       else
-        # Downgrade Rubygems so RSpec 3 can be instaled
+        # Downgrade Rubygems so RSpec 3 can be installed
         # https://github.com/rubygems/rubygems/issues/813
         sh "gem update --system 2.2.0"
       end
@@ -76,13 +75,12 @@ namespace :spec do
 end
 
 begin
+  rspec = BUNDLER_SPEC.development_dependencies.find{|d| d.name == "rspec" }
+  gem 'rspec', rspec.requirement.to_s
   require 'rspec/core/rake_task'
 
   desc "Run specs"
-  RSpec::Core::RakeTask.new do |t|
-    t.rspec_opts = %w(--format documentation --color)
-    t.ruby_opts  = %w(-w)
-  end
+  RSpec::Core::RakeTask.new
   task :spec => "man:build"
 
   namespace :spec do
@@ -114,7 +112,7 @@ begin
       rubyopt = ENV["RUBYOPT"]
       # When editing this list, also edit .travis.yml!
       branches = %w(master 2.2)
-      releases = %w(v1.3.6 v1.3.7 v1.4.2 v1.5.3 v1.6.2 v1.7.2 v1.8.29 v2.0.14 v2.1.11 v2.2.2)
+      releases = %w(v1.3.6 v1.3.7 v1.4.2 v1.5.3 v1.6.2 v1.7.2 v1.8.29 v2.0.14 v2.1.11 v2.2.2 v2.4.4)
       (branches + releases).each do |rg|
         desc "Run specs with Rubygems #{rg}"
         RSpec::Core::RakeTask.new(rg) do |t|
@@ -160,7 +158,9 @@ begin
       end
 
       task "setup_co" do
-        ENV["RUBYOPT"] = "-I#{File.expand_path ENV['RG']} #{rubyopt}"
+        rg = File.expand_path ENV['RG']
+        puts "Running specs against Rubygems in #{rg}..."
+        ENV["RUBYOPT"] = "-I#{rg} #{rubyopt}"
       end
 
       task "co" => "setup_co"

data/bin/bundle

@@ -6,7 +6,7 @@ Signal.trap("INT") { exit 1 }
 require 'bundler'
 # Check if an older version of bundler is installed
 $LOAD_PATH.each do |path|
-  if path =~ %r'/bundler-0.(\d+)' && $1.to_i < 9
+  if path =~ %r'/bundler-0\.(\d+)' && $1.to_i < 9
     err = "Looks like you have a version of bundler that's older than 0.9.\n"
     err << "Please remove your old versions.\n"
     err << "An easy way to do this is by running `gem cleanup bundler`."