Hi Vit,
Vít Ondruch wrote:
Dne 24. 09. 19 v 17:47 Todd Zullinger napsal(a):
> These srpm's require asciidoctor or rubygems-asciidoctor:
>
> awesome
> booth
> hugo
> ipmctl
> js8call
> mod_auth_mellon
> nanomsg
> ndctl
> nng
> oidentd
> qpid-dispatch
> tuned
> usbguard
> weechat
> wiki2beamer
> wsjtx
Are you sure you have used correct query? Looking just for
rubygem-asciidoctor, this is an output of my query:
hugo-0:0.55.6-1.fc31.src
js8call-0:1.1.0-2.fc31.src
mod_auth_mellon-0:0.14.2-2.fc31.src
nanomsg-0:1.1.5-2.fc31.src
ndctl-0:66-1.fc31.src
nng-0:1.1.1-3.fc31.src
oidentd-0:2.4.0-1.fc32.src
qpid-dispatch-0:1.8.0-3.fc32.src
rubygem-asciidoctor-doc-0:1.5.6.1-6.fc30.noarch
rubygem-asciidoctor-pdf-0:1.5.0-0.10.alpha.18.fc31.noarch
rubygem-chake-0:0.17.1-3.fc31.src
rubygem-jekyll-asciidoc-0:3.0.0-1.fc32.noarch
rubygem-slim-0:3.0.9-4.fc31.src
rubygem-tilt-0:2.0.8-6.fc31.src
wiki2beamer-0:0.10.0-2.fc31.src
wsjtx-0:2.1.0-2.fc31.src
Ahh, I see. I missed that some of the rubygem's use
rubygem(asciidoctor) as the BuildRequires. That covers
rubygem-chake, rubygem-slim, and rubygem-tilt.
The rubygem-{asciidoctor-pdf,jekyll-asciidoc} packages don't
BuildRequire asciidoctor, so my search wouldn't have picked
them up. I only looked for BuildRequires. I'm sure others
use asciidoctor at run time, but I only intended to directly
bcc package owners who BuildRequire asciidoctor.
FWIW, the query I used was:
dnf repoquery -q --qf '%{name}' --archlist=src --releasever=rawhide \
--disablerepo='*' --enablerepo=rawhide-source \
--whatrequires asciidoctor --whatrequires rubygem-asciidoctor
I should have added --whatrequires 'rubygem(asciidoctor)' as
well. I've added those rubygem package owners to Bcc to let
them know asciidoctor-2.0.10 is coming soon. Thanks for
checking and pointing that out!
Also, we currently have just rubygem-asciidoctor-1.5.6,
because it seems that 1.5.8 has never been built ...
In any case, it's long out of date. :)
My personal interest in asciidoctor is as a replacement for
asciidoc with the git documentation. I've worked a little
upstream with git and asciidoctor and submitted some PRs for
the asciidoctor package. Recent work by a few other folks
in the git project has greatly improved the results when
using asciidoctor for git.
--
Todd