Igor Kromin |   Consultant. Coder. Blogger. Tinkerer. Gamer.

NOTE: This article is 3 years or older so its information may no longer be relevant. Read on at your own discretion! Comments for this article have automatically been locked, refer to the FAQ for more details.
I had the 'Node remains in conflict' error message come up recently due to an SVN update, this is how it's resolved. This error came about because I had a file in my local checkout that was not under version control, someone checked in a file with the same name into SVN. This should never have happened, the repository had its file deleted, yet every time I did an update, I got this error.

This is what the SVN output looked like:
Updating '.':
Skipped 'xxxxWS/xxxxWS.jpr' -- Node remains in conflict


To fix, just resolve with the working copy:
svn resolve --accept=working xxxxWS/xxxxWS.jpr


The error goes away after this and the local changes are not affected.



-i

Skip down to comments...
Hope you found this post useful...

...so please read on! I love writing articles that provide beneficial information, tips and examples to my readers. All information on my blog is provided free of charge and I encourage you to share it as you wish. There is a small favour I ask in return however - engage in comments below, provide feedback, and if you see mistakes let me know.

If you want to show additional support and help me pay for web hosting and domain name registration, donations, no matter how small, are always welcome!

Use of any information contained in this blog post/article is subject to this disclaimer.
 
comments powered by Disqus
Other posts you may like...