OK, so I installed 1.9.7 just now and I still get the same issue.... but....
It looks like it might be related to if the working copy is based on a file:/// repo. If I do a rename with an absolute path for SRC for a working copy not based on a file:///, it does work. Would you mind trying a new local repo? Thanks! On Fri, Oct 27, 2017 at 12:06 AM, Johan Corveleyn <jcor...@gmail.com> wrote: > On Thu, Oct 26, 2017 at 11:50 PM, Dan Ellis <danelli...@gmail.com> wrote: > > > > Hi, > > > > I brought this up back in 2014 (https://svn.haxx.se/users/ > archive-2014-05/0115.shtml). I managed to work around it but just ended > up running into it again. I'm running SVN 1.8.13. > > > > C:\Project_files\wc1>svn rename C:\project_files\wc1\foo.c bar.c > > svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup' > for details) > > svn: E155004: Working copy 'C:\Project_files\wc1' locked. > > svn: E155004: 'C:\Project_files\wc1' is already locked. > > > > > > C:\Project_files\wc1>svn rename foo.c bar.c > > A bar.c > > D foo.c > > > > Can anyone else confirm this is an issue before I cross it over to dev? > > Hi Dan, > > I've tried this with a 1.9.1 svn client, and it seems to work fine. So > I guess this was fixed in 1.9. > > -- > Johan >
