[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#836613: debbugs: specifying 0 (“current message”) causes ‘summary’ to attempt to parse message header



Package: debbugs
Severity: normal

The attached response came from ‘debbugs’ when I sent a message
<URL:https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=358195;msg=33>
that contains a command “summary -1 0”.

According to the documentation for that command:

    The first non-pseudoheader/non-control paragraph of that message
    is parsed and set as the outlook of the bug which is displayed on
    the top of the bug report page.

    […] if a message number of 0 is given, the current message is used
    (that is, the message which was sent to control@bugs.debian.org
    which contains the outlook control command).

    <URL:https://www.debian.org/Bugs/server-control#summary>

I understand the documentation to imply that the referenced message
should have worked: It contained a <message number> value of “0”, and
the “first non-pseudoheader/non-control paragraph of that message” was
the summary text required.

The ‘debbugs’ server has evidently retrieved a completely different
text, some “Received” field from the message header. This fails to
meet the behaviour described in the documentation.

-- 
 \          “Jury: A group of 12 people, who, having lied to the judge |
  `\       about their health, hearing, and business engagements, have |
_o__)                           failed to fool him.” —Henry L. Mencken |
Ben Finney <bignose@debian.org>
--- Begin Message ---
Processing control commands:

> summary -1 0
Failed to give 358195 a summary: Can't use string ("Received: (at 358195) by bugs.de"...) as an ARRAY ref while "strict refs" in use.


-- 
358195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=358195
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- End Message ---

Attachment: signature.asc
Description: PGP signature


Reply to: