Re: postponing php5 issue

2017-02-23 Thread Thorsten Alteholz
On Tue, 21 Feb 2017, Emilio Pozuelo Monfort wrote: PS: has someone notified the maintainer before triaging this issue? i didn't see a mail go through... AFAIK we handle php5 ourselves. Yes, I added it to lts-do-not-call. Thorsten

Re: postponing php5 issue

2017-02-22 Thread Emilio Pozuelo Monfort
On 22/02/17 20:48, Antoine Beaupré wrote: > On 2017-02-21 21:57:23, Emilio Pozuelo Monfort wrote: >> On 20/02/17 23:19, Antoine Beaupré wrote: >>> It seems a bit too much to do a DLA for a single issue in the php5 >>> package (CVE-2016-7478, namely): >>> >>> https://security-tracker.debian.org/trac

Re: postponing php5 issue

2017-02-22 Thread Antoine Beaupré
On 2017-02-21 21:57:23, Emilio Pozuelo Monfort wrote: > On 20/02/17 23:19, Antoine Beaupré wrote: >> It seems a bit too much to do a DLA for a single issue in the php5 >> package (CVE-2016-7478, namely): >> >> https://security-tracker.debian.org/tracker/source-package/php5 >> >> I looked at the i

Re: postponing php5 issue

2017-02-21 Thread Emilio Pozuelo Monfort
On 20/02/17 23:19, Antoine Beaupré wrote: > It seems a bit too much to do a DLA for a single issue in the php5 > package (CVE-2016-7478, namely): > > https://security-tracker.debian.org/tracker/source-package/php5 > > I looked at the issue and the patch is easily ported, but i suggest we > postpo

postponing php5 issue

2017-02-20 Thread Antoine Beaupré
It seems a bit too much to do a DLA for a single issue in the php5 package (CVE-2016-7478, namely): https://security-tracker.debian.org/tracker/source-package/php5 I looked at the issue and the patch is easily ported, but i suggest we postpone this DLA until we have piled up more important issues