I did the deb7u9 update of apache2 and I was not aware of the regression
either. I wonder if it makes sense for bugs above a certain severity
affecting versions of a package which are security uploads to show up in
the security tracker. Or would there be some other sensible way, aside
from having
Hi Stefan,
> Note that a previous DLSA introduced a regression. It would be nice if
> you could take a look at that, too:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858373
Unfortunately I uploaded this morning before I saw your note about
this regression.
I've added anarcat and mejo
On 2017-07-07 16:02:51, Guido Günther wrote:
> On Fri, Jul 07, 2017 at 03:57:35PM +0200, Philipp Kern wrote:
>> On 07/06/2017 08:01 PM, Antoine Beaupré wrote:
>> > In looking at fixing #858539 (blocking WoSign and StartCom, in CC) for
>> > wheezy, I noticed the issue was also pending in jessie. Fur
Control: forcemerge 867169 867728
Control: severity 867169 important
Control: tags 867169 +patch
Hi everyone,
Some context, for the unattended-upgrades maintainer: the LTS folks have
noted there is an issue with unattended-upgrades in Debian LTS /
wheezy. It stopped working since the suite names
Hi Raphael,
On Saturday, 15 July 2017 11:52:49 CEST Raphael Hertzog wrote:
> Hello Stefan,
>
> The Debian LTS team would like to fix the security issues which are
> currently open in the Wheezy version of apache2:
> https://security-tracker.debian.org/tracker/CVE-2017-9788
>
> Would you like to
