[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Bug: svn up file --depth empty

From: Dave Lawrence <dlawrence_at_ad-holdings.co.uk>
Date: Mon, 12 May 2008 18:21:28 +0100

To reproduce this problem:
1) Create a test repo
2) Set it up with a server (svnserve 1.4.5 in my case)
3) Add a file as <server url>/tests/test.txt
4) make a few revisions (3 will do) - make the text obviously indicate
the revision number
5) svn co <server url>/tests/ .
6) svn up test.txt -r1
7) svn up test.txt --depth empty

Now the working copy is broken. The file working copy and working base
are still at revision 1, the checksum is incorrect (presumably the
checksum is at the head revision). Errors such as "checksum incorrect"
and "delta ended unexpectedly" will result if trying to do further updates.

I originally saw this in TSVN - after I reported that Stefan changed a
use of "svn_depth_empty" to "svn_depth_files" and that particular
feature of TSVN now works OK (12885).

I don't know whether it is at all valid to update a single file with
depth set to empty, but it certainly shouldn't cause the working copy to
be corrupted.

Using svn.exe as built by the TortoiseSVN nightly build, from the head
revision of 1.5.x (a few days ago).

Windows XP SP2.

b.t.w this doesn't seem to happen with file:// protocol. I've seen it
with 2 different server configs:
1) Apache with svn 1.3.1 on Linux
2) svnserve 1.4.5 on Cygwin

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-05-12 19:22:06 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.