mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Randall S. Becker" <>
To: <>
Subject: Documentation Breakage at 2.5.6
Date: Tue, 5 Dec 2017 23:12:33 -0500	[thread overview]
Message-ID: <008d01d36e48$747cc130$5d764390$> (raw)

Hi All,

I'm trying to upgrade the NonStop port from 2.3.7 upward eventually to
2.15.1 and hit a snag on documentation. The xmlto component is a bit new to
me and I hit the following error:

    XMLTO git-remote-testgit.1
xmlto: /home/git/git/Documentation/git-remote-testgit.xml does not validate
(status 3)
xmlto: Fix document syntax or use --skip-validation option
I/O error : Attempt to load network entity
/home/git/git/Documentation/git-remote-testgit.xml:2: warning: failed to
load external entity
D DocBook XML V4.5//EN"
I/O error : Attempt to load network entity
warning: failed to load external entity
validity error : Could not load the external subset

The -skip-validation option just takes me to a different problem validating
via sourceforge URL that appears not to exist anymore, although I had to
modify ./git/Documention/Makefile, which is vexing.

    XMLTO git-remote-testgit.1
I/O error : Attempt to load network entity
warning: failed to load external entity
compilation error: file /tmp/xmlto-xsl.ie6J8p line 4 element import
xsl:import : unable to load
Makefile:328: recipe for target 'git-remote-testgit.1' failed

Any advice on getting past this? It would be nice to get git help to working
again. An answer of "you need to get past 2.5.6" is ok too as long as I know
where I'm going.


-- Brief whoami: NonStop&UNIX developer since approximately
-- In my real life, I talk too much.

             reply	other threads:[~2017-12-06  4:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06  4:12 Randall S. Becker [this message]
2017-12-06  8:14 ` Documentation Breakage at 2.5.6 Ævar Arnfjörð Bjarmason
2017-12-06  8:48   ` Jeff King
2017-12-06 15:43     ` Randall S. Becker
2017-12-08 22:29       ` Junio C Hamano
2017-12-08 22:47         ` Randall S. Becker

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='008d01d36e48$747cc130$5d764390$' \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 read-only IMAP folder(s) and NNTP newsgroup(s).