search

guillermo / rake-hooks

Rake hooks let you add callbacks to rake tasks.
MIT License
70 stars 21 forks source link

From bundler: "Unfortunately, the gem rake-hooks (1) has an invalid gemspec." #10

Closed mattscilipoti closed 12 years ago

mattscilipoti commented 12 years ago

When I attempt to bundle update rails, I receive this error: "Unfortunately, the gem rake-hooks (1) has an invalid gemspec. As a result, Bundler cannot install this Gemfile. Please ask the gem author to yank the bad version to fix this issue. For more information, see http://bit.ly/syck-defaultkey."

I checked that page and I didn't see how that related to this project. I have the latest rubygems (1.8.19). Any ideas?

kaineer commented 12 years ago

Same here, running bundle install in my project.

dayyan commented 12 years ago

I solved this problem by using an earlier verson of bundler, specifically 1.0.21.

soulcutter commented 12 years ago

You can also fix this by doing "bundle install --full-index" however the offending version(s) should really be pulled from rubygems, because this problem isn't going to go away otherwise.

http://help.rubygems.org/kb/gemcutter/removing-a-published-rubygem

Side-note: this --full-index workaround doesn't work with bundle update.

szymon-jez commented 12 years ago

@soulcutter thanks + 1 up vote for the idea to remove the published offending version(s)

stanislaw commented 12 years ago

The same here:

RUBYGEMS: 1.8.19 RUBY - 1.9.3-p125

mattscilipoti commented 12 years ago

My investigation indicates that version 1 of rake-hooks is causing the issue. I didn't realize, until I was debugging, that the "1" in the error message "rake-hooks (1)" was a version number. The lack of a ".0", as in "1.0", threw me off.

It does seem kind of strange that version "1" is affecting us even if we are specifying version 1.2.3 OR installing a local package. But... the Rubygems guys are recommending we yank the offending version from rubygems.org.

Please yank version "1". http://help.rubygems.org/kb/gemcutter/removing-a-published-rubygem

guillermo commented 12 years ago

WOW!!! Seems like a totally wired bug !

I just yank version 1. Can you please try again? I was not able to reproduce this problem.

mattscilipoti commented 12 years ago

Thanks! That seems to have done it. Even my Travis CI is passing.

"I was unable to reproduce this problem": Interesting. It is causing your travis builds to break too: http://travis-ci.org/#!/guillermo/rake-hooks/jobs/1100996. These should pass after your next commit, even if you simply change your readme.