Thorsten Schöning wrote on Tue, Jan 03, 2017 at 17:56:12 +0100:
> Guten Tag Daniel Shahaf,
> am Dienstag, 3. Januar 2017 um 16:02 schrieben Sie:
>
> >> > write(4, "( failure ( ( 160016 50:Pfad \302\273t"..., 86) = 86
>
> > In subversion/libsvn_ra_svn/protocol in the source tree.
>
> Does this te
Guten Tag Daniel Shahaf,
am Dienstag, 3. Januar 2017 um 16:02 schrieben Sie:
> It would have helepd to say what was being strace'd. It looks like the
> strace was of svnsync of r1397, run with the target repository accessed
> via file://.
Sorry, but your guess was correct. The sync source is svn
Thorsten Schöning wrote on Tue, Jan 03, 2017 at 13:56:34 +0100:
> Could you please be so kind and have a look at the following excerpt
> from strace?
It would have helepd to say what was being strace'd. It looks like the
strace was of svnsync of r1397, run with the target repository accessed
via
Hi all,
I'm dealing with the error mentioned in the subject currently. The
problem is present only for one repo out of dozens and this repo got
the last working commit yesterday, which has been successfully synced
some minutes later. Today a new commit was made to the source repo, I
can update to
