I'm seeing the following error when I attempt to update a working copy that has an svn external.
svn: warning: W200000: Error handling externals definition for 'MySharedProjectBeforeRename': svn: warning: W160013: File not found: revision 100, path '/trunk/MySharedProjectBeforeRename' svn: E205011: Failure occurred processing one or more externals definitions The external is set to a specific revision such as revision r100 and a rename was recently done on that directory as part of revision r101. The external references a project that is located in a separate repository on the same server and has always worked until after the rename. It appears as though when svnserve is resolving the path that it is resolving first from HEAD even though a specific revision was specified. below is an example of what the external definition looks like followed by both the versions of svn client and svnserve that I'm running. -r 100 /shared/trunk/MySharedProjectBeforeRename MySharedProjectBeforeRename svn, version 1.7.4-SlikSvn-1.7.4-X64 (SlikSvn/1.7.4) X64 compiled Mar 8 2012, 13:42:47 svnserve, version 1.7.1-SlikSvn-1.7.1-WIN32 (SlikSvn/1.7.1) WIN32 compiled Oct 26 2011, 13:38:01 I've noticed that I can work around this issue by specifying my svn:external using a peg revision but I can't find anywhere in the documentation that suggests that using a peg revision is the correct way to reference a specific fixed revision number or in any other way suggests that this would be expected behavior. Could somebody comment on whether this issue is a bug in either svn or svnserve and if so whether it has been reported or perhaps fixed in a more recent release of Subversion 1.7. Thanks, Jeff Pierson
