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

rspec 2.6.0.rc3 gemspec causes exceptions in rubygems 1.3.7 #358

Closed
indirect opened this issue May 1, 2011 · 2 comments
Closed

rspec 2.6.0.rc3 gemspec causes exceptions in rubygems 1.3.7 #358

indirect opened this issue May 1, 2011 · 2 comments

Comments

@indirect
Copy link

indirect commented May 1, 2011

Hello!

The gemspec for the 2.6.0.rc3 gem has invalid data in it. Specifically, the dependency lines that look like this:

s.add_runtime_dependency(%q<rspec-core>, ["#<YAML::Syck::DefaultKey:0x1069613b8> 2.6.0.rc3"])

When it tries to do stuff with that gemspec, Rubygems 1.3.7 just explodes. As a result, it is impossible to install 2.6.0.rc3 using that Rubygems version:

$ gem install rspec --pre
ERROR:  While executing gem ... (NoMethodError)
   undefined method `call' for nil:NilClass

It is also impossible to run bundle install against any Gemfile that requires any rspec prerelease version, because Bundler will evaluate the gemspec and call some Rubygems methods that result in an exception due to the invalid data.

Please fix the gemspec so that rspec will still work with Rubygems 1.3.7! Thanks.

@dchelimsky
Copy link
Contributor

I just released 2.6.0.rc4, which fixes the gemspec problem if you specify 2.6.0.rc4 (and not just --pre). I need to leave 2.6.0.rc3 unyanked for at least enough time for @tenderlove to take a look at ruby/psych#13, so please bear with me and use the --pre for the moment, after which I'll yank 2.6.0.rc3. Leaving this open until that time.

@dchelimsky
Copy link
Contributor

Closing this now that rc3 is yanked.

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