Dne 24. 09. 19 v 17:47 Todd Zullinger napsal(a): > Hi all, > > I'm planning to push asciidoctor-2.0.10 to rawhide in the > next few days. This is a major bump from our current 1.5.8, > but upstream has worked hard to fix regressions found since > the initial 2.0.0 release back in March. > > The 2.0.0 release notes can be found at: > > https://github.com/asciidoctor/asciidoctor/releases/tag/v2.0.0 > > The subsequent minor release are covered at: > > https://github.com/asciidoctor/asciidoctor/releases > > Most packages shouldn't really notice the change. But there > are likely some which have relied on things which worked in > 1.5.8 that may have been changed. One notable change is the > removal of docbook 4.5 support (in favor of docbook 5). > This can impact packages which use asciidoctor to generate > intermediate xml that is then fed to xmlto. > > (The upstream git project is one such project, though in git > we still default to asciidoc for now. And patches are > landing upstream to support building with asciidoctor 2.x > and docbook 5.) > > 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 Also, we currently have just rubygem-asciidoctor-1.5.6, because it seems that 1.5.8 has never been built ... Vít > I've included those package owners via Bcc:. > > If anyone needs me to hold off for a bit, please speak up. > We do want to take this action soon though, so we can ensure > any kinks get worked out well before we branch for f32. > > There's also an outstanding FTBFS bug for the current 1.5.8 > package which this move to 2.0.10 conveniently fixes. > _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
