-
-
Notifications
You must be signed in to change notification settings - Fork 975
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Apparently upgrading rubygems to version 1.8.10 didn't fix the problem. Building the gems again using Ruby 1.8.7.
- Loading branch information
Showing
7 changed files
with
7 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
c0b6f06
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
c0b6f06
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Problem persists also after upgrading rubygems to 1.8.10
c0b6f06
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apparently related this error appears to be a problem within bundler: rubygems/bundler#1235
I'm cleaning up the cache bundler creates but still no dice. Will double check again; for the moment the gem is not installable on my system.
c0b6f06
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wiped my entire gemset, switched back to gem "omniauth", "~> 0.2.6" in Gemfile, no go. I'm at loss now. If you need more info let me know.
c0b6f06
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm about to get on a long flight. Hailing @tenderlove, @indirect, and @hone to assist.
This is a serious bug in bundler 1.1. You can avoid the problem on your machine by downgrading to bundler 1.0, but this doesn't help people trying to deploy to the Heroku Cedar stack or similar. Let's get this fixed and push a new bundler 1.1 pre ASAP.
Thanks all!
c0b6f06
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not a bug in Bundler 1.1. Sorry. :( This is a bug in the gemspec for Omniauth 0.3.0.rc2. It's an invalid gemspec, and it cannot be evaluated or installed by Rubygems 1.0 through 1.8.9. As a result of the gemspec being invalid, that version of the gem needs to be yanked. Please yank it, and the problem will be solved (since rc3 has a valid and working gemspec).
c0b6f06
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@indirect The problem persist even after the gem has been yanked. That's why I think it's a bundler bug.
c0b6f06
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can verify that omniauth-0.3.0.rc2 has been yanked at http://rubygems.org/gems/omniauth/versions
Sounds like a caching bug in bundler 1.1. Downgrading to 1.0 fixes the problem but the problem re-appears when I go back to using bundler 1.1.
c0b6f06
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just yanking the master omniauth gem doesn't fix the problem. All of the rc2 gems need to be yanked, including (at least) oa-core: http://rubygems.org/gems/oa-core/versions.
c0b6f06
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
c0b6f06
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's fine now, thanks all :)