Created attachment 23132 [details] Build log Running ./configure --enable-docbook-docs && make results in a failing build. Complete build log attached. There is also a Debian bug filed at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516253
Yeah, I've noticed this too. Kinda strange since it used to work. Any ideas? Thanks.
(In reply to comment #1) > Yeah, I've noticed this too. Kinda strange since it used to work. Any ideas? I'm not an expert in XML/XSLT, so I don't have any advice without looking into it first myself, sorry.
xmlto used to validate XML documents via `xmllint >/dev/null --xinclude --postvalid' However, this does not resolve entities and thus may fail in certain situations, where we have a valid XML document. So this is a bug. It was fixed in Debian (and will be fixed in the upcoming 0.0.22 release) by adding the --noent switch for xmllint, so it resolves the entities too. What's happening here is, that the resulting document with resolved entities does not validate and xmllint also clearly shows you, where your DocBook is not valid. Typical mistakes done are: <listitem>text</listitem> must be <listitem><para>text</para></listitem> (or <simpara> instead of <para>) <variablelist role="params"/> is not valid, as <variablelist> must have a <varlistentry> child (it's not an empty element) <refsect1> contents must not be mixed <para>|<variablelist> and <refsect2> - it can only be *first* content (like <para> or <variablelist>) and then *only* <refsect2>, but not <para> between the <refsect2> Fix those issues to get a valid DocBook XML file. You can test the result with: xmllint --noout --noent --valid As long as xmllint complains, your XML is not valid. I would further suggest, that you add the following code to your configure.ac: AC_ARG_VAR([XMLTO],[Define/override the `xmlto' location.]) AC_ARG_VAR([XMLTO_FLAGS],[Define/override `xmlto' options, like `--skip-validation'.]) (this works nice in addition to AC_PATH_PROG) and in doc/Makefile.am use $(XMLTO) $(XMLTO_FLAGS) ... to let the user/maintainer workaround buggy XML if necessary (like in this case). However, you should create a check-target to check your DocBook XML: check-local: xmllint --noout --noent --valid ConsoleKit.xml to catch buggy XML before you make a distribution tarball. Regards, Daniel
Hopefully fixed now in master. Thanks for the advice!
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.