Your message dated Wed, 27 Jan 2010 11:21:48 +0000
with message-id <[email protected]>
and subject line Bug#566989: fixed in reportbug 4.10.2
has caused the Debian Bug report #566989,
regarding reportbug: Please stop removing “Source” from pseudoheaders.
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.)
--
566989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566989
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: reportbug
Version: 4.10.1
Severity: important
Hi,
while waiting for #560230 to be fixed, I tried to do as proposed by Kurt
or Lucas, that is, “reportbug $source” and then s/Package/Source/ in the
pseudoheaders. Unfortunately, that leads to a broken message (without
Package/Source line) sent to the BTS, which in turn ignores the message
entirely.
One can notice that “Source: $source” appears in the headers, though;
but no longer in pseudoheaders.
Example of such outgoing mail:
| Received: (at submit) by bugs.debian.org; 18 Jan 2010 10:43:26 +0000
| X-Spam-Checker-Version: SpamAssassin 3.2.3-bugs.debian.org_2005_01_02
| (2007-08-08) on rietz.debian.org
| X-Spam-Level:
| X-Spam-Bayes: score:0.0000 Tokens: new, 139; hammy, 149; neutral, 101; spammy,
| 2. spammytokens:0.993-1--ipage, 0.993-1--Api
| hammytokens:0.000-+--H*M:reportbug, 0.000-+--H*MI:reportbug,
| 0.000-+--H*x:reportbug, 0.000-+--H*UA:reportbug, 0.000-+--Severity
| X-Spam-Status: No, score=-11.8 required=4.0 tests=AWL,BAYES_00,FROMDEVELOPER,
| HELO_LH_LD,MURPHY_DRUGS_REL8,MURPHY_WRONG_WORD1,MURPHY_WRONG_WORD2,
| XMAILER_REPORTBUG,X_DEBBUGS_CC autolearn=ham
| version=3.2.3-bugs.debian.org_2005_01_02
| Return-path: <[email protected]>
| Received: from gruyere.kerlabs.com ([62.160.40.62] helo=localhost.localdomain)
| by rietz.debian.org with esmtp (Exim 4.63)
| (envelope-from <[email protected]>)
| id 1NWp4w-0000oq-1O
| for [email protected]; Mon, 18 Jan 2010 10:43:26 +0000
| Content-Type: text/plain; charset="us-ascii"
| MIME-Version: 1.0
| Content-Transfer-Encoding: 7bit
| From: Cyril Brulebois <[email protected]>
| To: Debian Bug Tracking System <[email protected]>
| Subject: qt4-x11: FTBFS on GNU/kFreeBSD
| Source: qt4-x11
| Message-ID: <[email protected]>
| X-Mailer: reportbug 4.10.1
| Date: Mon, 18 Jan 2010 11:43:30 +0100
| X-Debbugs-Cc: [email protected]
| Delivered-To: [email protected]
|
| Version: 4:4.6.0-1
| Severity: serious
| Justification: FTBFS
|
| Hi,
|
| [ Real bug reportbug body ]
|
| Mraw,
| KiBi.
Response from the BTS:
| Your message didn't have a Package: line at the very first line of the
| mail body (part of the pseudo-header), or didn't have a Package: line
| at all. Unfortunatly, this means that your message has been ignored
| completely.
|
| Without this information we are unable to categorise or otherwise deal
| with your problem report. Please _resubmit_ your report to
| [email protected] and tell us which package the
| report is for. For help, check out
| http://www.debian.org/Bugs/Reporting.
|
| Your message was dated Mon, 18 Jan 2010 11:43:30 +0100 and had
| message-id <[email protected]>
| and subject qt4-x11: FTBFS on GNU/kFreeBSD.
| The complete text of it is attached to this message.
|
| If you need any assistance or explanation please contact
| [email protected] and include the the attached
| message.
|
| If you didn't send the attached message (spam was sent forging your
| from address), we apologize; please disregard this message.
|
| --
| -1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1
| Debian Bug Tracking System
| Contact [email protected] with problems
I guess this answer could mention the possibility of using “Source”,
too, but that's another story.
Mraw,
KiBi.
--- End Message ---
--- Begin Message ---
Source: reportbug
Source-Version: 4.10.2
We believe that the bug you reported is fixed in the latest version of
reportbug, which is due to be installed in the Debian FTP archive:
python-reportbug_4.10.2_all.deb
to main/r/reportbug/python-reportbug_4.10.2_all.deb
reportbug_4.10.2.dsc
to main/r/reportbug/reportbug_4.10.2.dsc
reportbug_4.10.2.tar.gz
to main/r/reportbug/reportbug_4.10.2.tar.gz
reportbug_4.10.2_all.deb
to main/r/reportbug/reportbug_4.10.2_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sandro Tosi <[email protected]> (supplier of updated reportbug package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Tue, 26 Jan 2010 23:51:23 +0100
Source: reportbug
Binary: reportbug python-reportbug
Architecture: source all
Version: 4.10.2
Distribution: unstable
Urgency: low
Maintainer: Reportbug Maintainers <[email protected]>
Changed-By: Sandro Tosi <[email protected]>
Description:
python-reportbug - Python modules for interacting with bug tracking systems
reportbug - reports bugs in the Debian distribution
Closes: 566989
Changes:
reportbug (4.10.2) unstable; urgency=low
.
* reportbug/utils.py
- allow 'Source' as pseudo-header; thanks to Cyril Brulebois for the
report;
Closes: #566989
Checksums-Sha1:
03b8c5ca4f3b54b027af5b89bb138f6f72c8d1c2 1121 reportbug_4.10.2.dsc
39200f3d4a53a1ba80f479b239b3be087a350301 168752 reportbug_4.10.2.tar.gz
533ec3d3069cc6b63fab1d2ed8d8ba33dc79e4f6 107624 reportbug_4.10.2_all.deb
fb9f58a29f20d6202d4ca4fe3fc75d020db33561 120536 python-reportbug_4.10.2_all.deb
Checksums-Sha256:
56016949c528bf487cc98f3992d09f77d94b1c5644f388aa4486ad7bcdb6420e 1121
reportbug_4.10.2.dsc
72a132be72b11911841ff08c4511ab4509f4f0a8a8b12cb94fbbd15f6b521fa0 168752
reportbug_4.10.2.tar.gz
5c93eea96d80ca6156b623edb3f272900445c5ec5c3560d4a9723013ac1f6e28 107624
reportbug_4.10.2_all.deb
1dbf1b14703f5814358a59ffdb8b30da42b4f65fbc9cdfac46ceda9cb20272cb 120536
python-reportbug_4.10.2_all.deb
Files:
b7b8ae0a2df248cf30c3b70cce0487a3 1121 utils standard reportbug_4.10.2.dsc
ad07225908dfa58b6e80033a8e53aa4f 168752 utils standard reportbug_4.10.2.tar.gz
b2cb5ba9590c59cf84d8cab24eb9aabe 107624 utils standard reportbug_4.10.2_all.deb
dc423d5428d542782aee458afa0b9a28 120536 python standard
python-reportbug_4.10.2_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAktfcyMACgkQAukwV0RN2VDVyACghbxIGSatuvcjqB9Zry/aoRVe
4+EAnijDG2eyUSRSqHvUoC/VYerFBDMj
=u/2I
-----END PGP SIGNATURE-----
--- End Message ---
