From: Miklos Vajna <vmiklos@frugalware.org>
To: Tim Visher <tim.visher@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Issues building docs on an offline box again.
Date: Tue, 24 Feb 2009 03:28:56 +0100 [thread overview]
Message-ID: <20090224022856.GN4371@genesis.frugalware.org> (raw)
In-Reply-To: <c115fd3c0902231507k46da3294yf2726a92cb0fbc1a@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
On Mon, Feb 23, 2009 at 06:07:54PM -0500, Tim Visher <tim.visher@gmail.com> wrote:
> xmlto -m callouts.xsl man git-add.xml
> 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 /tmp/xmlto-xsl.f254nC line 4 element import
> xsl:import : unable to load
> http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
> make: *** [git-add.1] Error 1
>
> Strange thing is that I thought I had gotten these to build offline
> before with the exact same configuration. Any thoughts?
Probably you somehow broke your docbook toolchain.
> My current solution is to build them on the online box and then copy
> them over the sneaker net to the offline box. But, this is kludgey,
> so not cool. :)
That's just a workaround. The solution is to have the correct mappings
under /etc/xml, so that it maps the doctype to
/usr/share/xml/docbook/manpages/docbook.xsl, or a similar path. After
all, ideally your distro does this for you automatically. :)
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-02-24 2:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 23:07 Issues building docs on an offline box again Tim Visher
2009-02-24 2:28 ` Miklos Vajna [this message]
2009-02-24 13:04 ` Tim Visher
2009-02-24 14:07 ` Miklos Vajna
2009-02-24 14:51 ` Ben Walton
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=20090224022856.GN4371@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--cc=git@vger.kernel.org \
--cc=tim.visher@gmail.com \
/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).