When I do a svn status .
, I get this:
! C auto-complete-config.elc
> local edit, incoming delete upon update
! + C auto-complete.elc
> local edit, incoming delete upon update
! + C popup.elc
> local edit, incoming delete upon update
! + C fuzzy.elc
> local edit, incoming delete upon update
basically, these files shouldn't be in the repository. A developer has removed them. Then, I think I did a svn rm ...
after the fact by mistake (should've done svn update .
instead).
So now, when I do svn status .
, I get these tree conflict messages.
I found the doc here but not sure how to “merge” it according to the doc.
How to get rid of them?
I think my working copy is in sync with the repository. Don't know why these messages shows. These files should be removed and are removed as far as I know everywhere. I tried svn update .
and svn revert .
but I still get this message when I do svn status .
.
This question is related to
svn
If you haven't made any changes inside the conflicted directory, you can also rm -rf conflicts_in_here/
and then svn up
. This worked for me at least.
This issue often happens when we try to merge another branch changes from a wrong directory.
Ex:
Branch2\Branch1_SubDir$ svn merge -rStart:End Branch1
^^^^^^^^^^^^
Merging at wrong location
A conflict that gets thrown on its execution is :
Tree conflict on 'Branch1_SubDir'
> local missing or deleted or moved away, incoming dir edit upon merge
And when you select q to quit resolution, you get status as:
M .
! C Branch1_SubDir
> local missing or deleted or moved away, incoming dir edit upon merge
! C Branch1_AnotherSubDir
> local missing or deleted or moved away, incoming dir edit upon merge
which clearly means that the merge contains changes related to Branch1_SubDir
and Branch1_AnotherSubDir
, and these folders couldn't be found inside Branch1_SubDir
(obviously a directory can't be inside itself).
How to avoid this issue at first place:
Branch2$ svn merge -rStart:End Branch1
^^^^
Merging at root location
The simplest fix for this issue that worked for me :
svn revert -R .
So you can just revert the file that you deleted but remember, If you are working on any type of project with a set project file (like iOS), reverting the file will add it to your system folder structure but not your project file structure. additional steps may be required if you are in this case
I just got this same issue and I found that
$ svn revert foo bar
solved the problem.
svn resolve did not work for me:
$ svn st
! + C foo
> local edit, incoming delete upon update
! + C bar
> local edit, incoming delete upon update
$ svn resolve --accept working
svn: Try 'svn help' for more info
svn: Not enough arguments provided
$ svn resolve --accept working .
$ svn st
! + C foo
> local edit, incoming delete upon update
! + C bar
> local edit, incoming delete upon update
$ svn resolve --accept working foo
Resolved conflicted state of 'foo'
$ svn st
! + foo
! + C bar
> local edit, incoming delete upon update
You can force to revert your local directory to svn.
svn revert -R your_local_path
Try to resolve the conflict using
svn resolve --accept=working PATH
Source: Stackoverflow.com