title: Is there a way to force bundler to accept a particular version of a gem?
body: <p>I have a rails project where certain third party dependencies insist on a certain version of another third party library (using ~> ) When I try to do a bundle install, I get the following:</p>
  
  <pre><code>Bundler could not find compatible versions for gem "faraday":
    In snapshot (Gemfile.lock):
      faraday (= 0.9.2)
  
    In Gemfile:
      linkedin-v2 (&gt;= 0.1.7) was resolved to 0.1.7, which depends on
        faraday (~&gt; 0.11)
  
      twitter (~&gt; 5.0) was resolved to 5.17.0, which depends on
        faraday (~&gt; 0.9.0)
  
  Running `bundle update` will rebuild your snapshot from scratch, using only
  the gems in your Gemfile, which may resolve the conflict.
  </code></pre>
  
  <p>Applicable segments from the Gemfile:</p>
  
  <pre><code>...
  gem 'linkedin-v2', '&gt;= 0.1.7'
  ...
  gem 'twitter', '~&gt; 5.0'
  ...
  </code></pre>
  
  <p>In this case, I am almost certain that there is no incompatibility in the third party library, and after testing I could use faraday 0.11 without issue. Is there a directive I can use in the Gemfile way to tell bundler just to accept a certain version of a gem, perhaps while printing out a warning?</p>
  
  <p>I can fork the third party project on github (In this case the 'twitter' project) and then change the version number of faraday in its Gemfile, and then reference this forked project in my Gemfile - but this seems like a really ugly and overly complex hack. (i.e: It introduces the issue of keeping the forked project up to date.)</p>