Closed pupeno closed 12 years ago
If I comment out this line:
gem "omniauth-facebook"
then bundler doesn't get stuck.
omniauth-facebook depends on omniauth-oauth2 which depends on oauth2 ~> 0.6.0 while my version of sorcery depends on oauth2 ~> 0.7.1. Obviously dependencies can't be met.
Confirmed that changing my copy of sorcery to depend on oauth2 ~> 0.6.0 workarrounded the problem.
Great, thanks for reporting back. The reason Bundler is getting stuck is likely that it was trying every single combination of sorcery and omniauth-facebook, to see if there was any previous version that would allow your Gemfile to resolve.
Should at some point give up? I left it running for 10 minutes or so and nothing happened.
It's a complicated and hard problem. I have heard of successful resolves that take 30 minutes to complete in the past, so I'm wary of instituting a hard timeout. We probably should at some point, with a flag to override the timeout, though, to make the experience friendlier.
On Jun 13, 2012, at 9:53 AM, J. Pablo Fernández wrote:
Should at some point give up? I left it running for 10 minutes or so and nothing happened.
Reply to this email directly or view it on GitHub: https://github.com/carlhuda/bundler/issues/1984#issuecomment-6306582
30 minutes? wow. Maybe outputting something to let us know what's going on would be useful. Specially if you can output something like "trying to figure out dependencies among sorcery and facebook-omniauth" or something like that.
Hello,
I forked the gem sorcery for it to depend on oauth2 0.7.1 instead of oauth2 0.5.2. I then changed the line from
to
If I have a pristine copy of sorcery, everything works fine, but when I have my own modifications that depend on oauth2 0.7.1, then bundler gets stuck. I also depend on these related gems:
The output from bundler is: