Re: GitHub svn bridge corrupting working copies
From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Sun, 15 Oct 2017 18:07:31 +0000
Ryan Schmidt wrote on Sun, 15 Oct 2017 12:49 -0500:
Have you looked at these commits? Is there anything unusual in them,
> I can "rm -rf kde && svn update kde" it, which restores it from the pristines, and then again fails to update it because of the corrupted node.
Have you also tried 'svn up -r0 kde' and 'svn up --set-depth=exclude kde'?
> I haven't tried to capture the network traffic. I haven't used such tools before, so I'm unfamiliar with them, and I can't reproduce the problem on demand so it seems problematic to try capturing all network traffic for days until the problem happens to occur.
Well, the next time you run into the problem, backup the working copy
You might be able to reproduce the problem by backdating your working
> Thanks for any suggestions you might have! (Other than "use the git client instead"; I've tried that for months and it doesn't seem to be compatible with my brain.)
If you're comfortable with rebuilding, you can try wrapping the "debug
This is an archived mail posted to the Subversion Users mailing list.