Re: RESOLVED: SVN copy that worked in 1.8.0 now fails with (424 FailedDependency)
Brenden Walker bkwal...@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? -- Philip Martin | Subversion Committer WANdisco | Non-Stop Data
RE: RESOLVED: SVN copy that worked in 1.8.0 now fails with (424 FailedDependency)
-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 FailedDependency) Brenden Walker bkwal...@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.
RE: RESOLVED: SVN copy that worked in 1.8.0 now fails with (424 FailedDependency)
Brenden Walker bkwal...@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. Are you sharing working copies with multiple people? BOb
RE: RESOLVED: SVN copy that worked in 1.8.0 now fails with (424 FailedDependency)
-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 FailedDependency) Brenden Walker bkwal...@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. Are you sharing working copies with multiple people? If by that you mean checking out somewhere and having multiple people using the same working copy, no. Each developer has their own working copy. The reason the files were locked is that they're unmergeable binaries, AND most people here are still used to StarTeam. I offered up some other options to keep other developers from accidentally changing these files.
