Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using rspec-rails 3.0.0.beta1 generates a dependency resolution problem #56

Closed
christiannelson opened this issue Jan 27, 2014 · 7 comments
Labels
outdated Inactive - Outdated

Comments

@christiannelson
Copy link

Using rspec-rails 3.0.0.beta1 on a rails 4.1.0.beta1 application, running bundle update produces this output:

% bundle update
Updating git://github.com/elabs/pundit.git
Fetching gem metadata from https://rubygems.org/.......
Fetching additional metadata from https://rubygems.org/..
Resolving dependencies...
Bundler could not find compatible versions for gem "rspec-mocks":
  In Gemfile:
    fuubar (>= 0) ruby depends on
      rspec-mocks (= 2.0.0) ruby

    rspec-rails (~> 3.0.0.beta1) ruby depends on
      rspec-mocks (3.0.0.beta1)

Could not find gem 'chalofa_ruby-progressbar (~> 0.0.9) ruby', which is required by gem 'fuubar (>= 0) ruby', in any of the sources.

Switching the dependency declaration from gem 'fuubar' to gem 'fuubar', github: 'jeffkreeftmeijer/fuubar', then running bundle update produces:

% bundle update
Updating git://github.com/elabs/pundit.git
Updating git://github.com/jeffkreeftmeijer/fuubar.git
Fetching gem metadata from https://rubygems.org/.......
Fetching additional metadata from https://rubygems.org/..
Resolving dependencies...
Bundler could not find compatible versions for gem "rspec-mocks":
  In Gemfile:
    fuubar (>= 0) ruby depends on
      rspec-mocks (~> 2.14.0) ruby

    rspec-rails (~> 3.0.0.beta1) ruby depends on
      rspec-mocks (3.0.0.beta1)

a806825 looks like a fix for this. Seems like there are circumstances where fuubar still requests an older version of rspec-mocks.

/cc @twalpole @jfelchner

@jfelchner
Copy link
Collaborator

@christiannelson my guess is that this is an issue with your Gemfile. Can you gist both your Gemfile as well as your Gemfile.lock?

@christiannelson
Copy link
Author

Here you go: https://gist.github.com/anonymous/8662843 Thanks for helping out!

@jumichot
Copy link

I have exactly the same problem: https://gist.github.com/jumichot/f0d1cbf8aeb6b36c4aff

@jfelchner
Copy link
Collaborator

Guys, I just don't see where it's getting the rspec-mocks (= 2.0.0) ruby from. I mean I'd understand if it said rspec-mocks (>= 2.14.0) ruby.

Try this:

bundle open fuubar

Then change:

s.add_dependency              'rspec',              ['>= 2.14.0', '< 3.1.0']

to

s.add_dependency              'rspec',              ['>= 2.14.0', '<= 3.0.0.beta']

And see if that fixes the issue.

@christiannelson
Copy link
Author

I'm still seeing this but haven't had a chance to dive deeper. I do have a work around though:

  1. Comment out gem 'fuubar' in my Gemfile
  2. bundle update
  3. Uncomment gem 'fuubar'
  4. bundle

I agree it's pretty weird. I hope to have some time to delve deeper, but I don't know how soon it will be. Thanks again for your help on this odd issue.

@jfelchner
Copy link
Collaborator

This is a moot point now due to #60. I'll be moving RSpec 2.x functionality to the fuubar-legacy gem and fuubar will be RSpec 3.x only.

@github-actions
Copy link

This issue has been closed automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot added the outdated Inactive - Outdated label Dec 28, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
outdated Inactive - Outdated
Development

No branches or pull requests

3 participants