When building rspec-core the build fails with a long stack trace (attached). Reproducible: Always Steps to Reproduce: 1. emerge -av1 \=rspec-core-2.13.0 2. build failure 3. Actual Results: Build failure. Expected Results: Successful build.
Created attachment 345032 [details] emerge --info '=dev-ruby/rspec-core-2.13.0'
Created attachment 345034 [details] emerge -pqv '=dev-ruby/rspec-core-2.13.0'
Created attachment 345036 [details] emerge --info
Created attachment 345038 [details] Build Log
Created attachment 345040 [details] Ebuild Environment
This is a bug in maruku that should probably be reported upstream. Any of the other markdown providers (bluecloth, kramdown, rdiscount) work fine.
This is working in rspec-core-2.13.1. Should we close this bug and mark 2.13.0 as never stable?
(In reply to Alex Brandt from comment #7) > This is working in rspec-core-2.13.1. Should we close this bug and mark > 2.13.0 as never stable? Sounds good to me. I've removed 2.13.0 from the tree.