[Reportbug-maint] Bug#882983: Doesn't ask for description anymore and break afterwards

2017-11-28 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: reportbug Version: 7.1.7 Severity: grave Since several weeks I just get the following message after the list of current bugs: Briefly describe the problem (max. 100 characters allowed). This will be the bug email subject, so keep the su

[Reportbug-maint] Bug#882983: marked as done (Doesn't ask for description anymore and break afterwards)

2017-11-28 Thread Debian Bug Tracking System
Your message dated Tue, 28 Nov 2017 09:58:01 -0500 with message-id and subject line Re: Bug#882983: Doesn't ask for description anymore and break afterwards has caused the Debian Bug report #882983, regarding Doesn't ask for description anymore and break afterwards to be marked as done. This me

[Reportbug-maint] Bug#878088: reportbug: please inform security and lts teams about security update regressions

2017-11-28 Thread Markus Koschany
Hello, I still haven't got a response for Debian bug #878088 and I wonder if we should implement this feature in Wheezy (and Jessie/Stretch if the security team agrees) now. Are there any objections, hints, recommendations? Regards, Markus signature.asc Description: OpenPGP digital signature

[Reportbug-maint] Bug#878088: reportbug: please inform security and lts teams about security update regressions

2017-11-28 Thread Raphael Geissert
Hi, On 9 October 2017 at 19:47, Markus Koschany wrote: [...] > If the bug is reported against a package with a version number that > indicates a security update like +deb7u1 or ~deb8u3, both team mailing > lists should be added to CC after the bug reporter confirms that this > is a regression cau