You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@subversion.apache.org by "Johan Corveleyn (JIRA)" <ji...@apache.org> on 2016/06/20 21:45:58 UTC

[jira] [Updated] (SVN-4636) Making working copy sparse loses local deletes / moves

     [ https://issues.apache.org/jira/browse/SVN-4636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Johan Corveleyn updated SVN-4636:
---------------------------------
    Description: 
As first mentioned in this users@-thread:
{quote}
http://svn.haxx.se/users/archive-2016-06/0077.shtml
{quote}

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:
{noformat}
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
{noformat}


Sparsification losing a simple delete:
{noformat}
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

{noformat}

  was:
As first mentioned in this users@-thread:
{quote}
http://svn.haxx.se/users/archive-2016-06/0077.shtml
{quote}

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:
{noformat}
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
{noformat}


Sparsification losing a simple delete:
{noformat}
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

{noformat}


> Making working copy sparse loses local deletes / moves
> ------------------------------------------------------
>
>                 Key: SVN-4636
>                 URL: https://issues.apache.org/jira/browse/SVN-4636
>             Project: Subversion
>          Issue Type: Bug
>    Affects Versions: 1.9.4
>            Reporter: Johan Corveleyn
>
> As first mentioned in this users@-thread:
> {quote}
> http://svn.haxx.se/users/archive-2016-06/0077.shtml
> {quote}
> 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:
> {noformat}
> 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
> {noformat}
> Sparsification losing a simple delete:
> {noformat}
> 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
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)