Thanks. I didn't think any server-side locks were involved, but didn't know if a commit earlier on may have done something on the server-side. I did get around it by using the "svn mv" command to do a server-to-server move - kind of like doing it in TSVN's Repository Browser; and that worked just fine.
I'll have to look to see if upgrading the client to 1.7 is feasible - though I don't do this specific task very often; it's just a matter of whether there's enough dependencies in 8.04 to support 1.7 series; I already had to build 1.6 for it (since Debian/Ubuntu only supports 1.5 for 8.04). Thanks! Ben >________________________________ > From: Philip Martin <philip.mar...@wandisco.com> >To: BRM <bm_witn...@yahoo.com> >Cc: SubVersion Users <users@subversion.apache.org> >Sent: Wednesday, April 3, 2013 4:11 PM >Subject: Re: SVN wc/repo issue... > >BRM <bm_witn...@yahoo.com> writes: > >> $ svn mv ../../include . >> >> However, 'svn mv' keeps returning: >> >> Unable to lock '.' > >> Is there any way to tell what might be locked on the server side? > >The error does not involve a server-side lock. > >> We're using Apache2/2.2.22 + Subversion 1.6.17 as the server (Ubuntu >> Releases); and I'm using 1.6.19 on the client (compiled under Kubuntu >> 8.04). > >It's a bug in the 1.6 client that is fixed in 1.7. You can work >around it in 1.6 by doing > >$ cd ../.. >$ svn mv include foo/bar > >-- >Certified & Supported Apache Subversion Downloads: >http://www.wandisco.com/subversion/download > > >
