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

2017-11-29 Thread Guido Günther
Hi Markus, Great this is still moving forward! On Wed, Nov 29, 2017 at 08:00:12PM +0100, Markus Koschany wrote: > Hi! [..snip..] > I would prefer this solution. At the moment we check for the version > string and I think that's sufficient for an initial check. The following > actions should be

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

2017-12-01 Thread Guido Günther
Hi Markus, On Thu, Nov 30, 2017 at 06:38:27PM +0100, Markus Koschany wrote: > On Wed, 29 Nov 2017 22:49:55 +0100 Guido =?iso-8859-1?Q?G=FCnther?= > wrote: > [...] > > Can't we deduce if it's LTS from either the packages version number or from > > /etc/debian_version. Once we

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

2017-12-13 Thread Guido Günther
Hi Markus, (trimming the cc: list a bit since this is just a minor nit): [..snip..] > +for key, value in data.items(): > +if distnumber in value['major-version']: distnumber == value['major-version'] might be better since with distnumber = 1 it

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

2017-12-09 Thread Guido Günther
Hi, On Wed, Dec 06, 2017 at 08:48:17AM +0100, Markus Koschany wrote: > On Fri, 1 Dec 2017 09:28:26 +0100 Guido =?iso-8859-1?Q?G=FCnther?= > wrote: > [...] > > I would rather not make psql connections from reportbug. http is > > ubiquitous and can be proxied. That's why I

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

2017-12-09 Thread Guido Günther
Hi, On Sat, Dec 09, 2017 at 03:28:09PM +0100, Markus Koschany wrote: > Am 09.12.2017 um 15:21 schrieb Guido Günther: > [...] > > Looks good in principle. I would use a slightly different json format > > though (using YAML for readability): > > > > wheezy

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

2017-12-10 Thread Guido Günther
Hi, On Sun, Dec 10, 2017 at 12:51:38PM +0100, Salvatore Bonaccorso wrote: > Hi > > On Sun, Dec 10, 2017 at 10:00:55AM +0100, Salvatore Bonaccorso wrote: > > Hi > > > > Cc'ing explicitly Guido and Raphael, who commented before. > > > > On Sat, Dec 09, 2017 at 03:25:14PM +0100, Markus Koschany

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

2017-12-10 Thread Guido Günther
Hi, On Sun, Dec 10, 2017 at 01:35:43PM +0100, Salvatore Bonaccorso wrote: > Hi Guido, > > On Sun, Dec 10, 2017 at 12:59:05PM +0100, Guido Günther wrote: > > Hi, > > On Sun, Dec 10, 2017 at 12:51:38PM +0100, Salvatore Bonaccorso wrote: > > > Hi > > > > &g

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

2018-01-29 Thread Guido Günther
Hi Markus, thanks for pursuing this! Some minor nitpicks: On Mon, Jan 29, 2018 at 12:11:03AM +0100, Markus Koschany wrote: [..snip..] > +if utils.is_security_update(package, pkgversion): > +if ui.yes_no('Do you want to report a regression because of > a security

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

2018-01-29 Thread Guido Günther
Hi, On Mon, Jan 29, 2018 at 01:29:59PM +0100, Markus Koschany wrote: > [sorry forgot to CC the rest] > > Hello, > > Am 29.01.2018 um 09:30 schrieb Guido Günther: > > Hi Markus, > > thanks for pursuing this! Some minor nitpicks: > > > > On Mon, Jan 29, 20

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

2018-01-29 Thread Guido Günther
Hi, On Mon, Jan 29, 2018 at 01:34:51PM +0100, Markus Koschany wrote: > > >> This will not catch 404 or similar http status codes. If you don't care > >> about the type of error you can just do … > >> > >>r.raise_for_status() > > Ok, got it. So adding