From: David Sterba <dsterba@suse.cz>
To: Adam Borowski <kilobyte@angband.pl>
Cc: linux-btrfs@vger.kernel.org, David Sterba <dsterba@suse.com>
Subject: Re: docbook45 is gone
Date: Tue, 3 Sep 2019 17:34:29 +0200 [thread overview]
Message-ID: <20190903153429.GD2752@twin.jikos.cz> (raw)
In-Reply-To: <20190903081704.GA6277@angband.pl>
On Tue, Sep 03, 2019 at 10:17:04AM +0200, Adam Borowski wrote:
> I'm afraid that asciidoctor 2.0 dropped support for docbook45. The
> explanation given is here:
> https://github.com/asciidoctor/asciidoctor/issues/3005
>
> This makes btrfs-progs fail to build unless docs are off, with:
> asciidoctor: FAILED: missing converter for backend 'docbook45'. Processing aborted.
>
> Naively bumping the backend to docbook5 makes the output fail to pass
> validation.
As a workaround you can do
XMLTO_EXTRA += --skip-validation
it builds and the result looks correct from the few samples I tried.
Proper conversion to docbook5 will need to happen anyway, I'll open an
issue for 5.3 target. Thanks for the report.
prev parent reply other threads:[~2019-09-03 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 8:17 docbook45 is gone Adam Borowski
2019-09-03 10:54 ` Holger Hoffstätte
2019-09-03 15:34 ` David Sterba [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190903153429.GD2752@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=dsterba@suse.com \
--cc=kilobyte@angband.pl \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).