Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of cloos@jhcloos.com designates
 198.147.23.85 as permitted sender)
From: James Cloos <cloos@jhcloos.com>
To: users@subversion.apache.org
Subject: snvsync issues
User-Agent: Gnus/5.130012 (Ma Gnus v0.12) Emacs/24.4.50 (gnu/linux)
Face: iVBORw0KGgoAAAANSUhEUgAAABAAAAAQAgMAAABinRfyAAAACVBMVEX///8ZGXBQKKnCrDQ3
 AAAAJElEQVQImWNgQAAXzwQg4SKASgAlXIEEiwsSIYBEcLaAtMEAADJnB+kKcKioAAAAAElFTkSu
 QmCC
Copyright: Copyright 2014 James Cloos
OpenPGP: 0x997A9F17ED7DAEA6;
 url=https://jhcloos.com/public_key/0x997A9F17ED7DAEA6.asc
OpenPGP-Fingerprint: E9E9 F828 61A4 6EA9 0F2B  63E7 997A 9F17 ED7D AEA6
Date: Wed, 07 May 2014 10:50:59 -0400
Message-ID: <m3d2fphcb7.fsf@carbon.jhcloos.org>
Lines: 24
MIME-Version: 1.0
Content-Type: text/plain

I occasionally get syncs which are stuck because something killed the
process before it could release its lock.

The only way I could get past that was to edit revprops/0/0 and remove
the svn:sync-lock lines.

Is there a command which will remove such stale svnsync locks?

Neither svn, svnadmin nor svnsync seem to be able to do so.  Or even to
list such locks.

Several of the remote repos which I'd like to sync fail part way through
with errors like:

   svnsync: E210008: Error while replaying commit

Git-svn is able to clone such repos, including the commits which svnsync
cannot replay, so it doesn't seem to be due to any corruption.

Is there any way past the error, without alternate access to the remote?

-JimC
--
James Cloos <cloos@jhcloos.com>         OpenPGP: 0x997A9F17ED7DAEA6