You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Ian Girouard <ig...@aquadata.com> on 2013/08/21 19:56:30 UTC
SVN Copy now fails with 424 FailedDependency
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
Thanks
Re: SVN Copy now fails with 424 FailedDependency
Posted by Philip Martin <ph...@wandisco.com>.
"Ian Girouard" <ig...@aquadata.com> writes:
> 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)
> 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.
> Server : Visual SVN Server 2.6.4, with svn 1.8.1 and apache HTTP Server
> 2.2.25
This is a bug in the mod_dav module that comes with httpd 2.2.25. A fix
for https://issues.apache.org/bugzilla/show_bug.cgi?id=54610 was added
to 2.2.25 but the fix appears to be broken.
--
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*
Re: SVN Copy now fails with 424 FailedDependency
Posted by Ben Reser <be...@reser.org>.
On 8/21/13 12:27 PM, Ben Reser wrote:
> Okay that isn't a duplicate. The fix for PR 55304 removed the check
> for the parent of the copy but not the check for the locks. That's
> going to be a lot messier of a fix.
Turns out it wasn't so bad of a fix, but it took some studying of the RFC to
figure out how to do it correctly. It's fixed in httpd-trunk:
https://svn.apache.org/r1528718
I'll nominate it for 2.4.x and 2.2.x backport and hopefully it can be included
in the next releases of each.
Re: SVN Copy now fails with 424 FailedDependency
Posted by Ben Reser <be...@reser.org>.
On Wed Aug 21 12:15:05 2013, Ben Reser wrote:
> On Wed Aug 21 11:31:09 2013, Mark Phippard wrote:
>> 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
>
> That looks like a potential dupe of:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=55304
>
> Which is fixed but not included in a released version of httpd yet.
> Can someone try applying the change from that bug to their httpd and
> see if they can still replicate the issue?
Okay that isn't a duplicate. The fix for PR 55304 removed the check
for the parent of the copy but not the check for the locks. That's
going to be a lot messier of a fix.
I'd suggest that people using Subversion with httpd 2.2.25 apply the
patch produced by this command:
$ svn diff -c -1497441
https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/modules/dav/main/mod_dav.c
and people using httpd 2.4.6 apply the patch matching this command:
$ svn diff -c -1486456
https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/modules/dav/main/mod_dav.c
The fixes that the above is removing are for mod_dav_fs and unless
you're using them they shouldn't create any problems for you.
Re: SVN Copy now fails with 424 FailedDependency
Posted by Ben Reser <be...@reser.org>.
On Wed Aug 21 11:31:09 2013, Mark Phippard wrote:
> 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
That looks like a potential dupe of:
https://issues.apache.org/bugzilla/show_bug.cgi?id=55304
Which is fixed but not included in a released version of httpd yet.
Can someone try applying the change from that bug to their httpd and
see if they can still replicate the issue?
Re: SVN Copy now fails with 424 FailedDependency
Posted by Mark Phippard <ma...@gmail.com>.
On Wed, Aug 21, 2013 at 1:56 PM, Ian Girouard <ig...@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/