Bug#911992: stretch-pu: package spice-gtk/0.33-3.3+deb9u1

2018-10-26 Thread Salvatore Bonaccorso
Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu Hi spice-gtk is affected by the CVE-2018-10873 issue, as well tracked in the Debian BTS as #906316. Whilst for src:spice itself we released a DSA, for spice-gtk this does not warra

Bug#907199: Should the weboob package stay in Debian?

2018-10-26 Thread Chris Lamb
Dear Ian, > Please see the AH team's response here This is the response from late September. As I understand it, the AH team had a very recent meeting and it's highly likely that this issue was raised again then. I thus still await their update (or correction) on this. > So, should the next thin

Bug#907199: Should the weboob package stay in Debian?

2018-10-26 Thread Erik Granger
isn't there something more productive to do with y'alls time? On Fri, Oct 26, 2018 at 10:48 AM Ian Jackson < ijack...@chiark.greenend.org.uk> wrote: > Chris Lamb writes ("Re: Should the weboob package stay in Debian?"): > > I was led to believe — althought naturally feel very free to > > correct

Bug#911950: RM: wesnoth-1.12/1:1.12.6-1

2018-10-26 Thread Moritz Muehlenhoff
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Please remove wesnoth-1.12 by the next stretch point release. It's affected by CVE-2018-1999023. (People can still install wesnoth-1.14 from stretch-backport as an alternative) Cheers, M

Bug#907199: Should the weboob package stay in Debian?

2018-10-26 Thread Ian Jackson
Chris Lamb writes ("Re: Should the weboob package stay in Debian?"): > I was led to believe — althought naturally feel very free to > correct me — that the AH team were (quite correctly,) handling this > issue and thus I have not been taking action on it myself as > leader@. > > I therefore also e

Bug#907199: Should the weboob package stay in Debian?

2018-10-26 Thread Chris Lamb
Dear Ian, > > I look forward to hearing from the Debian maintainer, who I think is > > the first point of contact for the management of the package in > > Debian. > > I am concerned about the lack of progress. I would be grateful for > advice on what I should do next. I was led to believe — alt