Re: reportbug: please inform security and lts teams about security update regressions
- To: firstname.lastname@example.org
- Cc: Debian LTS <email@example.com>, "firstname.lastname@example.org" <email@example.com>, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org
- Subject: Re: reportbug: please inform security and lts teams about security update regressions
- From: Salvatore Bonaccorso <email@example.com>
- Date: Sun, 10 Dec 2017 10:00:55 +0100
- Message-id: <[🔎] 20171210090055.GB30428@eldamar.local>
- Mail-followup-to: firstname.lastname@example.org, Debian LTS <email@example.com>, "firstname.lastname@example.org" <email@example.com>, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org
- In-reply-to: <[🔎] email@example.com>
- References: <firstname.lastname@example.org> <[🔎] email@example.com>
Cc'ing explicitly Guido and Raphael, who commented before.
On Sat, Dec 09, 2017 at 03:25:14PM +0100, Markus Koschany wrote:
> I have updated my patch for reportbug. Now emails are sent only to one
> of the team mailing lists based on the release number in the version
> string. There is apparently no simple way to determine the relationship
> between release number, code name, suite and whether this is a LTS
> release. So we came up with a simple json file which provides this kind
> of information and can be adjusted as time goes by. We think that
> security-tracker.debian.org would be a good place for this file but I'd
> appreciate it if someone from the security team told us the exact location.
> See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878088#45
So let me first understand the information you would need from that
file (here in sort-of-yaml):
For reportbug I do not see a need for the alias mapping, so we should
not add it it yet, or why would you need to know that wheezy is
oldoldstable for it? AFAICS, what you need for is a value to decide if
it's lts or security team supported, that is what I'm aiming for in
the above format with the support field. Once jessie moves to lts
supported, we just need to update that value. Then on reportbug side,
if the support is for lts, X-Debbugs-CC the debian-lts list, if it's
support 'security', X-Debbugs-CC the security team.
Possibly we could add a static file exporting this information on the
security-tracker which only would be needed to extend once a suite
goes over to lts support and new known releases are added. Then could
be available under
How does your current patch for reportbug look like?
Please add my on Cc directly for replies.