Your message dated Thu, 20 Feb 2014 14:33:59 +0100
with message-id 
<capqicoxz14bdiiohurucrmhr+6wdro6tcjtwfuobnkowmwu...@mail.gmail.com>
and subject line Closing asciidoc bug 412260
has caused the Debian Bug report #412260,
regarding asciidoc: macros not expanded in NAME section of manpage
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
412260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412260
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: asciidoc
Version: 7.1.2-1
Severity: normal

For the stgit documentation (one frontend to many commands, hence one
manpage for the frontend and one per command), I have written a macro
to extract the one-line command descriptions from the code.  This
works perfectly when producing the frontend manpage with:

----------
stglink:new[]::
        stgdesc:new[]
----------

But the following in the command manpages does not work:

----------
NAME
----
stg-new - stgdesc:new[]
----------


Instead, the docbook and xhtml backend both produce "stgdesc:new[]" as
description, without producing an error when processing.


-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (90, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.19.1-smp
Locale: LANG=C, LC_CTYPE=french (charmap=ISO-8859-1)

Versions of packages asciidoc depends on:
ii  python                        2.4.4-2    An interactive high-level object-o

asciidoc recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 8.6.9-1

Hello,

Unable to reproduce the bug, unable to contact the submitter for 1
month now, so I close the bug.


Best regards,
Joseph

--- End Message ---

Reply via email to