Re: Bug#878088: reportbug: please inform security and lts teams about security update regressions
Hi Sandro,
On Thu, Dec 28, 2017 at 08:30:34PM -0500, Sandro Tosi wrote:
> >> + if is_security_update and support != 'none':
> >> + if support == 'lts':
> >> + email_address = ['debian-lts@lists.debian.org']
> >> + else:
> >> + email_address = ['team@security.debian.org']
> >> + listcc.extend(email_address)
> >> +
> >
> > I did not had much time recently, so I'm a bit late. I would be nice
> > here if that follows as well the intention of the file with the
> > support field, that is (beware only "pseudcode"):
> >
> > [...]
> > if is_security_update and support != 'none':
> > if support == 'lts':
> > email_address = ['debian-lts@lists.debian.org']
> > elif support == 'security"
> > email_address = ['team@security.debian.org']
> > else
> > # nothing at at the moment, no more cases right now
> > [...]
> >
> > that is, in case we add another support value (you remember there was
> > once testing-security? ;-)) this can be done.
> >
> > I realize though you did now already upload the wheezy version, and
> > the unstable version as delayed, so guess we will need to leave it
> > now.
>
> could you make it so that distributions.json contains directly the
> email address to use? do you really need the indirection of d.json ->
> support + support -> actual email (hardcoded in code)?
As stated earlier, the intention of this file will be that it is
extensible, and for a key of the suite name, having various attributes
to be exported/exposed. So yes the above can be done, and I just have
added a 'contact' field as well wich could be used instead to hardcode
the address in reportbug.
https://security-tracker.debian.org/tracker/distributions.json
carries the data now already, hope this helps already.
Regards,
Salvatore
Reply to: