How can I turn on client-side debugging? Are there any debug/trace
statements in the non-network related client side components?
I'd like to work on what I'm calling the "client, interrupted" bug. The bug
has been reported and discussed several times (google: svn interrupted is
not under version control) but from what I can tell no one has worked on it
or reported it in the official bug db. So I'm going to give it a try (-; I
know (from using wireshark) that the bug is likely entirely client-side in
the non-network checkout and/or cleanup code. I searched the bug db but
couldn't find it.
If anyone else recognizes and/or is working on this bug I'd like to hear
Client OS: WinXP or Vista (maybe others I don't know).
Client version: Latest command-line client (1.6.9?)
Server: 1.4.2 on Apache (as setup by Dreamhost at the moment)
Do an initial sync on a repository with multiple directories and small files
and also a large file in a subdirectory.
Interrupt the sync of the large file (ctrl-C or killing the window or
process, pulling the network cable, turning off wireless, etc)
Try to continue the sync using: svn update
The working copy is (correctly) reported as locked:
svn: Working copy '.' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for
Try to clean up the interrupted sync using: svn cleanup
The working copy is cleaned up properly and the sync can continue.
svn: In directory 'local\dir'
svn: Error processing command 'modify-wcprop' in 'local\dir'
svn: 'local\dir\file' is not under version control
Note that this is not the known issue about case-sensitivity (e.g., two
files with same name but different case). Also, moving or deleting the
reported subdirectory does not help. Doing that just moves the same error
up one directory level. The workaround is to delete the entire checkout and
This is a real issue since repositories can get big and it is unrealistic to
require the first checkout to succeed uninterrupted. For example, I keep
my personal files in a ~3GB repository. Syncing it down to a new laptop and
desktop has reproduced this bug 3X so far, because of interruption due to
intermittent wireless, auto-suspend, and having to take the laptop home.
Any suggestions? (-;
Citrix Systems, Inc
Received on 2010-03-18 17:40:40 CET