Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: local policy)
From: Bob Archer <Bob.Archer@amsi.com>
To: Brenden Walker <BKWalker@drbsystems.com>, Philip Martin
	<philip.martin@wandisco.com>
CC: "users@subversion.apache.org" <users@subversion.apache.org>
Subject: RE: RESOLVED: SVN copy that worked in 1.8.0 now fails with (424
 FailedDependency)
Thread-Topic: RESOLVED: SVN copy that worked in 1.8.0 now fails with (424
 FailedDependency)
Thread-Index: Ac6Thz6vrYI4IW7FTKeYoxJi6fkpOQAAqvvpAAnJ/IAABT9cwA==
Date: Wed, 7 Aug 2013 18:30:12 +0000
Message-ID: <EA9A16E4E64F694BAD262610B0A2515C236843F7@USALWEXMBX2.infor.com>
References: <6DF864426572664E96691EF01A78725919B70E@DSIMail.drbsystems.com>
 <871u655v9i.fsf@ntlworld.com>
 <6DF864426572664E96691EF01A78725919B7A8@DSIMail.drbsystems.com>
In-Reply-To: <6DF864426572664E96691EF01A78725919B7A8@DSIMail.drbsystems.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

> > Brenden Walker <BKWalker@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?
>=20
> 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.
>=20
> Breaking the locks allowed me to do an SVN copy.
>=20
> I haven't tried reproducing, but I certainly can if that would be helpful=
.

Are you sharing working copies with multiple people?

BOb