Bug#397811: pygobject lets pygtk FTBFS

[Simon McVittie]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Carsten wrote:
> This would need more testing but could drop the imports of stylesheets
> from upstreams 
> website - which is bad anyway if upstream has a service outage or moves
> it's files 
> around or whatever. 

You may have misunderstood the process slightly. xsltproc is running in
a mode where network access is forbidden (--nonet), so it can never actually
go upstream for files. This is by design - it ensures that only packages
on the system are used for the build, for repeatability and security
against DoS (and from Debian's point of view, also ensures that we have
all the source code in accordance with the DFSG). It would also be considered
rude to download the stylesheets from upstream on every build, with no
caching :-)

Instead, it looks up requested stylesheets in a "catalog" in /etc/xml/catalog -
this file maps URI prefixes to directories, e.g. mapping
http://docbook.sourceforge.net/release/xsl/current/ to a directory in
/usr/share if you have docbook-xsl installed. xsltproc knows how to follow
this indirection and load the stylesheet from /usr/share rather than
downloading it from the Web.

It seems most correct to me for python-gobject-dev to depend on
docbook-xsl - the stylesheets in the former are wrappers around
stylesheets in the latter, referenced by URI, so whenever python-gobject-dev
is installed it should arrange for
http://docbook.sourceforge.net/release/xsl/current to have an entry in
the system's XML catalog, by depending on docbook-xsl.

Copying the needed stylesheets into python-gobject-dev sounds a bad idea -
you'd have to either conflict with the real docbook-xsl (!), or add an extra
catalog to the search path (likely to be complicated and require some
divergence from upstream), and by the time you've supported both HTML and
PDF rendering you'd have copied in half of docbook-xsl already, by my count
(XHTML ~1.3M, FO for PDFs ~1.3M and "common" ~3.2M, out of ~11M total in the
package).

Hope this helps,

	Simon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: OpenPGP key: http://www.pseudorandom.co.uk/2003/contact/ or pgp.net

iD8DBQFFmcYSWSc8zVUw7HYRAt/jAJ45u3Yvp0tGUvEakmhnRdZoB0ArywCg7+v6
15HcBMXOUPZKCKSU62yXuqA=
=k4ES
-----END PGP SIGNATURE-----