On 2009-02-11 08:22, Gerfried Fuchs wrote:
> Alright, this is getting ridiculous. Did anyone actually try the build
> on an etch system before it was dumped on us? What times did it take? It
> is now building since over 8 hours and still not finished.
...
> My impression is that the time is currently spent in trying to get
> responses from external servers:
Just for explanation:
1. No external nor internal DTDs are ever needed to build the
lenny release notes. (DTDs are needed, if you want to
validate XML, but not for compilation.) No need to install
docbook-xml, no harm either.
Locally, via the XML catalog system, are accessed the XSL
stylesheets of the docbook-xsl package. Is this package
installed (standard etch version, no backport required).
2. xsltproc is always called with the --nonet option in the
lenny release notes Makefile and always has been since we
started to use xsltproc. It shows an error message
(IO error), but one can - to my knowledge - ignore that error
message safely.
3. Unfortunately, I forgot that dblatex internally also calls
xsltproc. So I now pass this option also to dblatex. Now I
discovered, that there is a bug in dblatex: In one case it
"forgets" to pass the options to xsltproc. Patch attached
for review.
4. I did not have problems building the release notes on etch,
because I built with network.
HTH.
--- /usr/share/dblatex/lib/dbtexmf/core/dbtex.py 2008-08-18 13:30:07.000000000 +0200
+++ /root/etch/usr/share/dblatex/lib/dbtexmf/core/dbtex.py 2009-02-12 00:13:55.000000000 +0100
@@ -174,7 +174,7 @@
param = {"current.dir": self.inputdir}
self.xsltproc.use_catalogs = 0
self.xsltproc.run(self.xsllist, self.input,
- self.listings, params=param)
+ self.listings, opts=self.xslopts, params=param)
else:
self.log.info("No external file support")
f = file(self.listings, "w")
