Bug#474951: [pkg-lighttpd] Bug#474951: Is a fix for etch planned?

2008-04-15 Thread Pierre Habouzit
On Tue, Apr 15, 2008 at 07:34:12AM +, Martin Schulze wrote: > Philipp Kern wrote: > > On Tue, Apr 15, 2008 at 08:39:03AM +0200, Pierre Habouzit wrote: > > > Dear security team, you broke lighttpd badly with your last upload, > > > because you use a broken patch to fix the last CVE on it. Plea

Bug#474951: [pkg-lighttpd] Bug#474951: Is a fix for etch planned?

2008-04-15 Thread Martin Schulze
Philipp Kern wrote: > On Tue, Apr 15, 2008 at 08:39:03AM +0200, Pierre Habouzit wrote: > > Dear security team, you broke lighttpd badly with your last upload, > > because you use a broken patch to fix the last CVE on it. Please update > > the patch, using e.g. the one in the unstable version inst

Bug#474951: [pkg-lighttpd] Bug#474951: Is a fix for etch planned?

2008-04-14 Thread Philipp Kern
On Tue, Apr 15, 2008 at 08:39:03AM +0200, Pierre Habouzit wrote: > Dear security team, you broke lighttpd badly with your last upload, > because you use a broken patch to fix the last CVE on it. Please update > the patch, using e.g. the one in the unstable version instead. You've > broken lightt

Bug#474951: [pkg-lighttpd] Bug#474951: Is a fix for etch planned?

2008-04-14 Thread Pierre Habouzit
On Tue, Apr 15, 2008 at 02:40:07AM +, Shane McChesney wrote: > Glad I found this thread, it explains the 239GB error log I just blew > away and the new one growing on the server now. > > On 1.4.13-4etch7, running: > > apt-get update > apt-get install lighttpd > > says "lighttpd is alread