Skip to content
This repository has been archived by the owner on Jan 10, 2024. It is now read-only.

Unable to complete "bundle install" #78

Closed
zmoazeni opened this issue Oct 28, 2013 · 5 comments
Closed

Unable to complete "bundle install" #78

zmoazeni opened this issue Oct 28, 2013 · 5 comments

Comments

@zmoazeni
Copy link
Contributor

Is anyone else having this issue?

I'm seeing this issue with both v1.9.3 and v2.0.0 and bundler versions 1.3.5 and 1.4.0.rc.1.

ruby-2.0.0-p247@jasmine-rails ~/projects/jasmine-rails (master) ∴ bundle
Fetching gem metadata from http://rubygems.org/.........
Fetching gem metadata from http://rubygems.org/..
Resolving dependencies.........
Retrying source fetch due to error (2/3): Bundler could not find compatible versions for gem "mime-types":
  In Gemfile:
    jasmine-rails (>= 0) ruby depends on
      mime-types (~> 1.16) ruby

    poltergeist (>= 0) ruby depends on
      mime-types (2.0)

Bundler could not find compatible versions for gem "sprockets":
  In Gemfile:
    jasmine-rails (>= 0) ruby depends on
      sprockets (~> 2.0.0) ruby

    jasmine-rails (>= 0) ruby depends on
      sprockets (2.10.0)

Bundler could not find compatible versions for gem "sprockets-rails":
  In Gemfile:
    jasmine-rails (>= 0) ruby depends on
      sprockets-rails (~> 2.0.0) ruby

    jasmine-rails (>= 0) ruby depends on
      sprockets-rails (0.0.0)


Resolving dependencies......
Retrying source fetch due to error (3/3): Bundler could not find compatible versions for gem "mime-types":
  In Gemfile:
    jasmine-rails (>= 0) ruby depends on
      mime-types (~> 1.16) ruby

    poltergeist (>= 0) ruby depends on
      mime-types (2.0)

Bundler could not find compatible versions for gem "sprockets":
  In Gemfile:
    jasmine-rails (>= 0) ruby depends on
      sprockets (~> 2.0.0) ruby

    jasmine-rails (>= 0) ruby depends on
      sprockets (2.10.0)

Bundler could not find compatible versions for gem "sprockets-rails":
  In Gemfile:
    jasmine-rails (>= 0) ruby depends on
      sprockets-rails (~> 2.0.0) ruby

    jasmine-rails (>= 0) ruby depends on
      sprockets-rails (0.0.0)


Resolving dependencies......
Bundler could not find compatible versions for gem "mime-types":
  In Gemfile:
    jasmine-rails (>= 0) ruby depends on
      mime-types (~> 1.16) ruby

    poltergeist (>= 0) ruby depends on
      mime-types (2.0)

Bundler could not find compatible versions for gem "sprockets":
  In Gemfile:
    jasmine-rails (>= 0) ruby depends on
      sprockets (~> 2.0.0) ruby

    jasmine-rails (>= 0) ruby depends on
      sprockets (2.10.0)

Bundler could not find compatible versions for gem "sprockets-rails":
  In Gemfile:
    jasmine-rails (>= 0) ruby depends on
      sprockets-rails (~> 2.0.0) ruby

    jasmine-rails (>= 0) ruby depends on
      sprockets-rails (0.0.0)
@zmoazeni
Copy link
Contributor Author

A little more info. I'm on master as of f33e0a6 with a clean gemset and no .bundle folder.

@searls
Copy link
Member

searls commented Oct 29, 2013

Hey Zach, I don't spend much time with jasmine-rails these days. Would you be willing to pull the repo down and debug? I'm not aware of what changed to have broken t :-(

On Mon, Oct 28, 2013 at 4:09 PM, Zach Moazeni notifications@github.com
wrote:

A little more info. I'm on master as of f33e0a6 with a clean gemset and no .bundle folder.

Reply to this email directly or view it on GitHub:
#78 (comment)

@zmoazeni
Copy link
Contributor Author

One unconfirmed guess is that a newer version of poltergeist came out and is causing the conflict. Adding a version constraint may fix it.

I don't have time to check now, but hopefully will sometime today.

@searls
Copy link
Member

searls commented Oct 29, 2013

That was also my guess when I scanned your email

On Tue, Oct 29, 2013 at 8:15 AM, Zach Moazeni notifications@github.com
wrote:

One unconfirmed guess is that a newer version of poltergeist came out and is causing the conflict. Adding a version constraint may fix it.

I don't have time to check now, but hopefully will sometime today.

Reply to this email directly or view it on GitHub:
#78 (comment)

@zmoazeni
Copy link
Contributor Author

Closing now that #79 is submitted

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants