Major Description
Patch Submission by Jon Foster. COPIED FROM ORIGINAL EMAIL: Hi, As discussed on this list, we don't always need svnsync's networked lock. If svnsync only runs on a single server, the administrator can use the "flock" tool to prevent running multiple copies of svnsync at the same time. And if svnsync's lock is not needed, then it is actually an inconvenience. E.g. if the network connection fails, then a stale lock can be left behind. This requires manual administrator intervention to fix. One workaround is for your scripts to run this command immediately before they start svnsync: svn propdel svn:sync-lock --revprop -r0 $target_url However, it would be better to provide a command-line option to disable svnsync's locking. So, here's a patch to do that. The option name has been chosen to try to make it obvious that no locking is a bad idea, and administrators should either use svnsync's internal locking or have their own external locking.
Original issue reported by gavinbaumanis