On Fri, Apr 16, 2010 at 08:19:26PM -0400, Andersen, Krista wrote:
> I have run into the same "first" sync issue again today. This time it was on
> a commit that involved over 8000 paths. When I gave the sync command myself
> I got this error output:
> Transmitting file data . polka-dots
I have run into the same "first" sync issue again today. This time it was on a
commit that involved over 8000 paths. When I gave the sync command myself I
got this error output:
Transmitting file data .svnsync: REPORT of
'http://serverName/parentDirectory/repoName': Could n
Stefan Sperling wrote on Thu, 15 Apr 2010 at 21:02 +0200:
> svn pg --revprop -r 0 svnsync:last-merged-rev
You mean 'svn:sync-last-merged-rev'. And the same for the other
property names.
(One way to remember this is by noting they are under the reserved "svn:"
namespace.)
On Thu, Apr 15, 2010 at 07:10:00PM -0400, Andersen, Krista wrote:
> Do you know what SVN does now to detect and remove stale sync locks? Can
> this be related? Is it possible my first sync issue is from timing-out? Or
> perhaps it only appears to timeout from my command line client's point of
-Original Message-
From: Stefan Sperling [mailto:s...@elego.de]
Sent: Thursday, April 15, 2010 12:02 PM
To: Andersen, Krista
Cc: users@subversion.apache.org
Subject: Re: Sync Fail on svn 1.6.9
On Thu, Apr 15, 2010 at 02:09:21PM -0400, Andersen, Krista wrote:
> I have noticed some
On Thu, Apr 15, 2010 at 02:09:21PM -0400, Andersen, Krista wrote:
> I have noticed some odd sync behavior since we upgraded to 1.6.9 about four
> weeks ago.
>
> (Mostly we are pleased with the improved sync performance over 1.6.3 - yay!
> However...)
>
> First: I have seen commits involving a l
I have noticed some odd sync behavior since we upgraded to 1.6.9 about four
weeks ago.
(Mostly we are pleased with the improved sync performance over 1.6.3 - yay!
However...)
First: I have seen commits involving a large number (over 700 paths listed in
the log) of files fail with the output:
T
