Date: Wed, 13 Sep 2023 02:01:33 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 273748] textproc/rubygem-asciidoctor-plantuml Message-ID: <bug-273748-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273748 Bug ID: 273748 Summary: textproc/rubygem-asciidoctor-plantuml Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: sunpoet@FreeBSD.org Reporter: bsdunix44@gmail.com Assignee: sunpoet@FreeBSD.org Flags: maintainer-feedback?(sunpoet@FreeBSD.org) Created attachment 244798 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D244798&action= =3Dedit Image of the debug info Java throws when using the asciidoctor-plantuml rub= ygem to render the above plantuml Trying to render PlantUML in an asciidoc document using asciidoctor-plantuml fails in almost every block of plantuml I try to render. Specifically, for a simple example, the following block causes it to fail w= ith the attached image (debug info), using the following command line: asciidoc= tor -b html5 -o index.html -r asciidoctor-diagram example.adoc -w [#techwriting-UI,reftext=3DUI] =3D=3D User Interface =3D=3D=3D The login window =3D=3D=3D=3D _See Example 1. Login Window._ =3D=3D=3D=3D [plantuml, format=3Dsvg] .... @startsalt title Example 1, Login Window {+ Login | "MyName " Password | "**** " [Cancel] | [ OK ] } @endsalt .... What I've noted is the following in trying to figure this out: 1) The above block renders as it should on the https://plantuml.com/ main p= age. They have an online demo server you can paste uml into and it renders it on= the fly. So the syntax is correct. 2) Our port of asciidoctor-plantuml is 0.1.1 released may 1st 2022. The lat= est release of asciidoctor-plantuml is v1.2023.10 released July 23rd of this ye= ar. So the rubygem in ports is over a year out of date. But when I checked the rubygem homepage our port is the latest version of the rubygem. I think it's the upstream rubygem maintainer that needs to roll a new release. If that's= the case then you can close this PR and I will just poke the rubygem maintainer= .=20 3) Our asciidoctor-diagram port is v2.0.0 released December 15th 2019. The current asciidoctor-diagram version is v2.2.12 released 3 days ago. That ma= kes our asciidoctor-diagram over 3 years old. Granted I should file a PR to see= if that can be updated but I am noting it here as it is involved in the render= ing of plantuml diagrams. 4) I'm pretty sure it's the asciidoctor-plantuml port and not the asciidoctor-diagram port but I am not 100% certain, that is at issue here.= =20 Whatever is breaking, is making it impossible to render plantuml in asciido= c. Also, what is the deal with: rubygem-asciidoctor-plantuml-0.1.1 Asciidoctor PlantUML extension rubygem-asciidoctor-plantuml00-0.0.16 Asciidoctor PlantUML extension There is no difference in the description. Other than the different version formatting could we possibly update the descriptions to make it easier to understand the difference? Do we need two versions? I don't understand why rubygem-asciidoctor-plantuml00-0.0.16 is in ports. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273748-7788>