Hello,

I recently ported a new port, astro/kosmorro, which uses ronn to build
its man pages.

No problem on recent FreeBSD versions, but pkg-fallout reported an error
on 11.4 / i386:

ronn --roff manpage/kosmorro.1.md
     roff: manpage/kosmorro.1                         
/usr/local/lib/ruby/gems/2.7/gems/ronn-0.7.3/lib/ronn/document.rb:330:in 
`split': invalid byte sequence in US-ASCII (ArgumentError)
        from 
/usr/local/lib/ruby/gems/2.7/gems/ronn-0.7.3/lib/ronn/document.rb:330:in 
`markdown_filter_heading_anchors'
        from 
/usr/local/lib/ruby/gems/2.7/gems/ronn-0.7.3/lib/ronn/document.rb:299:in 
`process_markdown!'
        from 
/usr/local/lib/ruby/gems/2.7/gems/ronn-0.7.3/lib/ronn/document.rb:210:in 
`markdown'
        from 
/usr/local/lib/ruby/gems/2.7/gems/ronn-0.7.3/lib/ronn/document.rb:290:in 
`input_html'
        from 
/usr/local/lib/ruby/gems/2.7/gems/ronn-0.7.3/lib/ronn/document.rb:305:in 
`process_html!'
        from 
/usr/local/lib/ruby/gems/2.7/gems/ronn-0.7.3/lib/ronn/document.rb:215:in `html'
        from 
/usr/local/lib/ruby/gems/2.7/gems/ronn-0.7.3/lib/ronn/document.rb:251:in 
`to_html_fragment'
        from 
/usr/local/lib/ruby/gems/2.7/gems/ronn-0.7.3/lib/ronn/document.rb:227:in 
`to_roff'
        from 
/usr/local/lib/ruby/gems/2.7/gems/ronn-0.7.3/lib/ronn/document.rb:221:in 
`convert'
        from /usr/local/lib/ruby/gems/2.7/gems/ronn-0.7.3/bin/ronn:191:in 
`block (2 levels) in <top (required)>'
        from /usr/local/lib/ruby/gems/2.7/gems/ronn-0.7.3/bin/ronn:181:in `each'
        from /usr/local/lib/ruby/gems/2.7/gems/ronn-0.7.3/bin/ronn:181:in 
`block in <top (required)>'
        from /usr/local/lib/ruby/gems/2.7/gems/ronn-0.7.3/bin/ronn:167:in `each'
        from /usr/local/lib/ruby/gems/2.7/gems/ronn-0.7.3/bin/ronn:167:in `<top 
(required)>'
        from /usr/local/bin/ronn:23:in `load'
        from /usr/local/bin/ronn:23:in `<main>'

(Full log available at
<http://beefy10.nyi.freebsd.org/data/114i386-default/566741/logs/kosmorro-0.9.0.log>
)

Is there anything special to do for this platform?

Thanks.
-- 
Th. Thomas.

Attachment: signature.asc
Description: PGP signature

Reply via email to