Re: SVN Copy now fails with 424 FailedDependency

On Wed, Aug 21, 2013 at 1:56 PM, Ian Girouard <igirouard_at_aquadata.com>wrote:

> Hi, I’m trying to do a svn copy command to create a tag and I get the
> following error : ****
>
> ** **
>
> Command: Copy C:\Projets\Logiciels9.1.XX.307 to
> https://svn.aquadata.com:8443/svn/Logiciels/Tags/TestTagSVN18, Revision
> WC ****
>
> Adding: C:\Projets\Logiciels9.1.XX.307 ****
>
> Error: Commit failed (details follow): ****
>
> Error: Adding directory failed: COPY on ****
>
> Error: /svn/Logiciels/!svn/rvr/118520/Branches/9.1.XX.307 (424 Failed
> Dependency) ****
>
> ** **
>
> This command is executed as a part of our deployment process and it worked
> flawlessly in svn 1.7 before upgrading to 1.8****
>
> I was able to make the copy work by asking all the developers to release
> their locks on the repository. (We have locks only on binary files) This
> workaround can’t be a solution because developers need to keep their locks
> even when we are doing a deployment.****
>
> ** **
>
> Here is our setup****
>
> Server : Visual SVN Server *2.6.4, with svn 1.8.1 and apache HTTP Server
> 2.2.25*****
>
> Client : TortoiseSVN 1.8.1****
>
> **
>

I have had two different people report this problem to me as well. In this
case they were using SVN Edge which provides Apache 2.4.6

I think this regression is probably caused by a change in mod_dav in Apache
2.2.25/2.4.6

https://issues.apache.org/bugzilla/show_bug.cgi?id=55306

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/