On Tue, Oct 01, 2002 at 02:06:53AM -0700, Peter Davis wrote:
> On Friday 27 September 2002 08:59, Kevin Pilch-Bisson wrote:
> > Someone had the same problem on IRC last night, and upgrading to 2.0.42
> > solved it for them, so I think it might very well be caused by the version
> > mismatch.
>
> I keep seeing people having problems with outdated apaches. Shouldn't there
> be some autoconf check to simply not allow compiling with < 2.0.42 or with
> cvs earlier than some date? I haven't checked this myself so sorry if it's
> already doing that, but all these complaints make me suspicious.
Is there a document somewhere that describes which changes in 2.0.42
are needed for subversion and what is affected if you don't fulfill
this requirement?
I have done some tests here with svn 0.14.3 and apache 2.0.40 + some
patches and didn't have problems yet. So I wonder, if I was just
lucky or if the needed change is already in the patches I have here.
If there is just a simple fix for 2.0.40 needed to run svn I would
prefer to apply this patch rather than upgrading some productive
machines.
Robert
--
Robert Schiele Tel.: +49-621-181-2517
Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de
- application/pgp-signature attachment: stored
Received on Tue Oct 1 16:24:22 2002