Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.9.4
-
None
-
None
-
None
Description
As first mentioned in this users@-thread:
When making a directory depth=empty, svn is careful not to lose local modifications (modified files are left there as part of the sparse working copy – same for added files). However, local deletes are lost (and consequently also moves are broken, only the A+ is left). I think that's a bug. It makes it hard to confidently make a working copy more sparse.
Copy-pasting some reproduction transcripts from the users@-thread below:
Sparsification breaking a move:
C:\svntest>svnadmin create r C:\svntest>svn co -q file:///c:/svntest/r wc C:\svntest>cd wc C:\svntest\wc>touch iota C:\svntest\wc>svn add -q iota C:\svntest\wc>svn ci -q -m r1 C:\svntest\wc>svn up -q C:\svntest\wc>svn mv iota kappa A kappa D iota C:\svntest\wc>svn st D iota > moved to kappa A + kappa > moved from iota C:\svntest\wc>svn up --set-depth empty D iota Updating '.': Updated to revision 1. C:\svntest\wc>svn st A + kappa
Sparsification losing a simple delete:
C:\svntest>svn co file:///c:/svntest/r wc2 A wc2\iota Checked out revision 1. C:\svntest>cd wc2 C:\svntest\wc2>svn rm iota D iota C:\svntest\wc2>svn st D iota C:\svntest\wc2>svn up --set-depth empty D iota Updating '.': Updated to revision 1. C:\svntest\wc2>svn st