-
Notifications
You must be signed in to change notification settings - Fork 94
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
Invalid gemspec #61
Comments
It seems the problem of old version rubygems. Best regards. |
Thanks for the quick response! Unfortunately, "gem update --system" yields: "Latest version currently installed. Aborting" (and repeats the invalid gemspec errors). |
Hmm... |
Anyone have any thoughts on this? Just can't get rid of it . . . |
Manually edit /usr/lib64/ruby/gems/1.9.1/specifications/earthquake-0.8.1.gemspec
I don't think this is a smart way, but it worked for me. |
Doesn't work for me. In fact, no amount of screwing around with that file does anything (including erasing it). Can someone at least explain the nature of the problem? I'm not familiar enough with rubygems to really be able to figure out why it's failing. I haven't been able to use earthquake in months. |
possible workaround: |
Finally! That seems to have fixed it. Thank you so much, irohiroki (and everyone who replied). But, um, what did I just do? ;) |
well, ruby has two yaml engines, syck (legacy) and psych (brand new). |
Great!!! |
Love, love, love earthquake. But can't run it anymore, because I get:
Invalid gemspec in [/usr/lib64/ruby/gems/1.9.1/specifications/earthquake-0.8.1.gemspec]: Illformed requirement ["#Syck::DefaultKey:0x0000000251a278 0.4.3"]
when I try to install it.
In fact, that error appears even when earthquake is not actually installed (when running anything having to do with gems, irb etc.)
Any thoughts on what might be causing this? Is there a way to clear out the gemspec and start over?
The text was updated successfully, but these errors were encountered: