[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: NOT RESOLVED: SVN copy that worked in 1.8.0 now fails with (424 FailedDependency)

From: Ben Reser <ben_at_reser.org>
Date: Thu, 07 Nov 2013 21:55:08 -0800

On 11/7/13 6:37 PM, Geoff Field wrote:
> I'm just trying to bump the priority again, given our circumstances.

Consider it bumped. :)

> So is it just mod_dav*.so that's affected?

Correct, this is only applicable to DAV. You won't see this problem if you're
using svnserve and it doesn't impact things that aren't DAV related with
respect to httpd. In practice this makes it generally specific to Subversion.
 Though I'm sure there's some people out there using mod_dav_fs (presumably
those people are the ones that wanted the fix that triggered several problems
for us).

> I agree. Breaking/releasing locks is NOT a resolution. Applying patches (or patched software) is. Is there an easy way to apply a patch on a Windows server with limited drive space for extra tools such as compilers?

Building httpd on Windows is unfortunately not easy at this time. I'd suggest
going with a binary produced by one of the vendors. I think several have
already patched. Mark mentioned that Collab.Net's packages are patched. Maybe
one of the other providers will chime in here that there's are patched as well.

Putting my own corporate hat on for a moment here. WANdisco binaries that come
with httpd should be patched as well. I need to ask the individual that builds
them to verify for sure. If you find that they are not let me know and I'll
see that this changes. You can find the WANdisco binaries here for free download:
Received on 2013-11-08 06:55:49 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.