Invalid gemspec error when running tests using rake #71

Closed
josh-m-sharpe opened this Issue Mar 9, 2012 · 7 comments

Comments

Projects
None yet
3 participants
@josh-m-sharpe

Can't get the test suite running. bundle installs stuff, but then rake does this:

$ rake
Invalid gemspec in [/Users/jsharpe/.rvm/gems/ree-1.8.7-2012.01/specifications/hanna-nouveau-0.2.4.gemspec]: Illformed requirement ["#YAML::Syck::DefaultKey:0x1121775b0 3.0.25"]
Invalid gemspec in [/Users/jsharpe/.rvm/gems/ree-1.8.7-2012.01/specifications/hanna-nouveau-0.2.4.gemspec]: Illformed requirement ["#YAML::Syck::DefaultKey:0x1121775b0 3.0.25"]
Could not find hanna-nouveau-0.2.4 in any of the sources
Run bundle install to install missing gems.

floehopper added a commit that referenced this issue Mar 9, 2012

Remove hannah-noveau as a dependency.
The gemspec for this gem always seems to be invalid and caused #71.
@floehopper

This comment has been minimized.

Show comment Hide comment
@floehopper

floehopper Mar 9, 2012

Owner

Sorry about that. Some rubygems weirdness with that hanna-noveau gem. I've removed it from the dependencies in 5753a8a, so if you git pull and do another bundle install all should be well, although you may need to delete the offending gemspec if you get warnings when running the tests.

Owner

floehopper commented Mar 9, 2012

Sorry about that. Some rubygems weirdness with that hanna-noveau gem. I've removed it from the dependencies in 5753a8a, so if you git pull and do another bundle install all should be well, although you may need to delete the offending gemspec if you get warnings when running the tests.

@cairo140

This comment has been minimized.

Show comment Hide comment
@cairo140

cairo140 Mar 9, 2012

Contributor

For the curious, this is the classic rubygems.org Syck issue: http://blog.rubygems.org/2011/08/31/shaving-the-yaml-yak.html

Upgrade to 1.8.16 and delete your old specification files and everything should work.

Contributor

cairo140 commented Mar 9, 2012

For the curious, this is the classic rubygems.org Syck issue: http://blog.rubygems.org/2011/08/31/shaving-the-yaml-yak.html

Upgrade to 1.8.16 and delete your old specification files and everything should work.

@floehopper

This comment has been minimized.

Show comment Hide comment
@floehopper

floehopper Mar 10, 2012

Owner

@crankharder can you tell us whether this fixed your problem and if it did can you close this issue? Thanks.

Owner

floehopper commented Mar 10, 2012

@crankharder can you tell us whether this fixed your problem and if it did can you close this issue? Thanks.

@josh-m-sharpe

This comment has been minimized.

Show comment Hide comment
@josh-m-sharpe

josh-m-sharpe Mar 10, 2012

bundle works now, but there are test failures on master

On Sat, Mar 10, 2012 at 4:55 AM, James Mead <
reply@reply.github.com

wrote:

@crankharder can you tell us whether this fixed your problem and if it did
can you close this issue? Thanks.


Reply to this email directly or view it on GitHub:
https://github.com/floehopper/mocha/issues/71#issuecomment-4430000

bundle works now, but there are test failures on master

On Sat, Mar 10, 2012 at 4:55 AM, James Mead <
reply@reply.github.com

wrote:

@crankharder can you tell us whether this fixed your problem and if it did
can you close this issue? Thanks.


Reply to this email directly or view it on GitHub:
https://github.com/floehopper/mocha/issues/71#issuecomment-4430000

@floehopper

This comment has been minimized.

Show comment Hide comment
@floehopper

floehopper Mar 12, 2012

Owner

Are those the 6 tests that are known to fail on Ruby >= v1.9.2? i.e. the ones reported in #41? If this is the case and you are happy that the original problem described in this issue has been fixed, can you close it?

Owner

floehopper commented Mar 12, 2012

Are those the 6 tests that are known to fail on Ruby >= v1.9.2? i.e. the ones reported in #41? If this is the case and you are happy that the original problem described in this issue has been fixed, can you close it?

@floehopper

This comment has been minimized.

Show comment Hide comment
@floehopper

floehopper Apr 16, 2012

Owner

@crankharder your original issue is solved and #41 is now closed, so I'm closing this issue. Please re-open if you disagree and explain why. Thanks, James.

Owner

floehopper commented Apr 16, 2012

@crankharder your original issue is solved and #41 is now closed, so I'm closing this issue. Please re-open if you disagree and explain why. Thanks, James.

@floehopper floehopper closed this Apr 16, 2012

@floehopper

This comment has been minimized.

Show comment Hide comment
@floehopper

floehopper Apr 21, 2012

Owner

I hope you don't mind, but I've renamed this issue to better reflect the original problem.

Owner

floehopper commented Apr 21, 2012

I hope you don't mind, but I've renamed this issue to better reflect the original problem.

@ghost ghost assigned floehopper Apr 21, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment