Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#67086 - [asciidoc] Broken symlink of asciidoc-graphviz-sample.txt example

Attached to Project: Community Packages
Opened by drws (drws) - Monday, 22 June 2020, 21:12 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 24 September 2020, 14:30 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Levente Polyak (anthraxx)
Eli Schwartz (eschwartz)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The following symlink in the latest asciidoc:
/usr/share/doc/asciidoc/examples/website/asciidoc-graphviz-sample.txt

Points to a non-existent file "../../filters/graphviz/asciidoc-graphviz-sample.txt".
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Thursday, 24 September 2020, 14:30 GMT
Reason for closing:  Fixed
Additional comments about closing:  We now package 9.x
Comment by drws (drws) - Monday, 22 June 2020, 21:15 GMT
Also forgot to mention that the symlinked file is not to be found anywhere. This example was probably removed, but the link remained in the package.
Comment by Eli Schwartz (eschwartz) - Monday, 22 June 2020, 21:43 GMT
https://github.com/asciidoc/asciidoc/blob/master/examples/website/asciidoc-graphviz-sample.txt

It symlinks to https://github.com/asciidoc/asciidoc/blob/master/filters/graphviz/asciidoc-graphviz-sample.txt and is installed by the upstream build system, inconsistently; I'd normally suggest you ask upstream why this is the case, but they're basically ready to sunset asciidoc 8.x in favor of the asciidoc-py3 9.x repository, which is ported to python3 and has various improvements including https://github.com/asciidoc/asciidoc-py3/pull/102 which fixes this exact issue.
Comment by drws (drws) - Monday, 22 June 2020, 22:14 GMT
Thank you for this info!

Loading...