search

hammackj / risu

Risu is Nessus parser, that converts the generated reports into a ActiveRecord database, this allows for easy report generation and vulnerability verification.
http://hammackj.github.io/risu
MIT License
63 stars 20 forks source link

Invalid Gemspec #40

Closed mlpotgieter closed 13 years ago

mlpotgieter commented 13 years ago

I had an issue with --create-config which was fixed, but when I tried to update I seemed to have broken things. What is the best way to re-install risu? I tried uninstalling after the update and reinstalling, but keep getting this error now.

Invalid gemspec in [/opt/local/lib/ruby/gems/1.8/specifications/risu-1.4.7.gemspec]: Illformed requirement ["#YAML::Syck::DefaultKey:0x105eecba8 2.5.0"]

I am at the point where I want to re-install rubygems but surly there is a better way to just clear out the old risu and start afresh? Apologies if this is more rubygems related than risu related.

mlpotgieter commented 13 years ago

Right... I'm no rubygems guy so that line looked daunting until if vi'ed the file. Changed it to s.add_development_dependency(%q, [">= 2.5.0"]) and it works.

hammackj commented 13 years ago

Looking into this will have a fix as soon as I can.

Sent from my Phone

On Aug 19, 2011, at 9:17 AM, mlpotgieter reply@reply.github.com wrote:

I had an issue with --create-config which was fixed, but when I tried to update I seemed to have broken things. What is the best way to re-install risu? I tried uninstalling after the update and reinstalling, but keep getting this error now.

Invalid gemspec in [/opt/local/lib/ruby/gems/1.8/specifications/risu-1.4.7.gemspec]: Illformed requirement ["#YAML::Syck::DefaultKey:0x105eecba8 2.5.0"]

I am at the point where I want to re-install rubygems but surly there is a better way to just clear out the old risu and start afresh? Apologies if this is more rubygems related than risu related.

Reply to this email directly or view it on GitHub: https://github.com/hammackj/risu/issues/40

hammackj commented 13 years ago

This problem seems to be wide spread in other gems also(based on googling). I am trying to find the cause and fix, I should have a patch for this and the other issue by Monday.

hammackj commented 13 years ago

I think I have this problem fixed. Rubygem changed a field. This fix will be in v1.4.8. I will try to release it by Monday.