Updating a working copy of the source repository fixed the problem. (I
had forgotten that I had a working copy.)
But I am still concerned that the information from svnsync and svnadmin
contradict, or that the svnadmin commands don't work.
Have I misunderstood something?
Jonathan Coles wrote:
> An svnsync session to a mirror repository on my machine was aborted.
> On retry I get the error message, "Failed to get lock on destination
> repos, currently held by ...".
>
> I tried to use svnadmin lslocks on the repository path. It returns
> nothing. How obtuse! There are locks on that repository! I tried an
> svnadmin rmlocks on the repository. Response: "No paths to unlock
> provided". The repository path is all I have as the location of the
> lock. What does svnadmin want?
>
> There are other commands for displaying and releasing locks, but they
> require a working copy. All I have is two repositories, the remote one
> which is the source and my mirror repository, the destination.
>
> To recap: *svnsync* says that there are locks. *svnadmin* says there
> are none. Mirroring of the repository is no longer possible. Is there
> a way out, short of destroying the destination repository and starting
> over?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-22 01:51:05 CEST