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

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

From: Brenden Walker <BKWalker_at_drbsystems.com>
Date: Wed, 7 Aug 2013 16:59:57 +0000

> -----Original Message-----
> From: Philip Martin [mailto:philip.martin_at_wandisco.com]
> Sent: Wednesday, August 07, 2013 12:19 PM
> To: Brenden Walker
> Cc: users_at_subversion.apache.org
> Subject: Re: RESOLVED: SVN copy that worked in 1.8.0 now fails with (424
> FailedDependency)
>
> Brenden Walker <BKWalker_at_drbsystems.com> writes:
>
> >> > svn: E175002: Adding directory failed: COPY on
> >> > /svn/Development/!svn/rvr/7020/Trunk/Projects/SiteWatch (424 Failed
> >> > Dependency)
> >
> > Turned out that another developer had locks on several files.
> > Confirmed that was the problem. A more specific error message would
> > have been handy here.
>
> Can you describe how to reproduce the problem? What sort of locks prevent
> a COPY? Orphaned locks perhaps?

They were working copy locks from another developer. I asked him to try the build himself to see if it allows the user who holds the lock to svn copy, haven't heard back from that.

Breaking the locks allowed me to do an SVN copy.

I haven't tried reproducing, but I certainly can if that would be helpful.
Received on 2013-08-07 19:00:36 CEST

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