Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of jorton@redhat.com designates
 66.187.233.31 as permitted sender)
Date: Fri, 30 May 2008 16:26:54 +0100
From: Joe Orton <jorton@redhat.com>
To: dev@httpd.apache.org
Subject: Re: PR42829
Message-ID: <20080530152654.GA10175@redhat.com>
Mail-Followup-To: dev@httpd.apache.org
References: <200805292246.29785.sf@sfritsch.de>
 <483F2F6D.6050207@force-elite.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <483F2F6D.6050207@force-elite.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Organization: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor,
 Berkshire, SL4 1TE, United Kingdom.
  Registered in UK and Wales under Company Registration No. 03798903
  Directors: Michael Cunningham (USA), Brendan Lane (Ireland),
 Matt Parson (USA), Charlie Peters (USA)

On Thu, May 29, 2008 at 03:34:21PM -0700, Paul Querna wrote:
> Stefan Fritsch wrote:
>> https://issues.apache.org/bugzilla/attachment.cgi?id=21137 has been in 
>> Debian testing and unstable for about 6 months without problems. It is not 
>> an elegant solution but it works. Considering that is is not clear how an 
>> elegant solution would look like, including this patch might make sense.
>
> Please don't put these kind of patches into the debian apache packages, 
> especially ones that don't exist in trunk.

Why not, is this some kind of distros-can't-be-trusted-to-run-patch 
reaction after the Debian OpenSSL PRNG incident?  Blah.  

1) we-the-committers failed to do anything useful about this bug
2) Stefan has a patch 
3) having more test data from people running that patch is useful

If you don't want people *patching* the *Apache source code* (god 
forbid!), then we need to go pick another license.

joe