git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Francis Moreau <francis.moro@gmail.com>
To: Drew Northup <drew.northup@maine.edu>
Cc: git@vger.kernel.org
Subject: Re: Can't build doc anymore (v1.7.3.2)
Date: Tue, 23 Nov 2010 08:50:02 +0100	[thread overview]
Message-ID: <m2bp5glbrp.fsf@gmail.com> (raw)
In-Reply-To: <1290461070.5468.5.camel@drew-northup.unet.maine.edu> (Drew Northup's message of "Mon, 22 Nov 2010 16:24:30 -0500")

Drew Northup <drew.northup@maine.edu> writes:

[...]

> Supposedly docbook-dtds-1.0-53.fc14 contains the files needed. I would
> check to make sure that your /usr/share/sgml/docbook/xmlcatalog file is
> correct. If it is it will contain a line an awful lot like the
> following:
> <public publicId="-//OASIS//DTD DocBook XML V4.5//EN" uri="xml-dtd-4.5/docbookx.dtd"/>

It doesn't seem so:

  $ cat /usr/share/sgml/docbook/xmlcatalog
  <?xml version="1.0"?>
  <!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN" "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd">
  <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"/>

This file belongs to xml-common-0.6.3-33.fc14.noarch which sounds pretty
uptodate for a Fedora distribution.

Here's a list of some packages installed on my system that might be
relevant:

  asciidoc-8.4.5-5.fc14.noarch
  docbook-utils-0.6.14-26.fc14.noarch
  docbook-style-xsl-1.75.2-6.fc14.noarch
  docbook-style-dsssl-1.79-11.fc14.noarch
  docbook-dtds-1.0-53.fc14.noarch
  xml-commons-resolver-1.2-4.fc14.noarch
  xmlto-0.0.23-3.fc13.x86_64
  xmltex-20020625-16.fc13.noarch
  libxml2-devel-2.7.7-2.fc14.x86_64
  libxml2-python-2.7.7-2.fc14.x86_64
  libxml++-2.30.1-1.fc14.x86_64
  libxml2-2.7.7-2.fc14.i686
  libxml++-2.30.1-1.fc14.i686
  xml-common-0.6.3-33.fc14.noarch
  xml-commons-apis-1.4.01-1.fc13.noarch

-- 
Francis

  reply	other threads:[~2010-11-23  7:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22 19:45 Can't build doc anymore (v1.7.3.2) Francis Moreau
2010-11-22 20:35 ` Drew Northup
2010-11-22 20:44   ` Francis Moreau
2010-11-22 21:24     ` Drew Northup
2010-11-23  7:50       ` Francis Moreau [this message]
2010-11-23  8:45         ` Michael J Gruber
2010-11-23  9:05           ` Francis Moreau
2010-11-23  9:20             ` Michael J Gruber
2010-11-23  9:32               ` Francis Moreau
2010-11-23 10:01                 ` Michael J Gruber
2010-11-23 11:24                   ` Francis Moreau
2010-11-23 11:41                     ` Michael J Gruber
2010-11-23 11:57                       ` Francis Moreau
2010-11-23 12:04                         ` Michael J Gruber
2010-11-23 12:31                           ` Francis Moreau
2010-11-23 13:13           ` Drew Northup
2010-11-23 13:59             ` Michael J Gruber
2010-11-23 16:36               ` Francis Moreau
2010-11-23 17:06                 ` Drew Northup
2010-11-23 20:48                   ` Francis Moreau
2010-11-24 19:17                     ` Junio C Hamano
2010-11-25  8:13                       ` git
2010-11-25 19:54                         ` Francis Moreau
2010-11-23 16:30             ` Francis Moreau
2010-11-22 21:01 ` Pascal Obry
2010-11-22 21:14   ` Francis Moreau

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=m2bp5glbrp.fsf@gmail.com \
    --to=francis.moro@gmail.com \
    --cc=drew.northup@maine.edu \
    --cc=git@vger.kernel.org \
    /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).