problem with the yaml in the gem? #36

Closed
sp7777 opened this Issue Oct 4, 2011 · 1 comment

Projects

None yet

2 participants

@sp7777
sp7777 commented Oct 4, 2011

I'm using Rails 3.1 and just put acts_as_archive into my gemfile. Doing nothing else, I ran rake and get the following dump: It looks as though there is some invalid yaml in the gem. If I change my yaml parser to syck, it's ok (but syck is an old parser and should not be used).

rake --trace
rake aborted!
couldn't parse YAML at line 2 column 9
/blah/blah/ruby-1.9.2-p290/lib/ruby/1.9.1/psych.rb:148:in parse' /blah/blah/ruby-1.9.2-p290/lib/ruby/1.9.1/psych.rb:148:inparse_stream'
/blah/blah/ruby-1.9.2-p290/lib/ruby/1.9.1/psych.rb:119:in parse' /blah/blah/ruby-1.9.2-p290/lib/ruby/1.9.1/psych.rb:106:inload'
/blah/blah/ruby-1.9.2-p290@rails3/gems/acts_as_archive-0.4.0/lib/acts_as_archive/gems.rb:66:in block in gemset=' /blah/blah/ruby-1.9.2-p290@rails3/gems/acts_as_archive-0.4.0/lib/acts_as_archive/gems.rb:64:incollect'
/blah/blah/ruby-1.9.2-p290@rails3/gems/acts_as_archive-0.4.0/lib/acts_as_archive/gems.rb:64:in gemset=' /blah/blah/ruby-1.9.2-p290@rails3/gems/acts_as_archive-0.4.0/lib/acts_as_archive/gems.rb:37:inactivate'
/blah/blah/ruby-1.9.2-p290@rails3/gems/acts_as_archive-0.4.0/lib/acts_as_archive.rb:3:in <top (required)>' /blah/blah/ruby-1.9.2-p290@rails3/gems/bundler-1.0.18/lib/bundler/runtime.rb:68:inrequire'
/blah/blah/ruby-1.9.2-p290@rails3/gems/bundler-1.0.18/lib/bundler/runtime.rb:68:in block (2 levels) in require' /blah/blah/ruby-1.9.2-p290@rails3/gems/bundler-1.0.18/lib/bundler/runtime.rb:66:ineach'
/blah/blah/ruby-1.9.2-p290@rails3/gems/bundler-1.0.18/lib/bundler/runtime.rb:66:in block in require' /blah/blah/ruby-1.9.2-p290@rails3/gems/bundler-1.0.18/lib/bundler/runtime.rb:55:ineach'
/blah/blah/ruby-1.9.2-p290@rails3/gems/bundler-1.0.18/lib/bundler/runtime.rb:55:in require' /blah/blah/ruby-1.9.2-p290@rails3/gems/bundler-1.0.18/lib/bundler.rb:120:inrequire'

@sp7777 sp7777 closed this Oct 4, 2011
@dvdplm
dvdplm commented Oct 25, 2011

this is not fixed.

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