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

AW: Reversion of copied directories with depth != infinity

From: Markus Schaber <m.schaber_at_3s-software.com>
Date: Fri, 6 May 2011 10:48:50 +0200


> Von: Markus Schaber [mailto:m.schaber_at_3s-software.com]
> One current problem is that the revert command refuses to work on a
> directory with a depth different to infinity. This seems to be issue
> 3851[3]. There is written that "in most (all?) cases the user can use
> depth=infinity as an alternative".

I think I now found a case where depth=infinity is not an alternative.

Assume we are in a working copy, and have a non-modified directory tree

-- snip --

m.schaber_at_SCHABERM /cygdrive/d/testcheckout
$ svn cp foo bar
A bar

m.schaber_at_SCHABERM /cygdrive/d/testcheckout
$ svn status
A + bar

m.schaber_at_SCHABERM /cygdrive/d/testcheckout
$ touch bar/testfile

m.schaber_at_SCHABERM /cygdrive/d/testcheckout
$ svn status
A + bar
? bar/testfile

m.schaber_at_SCHABERM /cygdrive/d/testcheckout
$ svn propset svn:ignore testfile bar
property 'svn:ignore' set on 'bar'

m.schaber_at_SCHABERM /cygdrive/d/testcheckout
$ svn status
A + bar

m.schaber_at_SCHABERM /cygdrive/d/testcheckout
$ svn revert --depth=empty bar
svn: Try 'svn revert --depth infinity' instead?
svn: Unable to lock 'bar/innerdir'

-- snap --

Now, if we have other modifications inside bar, there is no way to
revert the change of the svn:ignore property without side effects.

Is there a workaround for this situation (working with the API of libsvn
1.6.16)? Maybe manually synchronizing the properties to the BASE state?

I'm just starting to look into svn:ignore support, and this problem
might hit me sooner or later.

Received on 2011-05-06 10:49:49 CEST

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

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