git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git doc build failure on OS X 10.5.6 (Leopard) during xmlto phase

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Mar 13, 2009, 10:29 UTC
Message-ID
<49BA356D.8050007@drmicha.warpmail.net>
In-Reply-To
<20090312170931.GB19175@inocybe.teonanacatl.org>
Todd Zullinger venit, vidit, dixit 12.03.2009 18:09:
Show 7 quoted lines
> Michael J Gruber wrote:
>> Following up on this:
>> On Fedora 10, I have asciidoc 8.2.5 and docbook 1.7.4 xsl's. For
>> proper man and html doc, I have to set DOCBOOK_XSL_172=Yes but leave
>> ASCIIDOC8 unset! I always forget, though (just like the packagers).
> 
> Check the fedora git packages in rawhide, we don't set ASCIIDOC8. :)
I was unclear, but I meant forgetting to set DOCB... But:
Show 7 quoted lines
> I experimented with that and found it did not improve things.  We are
> only setting DOCBOOK_XSL_172.  Without that, we get the '.ft C'
> droppings.  With it, we get non-ascii characters in various places
> (where bold should be used to make the (1) notations stand out, for
> example).  This was filed as:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=485161

I hadn't noticed that yet (neither the effect nor the report). So, you kept it unset intentionally and for a good reason. Please accept my apology!

Show 12 quoted lines
> 
> I didn't add DOCBOOK_XSL_172 to the F-10 packages yet, because I know
> that it fixes one problem and causes another.  Either way, we'd be
> shipping packages with known brokeness.  I chose to stick with keeping
> the currently broken '.ft C' behavior.  Pick your poison. ;)
> 
> One of the fedora/red hat folks that works on the xmlto and docbook
> packages was going to take a look, as I very much don't understand the
> documentation stack.  :/
> 
> Anyone who does is very welcome to help find the culprit(s) and help
> get fixes to the proper places.

So the easy solution is out again, quite a pitty. The problem occurs on F10 as well as F11/rawhide, right?

On a related issue: Does anybody know which asciidoc versions need asciidoc7compatible to be set? 8.2.5 and above certainly don't, so we should not advise using it. asciidoc's hg repo doesn't go back much more (the initial revision does not need it either), and I haven't dug for their earlier history yet.

Michael J Gruber
Previous: Todd ZullingerNext: Jay Soffian
Message 11 of 15 in “git doc build failure on OS X 10.5.6 (Leopard) during xmlto phase”
  1. Tom HoladayMar 11, 2009
  2. Michael J GruberMar 11, 2009
  3. Jay SoffianMar 11, 2009
  4. Jay SoffianMar 11, 2009
  5. Jay SoffianMar 11, 2009
  6. Michael J GruberMar 11, 2009
  7. Alejandro RiveiraMar 11, 2009
  8. Michael J GruberMar 12, 2009
  9. Alejandro Riveira FernándezMar 12, 2009
  10. Todd ZullingerMar 12, 2009
  11. Michael J GruberMar 13, 2009
  12. Jay SoffianMar 13, 2009
  13. Michael J GruberMar 13, 2009
  14. byrnejbMar 31, 2009
  15. byrnejbMar 31, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.