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 16:54:33 -0800
On 11/7/13 4:31 PM, Geoff Field wrote:
Not sure what you mean by this. The issue has been taken seriously, it's just
> There's a known issue with the Apache server software (https://issues.apache.org/bugzilla/show_bug.cgi?id=55306) whereby if the directory tree being copied has a lock anywhere in it, the DAV component will send a 424 error. Why a copy should need to be concerned about a lock is a mystery.
The existing mod_dav module didn't properly comply with the RFC for DAV that
> The so-called "Resolution" listed in the mailing lists here was simply to break or release the locks. It's not really a fix, just a workaround.
No I'd say the resolution is to apply the patch that has been written to your
> The most recent release of Apache is 2.4.6 from July, but the last activity in the bug report is from October. Any idea when the next release is due? The Apache release policy (http://www.apache.org/dev/release.html) doesn't seem to tell me anything significant about that. (I do realise it's an open source project and therefore dependant on people volunteering their time.)
I don't know for sure but there was some desire to do a httpd 2.4.x release in
> In the meantime, we will all have to continue trying to remember to unlock files before attempting a branch, tag, or other copy. Either that, or revert to an earlier version of Apache.
My suggestion would be to apply the patch to your local httpd. I'd meant to
But for your immediate consumption for this specific issue. The following
Hope this helps you.
This is an archived mail posted to the Subversion Users mailing list.