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

Invalid gemspec #3

Open
josegrad opened this issue Aug 7, 2012 · 4 comments
Open

Invalid gemspec #3

josegrad opened this issue Aug 7, 2012 · 4 comments

Comments

@josegrad
Copy link

josegrad commented Aug 7, 2012

Hi, I'm trying to use carmen-rails in one of my apps and I get the next error when starting the rails server.

Invalid gemspec in [/Users/elmaco/.rvm/gems/ruby-1.9.2-p0/specifications/carmen-1.0.0.beta2.gemspec]: Illformed requirement ["#Syck::DefaultKey:0x00000109445f70 2.6.1"]
Invalid gemspec in [/Users/elmaco/.rvm/gems/ruby-1.9.2-p0/specifications/carmen-1.0.0.beta2.gemspec]: Illformed requirement ["#Syck::DefaultKey:0x00000109445f70 2.6.1"]
Invalid gemspec in [/Users/elmaco/.rvm/gems/ruby-1.9.2-p0/specifications/carmen-1.0.0.beta2.gemspec]: Illformed requirement ["#Syck::DefaultKey:0x00000109445f70 2.6.1"]
Could not find carmen-1.0.0.beta2 in any of the sources

I added gem 'carmen-rails' to gemfile and bundle install shows:
Installing carmen (1.0.0.beta2)
Using carmen-rails (1.0.0.beta3)

Any hints?

Rails 3.2.3
Ruby ruby 1.9.2p0 (2010-08-18 revision 29036) [x86_64-darwin10.4.0]

@jim
Copy link
Owner

jim commented Aug 7, 2012

What version of Rubygems are you using?

@josegrad
Copy link
Author

josegrad commented Aug 7, 2012

1.6.2

@jim
Copy link
Owner

jim commented Aug 7, 2012

I think you need to update to Rubygems 1.8.x in order to fix this. You'll then need to manually delete the gemspec at /Users/elmaco/.rvm/gems/ruby-1.9.2-p0/specifications/carmen-1.0.0.beta2.gemspec and run bundle again.

This is related to how different versions of Rubygems deal with Yaml, and unfortunately there isn't a cleaner fix. The good news is updating Rubygems should prevent this from happening again.

@josegrad
Copy link
Author

josegrad commented Aug 7, 2012

Ok, thanks for the quick reply!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants