On Sun, Jul 05, 2020 at 09:55:30PM +0200, Christoph Berg wrote: > Re: tmanc...@debian.org > > > I/O error : Attempt to load network entity > > > http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl > > > warning: failed to load external entity > > > "http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl" > > > compilation error: file /etc/asciidoc/docbook-xsl/manpage.xsl line 12 > > > element import > > > xsl:import : unable to load > > > http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl > > > ... > > > > So I propose that we reassign this to asciidoc, since any package that > > build-depends on asciidoc and uses the manpage stylesheet should fail in > > the same manner. I don't have any experience with XSL stylesheets, but > > I assume that the asciidoc package can be updated to include the > > necessary components such that xsl files need not be fetched from the > > network during the build. > > > > Does that sound reasonable to folks? > > The primary problem is that we are missing a build-dependency on > docbook-xsl and possibly more packages of the xsl family which contain > the necessary files. > > I can't say if that is actually a bug in asciidoc to not depend on > the bunch. (I guess at least a Recommends or Suggests there is in > order, but that wouldn't fix the B-D problem.)
Ooh, thank you for the tip about docbook-xsl! That gives us a path forward for wsjtx. I see what you're saying about this maybe not being a bug for asciidoc. For now I'll add docbook-xsl to the B-D for wsjtx and upload with the patch for XSLTPROC_OPTS to add --nonet. Thanks, tony