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

2013-08-07 Thread Brenden Walker
> -Original Message- > From: Bob Archer [mailto:bob.arc...@amsi.com] > Sent: Wednesday, August 07, 2013 2:30 PM > To: Brenden Walker; Philip Martin > Cc: users@subversion.apache.org > Subject: RE: RESOLVED: SVN copy that worked in 1.8.0 now fails with (424

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

2013-08-07 Thread Bob Archer
> > Brenden Walker 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 p

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

2013-08-07 Thread Brenden Walker
> -Original Message- > From: Philip Martin [mailto:philip.mar...@wandisco.com] > Sent: Wednesday, August 07, 2013 12:19 PM > To: Brenden Walker > Cc: users@subversion.apache.org > Subject: Re: RESOLVED: SVN copy that worked in 1.8.0 now fails with (424 > FailedDep

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

2013-08-07 Thread Philip Martin
Brenden Walker 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 w