Jump to content

SVN Files As "Conflicted"


Prodigal Son
 Share

Recommended Posts

I just updated my SVN version of the game after quite a while and got this warning:

Spoiler

5aa989002cb9f_Screenshot2018-03-1422_34_52.thumb.png.6231bc8b4e21422803a794dc9f512e5c.png

What I could trace with a quick search was map related, a couple like this one:

Spoiler

5aa988db2acac_Screenshot2018-03-1422_30_42.thumb.png.88e81e0dc2b865e9babfe5106600d459.png

Will those cause any issues and if so, what should I do?

 

 

Edited by Prodigal Son
Link to comment
Share on other sites

Merge conflicts only happen when you at one point patched your working copy, then updated it and the update changed the same files in the places you have edited. Than can include a leftover unrevisioned file.

If you want to preserve your diff, you have to carefully proofread it. If you weren't aware that there was a difference, you should revert your working copy regardless of the chosen merge resolve action. Should also look for unintentionally leftover unrevisioned files with the file "status" somewhere in tortoise.

  • Like 1
Link to comment
Share on other sites

6 minutes ago, elexis said:

Merge conflicts only happen when you at one point patched your working copy, then updated it and the update changed the same files in the places you have edited. Than can include a leftover unrevisioned file.

If you want to preserve your diff, you have to carefully proofread it. If you weren't aware that there was a difference, you should revert your working copy regardless of the chosen merge resolve action. Should also look for unintentionally leftover unrevisioned files with the file "status" somewhere in tortoise.

I'm kinda confused by the terms. Could you explain exactly what patched and (leftover) unrevisioned stand for in this case?

Link to comment
Share on other sites

unrevisioned files = files that aren't marked as part of the repository. like a new template that someone wanted to add sometime but wasn't actually added but you still got the file around.

patched file = file that differs from what is in the repository

Link to comment
Share on other sites

Since there were merge conflicts, it means that at some point in history you most likely changed something in your directory.

If you don't care about that anymore, just do a revert and delete unrevisioned files.

https://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-dug-revert.html

https://stackoverflow.com/questions/613485/how-can-i-get-tortoisesvn-to-get-a-list-of-files-that-are-not-in-the-repository

Link to comment
Share on other sites

@elexis Ty, makes sense now.

I guess it happened while modding (though that was in another folder) or working on patches/tickets a while back, but I don't remember messing with the specific files in conflict. What I can recall is something similar happening with mod versions from github, not from SVN. Those shouldn't affect the main game files/public mod either.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...