{"thread":{"id":"31677","subject":"bug report, v1.7.12.1 -- Documentation/git-bundle.xml:130: parser error","startedAt":"2012-09-30T07:08:19Z","lastAt":"2012-09-30T18:29:39Z","messageCount":4,"participants":["Hugh Esco","Junio C Hamano","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"200196","messageId":"20120930030819.b5195ee0.hesco@yourmessagedelivered.com","threadId":"31677","inReplyTo":null,"subject":"bug report, v1.7.12.1 -- Documentation/git-bundle.xml:130: parser error","fromName":"Hugh Esco","fromEmail":"hesco@yourmessagedelivered.com","sentAt":"2012-09-30T07:08:19Z","receivedAt":"2012-09-30T07:08:19Z","isPatch":false,"sender":{"key":"hesco@yourmessagedelivered.com","avatar":null},"body":"doing a source install of git v1.7.12.1, \non the `make all doc` step, I get:\n\nxmlto: input does not validate (status 1)\n/usr/local/git-git-51993a4/Documentation/git-bundle.xml:130: parser error : Opening and ending tag mismatch: subscript line 130 and literal\nsuch as master1 cannot be packaged, but are perfec\n ^\n/usr/local/git-git-51993a4/Documentation/git-bundle.xml:134: parser error : Opening and ending tag mismatch: literal line 134 and subscript\nspecified explicitly (e.g. ^master10), or implici\n ^\nmake[1]: *** [git-bundle.1] Error 1\nmake[1]: Leaving directory `/usr/local/git-git-51993a4/Documentation'\nmake: *** [doc] Error 2\n\n-------------------------------------------\nand the patch which permitted me to proceed\n-------------------------------------------\n\n130c130\n> such as master1 cannot be packaged, but are perfectly suitable for\n---\n< such as master1 cannot be packaged, but are perfectly suitable for\n\n134c134\n> specified explicitly (e.g. ^master10), or implicitly (e.g.\n---\n< specified explicitly (e.g. ^master10), or implicitly (e.g.\n\n-------------------------------------------\n-------------------------------------------\n\nNext bug encountered with:\nDocumentation/git-check-ref-format.xml\n\ndetails to follow in next email.\n\n-- \nHugh Esco \n404-424-8701\nYourMessageDelivered.com\nKeeping Your Group in the Loop\nNo Matter How Large or How Small\n"},{"id":"200200","messageId":"7vipawge11.fsf@alter.siamese.dyndns.org","threadId":"31677","inReplyTo":"20120930030819.b5195ee0.hesco@yourmessagedelivered.com","subject":"Re: bug report, v1.7.12.1 -- Documentation/git-bundle.xml:130: parser error","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-09-30T07:34:18Z","receivedAt":"2012-09-30T07:34:18Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Hugh Esco writes:\n\n> doing a source install of git v1.7.12.1, \n> on the `make all doc` step, I get:\n>\n> xmlto: input does not validate (status 1)\n> /usr/local/git-git-51993a4/Documentation/git-bundle.xml:130: parser error : Opening and ending tag mismatch: subscript line 130 and literal\n> such as master1 cannot be packaged, but are perfec\n> ^\n> /usr/local/git-git-51993a4/Documentation/git-bundle.xml:134: parser error : Opening and ending tag mismatch: literal line 134 and subscript\n> specified explicitly (e.g. ^master10), or implici\n> ^\n> make[1]: *** [git-bundle.1] Error 1\n> make[1]: Leaving directory `/usr/local/git-git-51993a4/Documentation'\n> make: *** [doc] Error 2\n>\n> -------------------------------------------\n> and the patch which permitted me to proceed\n> -------------------------------------------\n>\n> 130c130\n>> such as master1 cannot be packaged, but are perfectly suitable for\n\nPLEASE STOP.\n\ngit-anything.xml files are _not_ the source files we edit, so\npatches to them are not useful for us.\n\nI suspect that a tilde inside literal `` environment is mishandled\nin your versions of the documentation toolchain. Either you would\nneed to upgrade some tool in the toolchain, or we would need patches\nto the source that would look like:\n\n\t-such as `master~1` cannot be packaged,...\n +such as `master{tilde}1` cannot be packaged,...\n\nto work around this problem if the version of the problematic tool\nyou are using is widespread.\n"},{"id":"200217","messageId":"20120930180209.GA13596@sigill.intra.peff.net","threadId":"31677","inReplyTo":"7vipawge11.fsf@alter.siamese.dyndns.org","subject":"Re: bug report, v1.7.12.1 -- Documentation/git-bundle.xml:130: parser error","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2012-09-30T18:02:09Z","receivedAt":"2012-09-30T18:02:09Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sun, Sep 30, 2012 at 12:34:18AM -0700, Junio C Hamano wrote:\n\n> I suspect that a tilde inside literal `` environment is mishandled\n> in your versions of the documentation toolchain. Either you would\n> need to upgrade some tool in the toolchain, or we would need patches\n> to the source that would look like:\n> \n> \t-such as `master~1` cannot be packaged,...\n> +such as `master{tilde}1` cannot be packaged,...\n> \n> to work around this problem if the version of the problematic tool\n> you are using is widespread.\n\nThat would not work, as commit 6cf378f turned off no-inline-literal, and\nmodern asciidoc would not expand that \"{tilde}\" at all. My guess is that\nHugh is using a version of asciidoc older than 8.4.1, which was the\nfirst version to understand inline literals.\n\nThis came up already once before:\n\n http://thread.gmane.org/gmane.comp.version-control.git/198733\n\nwhere the culprit was older third-party RPMs on RHEL5. It can be worked\naround by upgrading asciidoc, or using \"make quick-install-doc\" to pull\nthe pre-built versions.\n\n-Peff\n"},{"id":"200219","messageId":"20120930182939.30C058059E@mail.greens.org","threadId":"31677","inReplyTo":"20120930180209.GA13596@sigill.intra.peff.net","subject":"Re: bug report, v1.7.12.1 -- Documentation/git-bundle.xml:130: parser error","fromName":"Hugh Esco","fromEmail":"hesco@greens.org","sentAt":"2012-09-30T18:29:39Z","receivedAt":"2012-09-30T18:29:39Z","isPatch":false,"sender":{"key":"hesco@greens.org","avatar":null},"body":"Your are correct. That is apparently the issue:\n\ngit@pbx:~$ asciidoc --version\nasciidoc 8.2.7\n\nThis server is still running Debian Lenny.\nNot sure when I will be able to rebuild it. \n\nMy apologies for spamming your bug reporting list \nwith all of that. I now have source installs of git \nand gitolite installed and presumably working on this \nserver and promise not to bother you further with \nthat issue.\n\n-- Hugh Esco\n\nDate: Sun, 30 Sep 2012 14:02:09 -0400\nFrom: Jeff King \nTo: Junio C Hamano \nCc: hesco@yourmessagedelivered.com, git@vger.kernel.org\nSubject: Re: bug report, v1.7.12.1 -- Documentation/git-bundle.xml:130:\n parser error\n\nOn Sun, Sep 30, 2012 at 12:34:18AM -0700, Junio C Hamano wrote:\n\n> I suspect that a tilde inside literal `` environment is mishandled\n> in your versions of the documentation toolchain. Either you would\n> need to upgrade some tool in the toolchain, or we would need patches\n> to the source that would look like:\n> \n> \t-such as `master~1` cannot be packaged,...\n> +such as `master{tilde}1` cannot be packaged,...\n> \n> to work around this problem if the version of the problematic tool\n> you are using is widespread.\n\nThat would not work, as commit 6cf378f turned off no-inline-literal, and\nmodern asciidoc would not expand that \"{tilde}\" at all. My guess is that\nHugh is using a version of asciidoc older than 8.4.1, which was the\nfirst version to understand inline literals.\n\nThis came up already once before:\n\n http://thread.gmane.org/gmane.comp.version-control.git/198733\n\nwhere the culprit was older third-party RPMs on RHEL5. It can be worked\naround by upgrading asciidoc, or using \"make quick-install-doc\" to pull\nthe pre-built versions.\n\n-Peff\n"}]}