On 14.0-CURRENT, ports tree as of ae8e32b08e33bac7aec0f14f28e45d53dee6f565 I have installed docbookrx from the ports tree having ruby 3.1 installed, but it fails to load the gem: > docbookrx build.xml <internal:/usr/local/lib/ruby/site_ruby/3.1/rubygems/core_ext/kernel_require.rb>:85:in `require': cannot load such file -- docbookrx (LoadError) from <internal:/usr/local/lib/ruby/site_ruby/3.1/rubygems/core_ext/kernel_require.rb>:85:in `require' from /usr/local/lib/ruby/gems/3.1/gems/docbookrx-1.0.0.dev/bin/docbookrx:6:in `<top (required)>' from /usr/local/bin/docbookrx:25:in `load' from /usr/local/bin/docbookrx:25:in `<main>' It seems to be that a whole "lib" directory did not get staged and installed: > find /usr/local/lib/ruby/gems/3.1/gems/docbookrx-1.0.0.dev/ /usr/local/lib/ruby/gems/3.1/gems/docbookrx-1.0.0.dev/ /usr/local/lib/ruby/gems/3.1/gems/docbookrx-1.0.0.dev/bin /usr/local/lib/ruby/gems/3.1/gems/docbookrx-1.0.0.dev/bin/docbookrx /usr/local/lib/ruby/gems/3.1/gems/docbookrx-1.0.0.dev/LICENSE /usr/local/lib/ruby/gems/3.1/gems/docbookrx-1.0.0.dev/README.adoc
docbookrx has not been under development since 2020 and mostly 2018. And it officially does not support ruby after 2.7. So it's better to look for alternative. In the meantime I will mark this as BROKEN.
Created attachment 243445 [details] 0001-fix-cannot-load-such-file-docbookrx-LoadError.patch Patch to fix the installation bug
Created attachment 243446 [details] 0001-fix-cannot-load-such-file-docbookrx-LoadError.patch Patch to fix the installation bug
It turned out to be a normal bug, nothing related to the code being old and unmaintained. I am actually happy that I could restore an old book source written in DocBook, build it and try to covert it to asciidoc only using tools available easily in FreeBSD ports!
Created attachment 246569 [details] Update port to the main branch as of 06f4336c6cea1626722f12bbb2659e48d5ab4581 Several updates have been committed to the GitHub repository, including the fix for this issue, so let's just switch the repository to the upstream one and update the port. I have tested it with the DocBook I've had to convert when I encountered this issue. https://github.com/asciidoctor/docbookrx/commit/06f4336c6cea1626722f12bbb2659e48d5ab4581