[SOLVED] Objscale git pull problems.

[Arius]

Hello I was trying to use objcscale script on my server, but when I do git pull I get errors with merging: http://pastebin.com/sEYPbj2i
I've also get errors.dif http://pastebin.com/5FcV18RQ

 

[Rochet2]

Can you post the output of the command git log?

Seems you have Eluna and Objscale. The errors seem to be caused at least partly from that.
Try getting the current commit's hash you are on and save it in case things go wrong.

You would need to manually solve the errors marked with these tags in the files:

<<<<<<< HEAD
// Code you have
=======
// Code the merged repo has
>>>>>>>

For the eluna conflicts it might be better to select the one with Eluna code (the first code block). (unsure if both work or both fail)
For the conflicts about code about modelids use the second code block.

After that see that there are no more conflicts and commit.
Then pull Eluna and try to solve any new conflicts.

When you want to try revert back to where you were, try using git reset --hard <yoursavedcommithash>

 

[Arius]

That's what I get with command git log: http://pastebin.com/C6m11tBD

 

[Rochet2]

Did you try the stuff I suggested?

Unsure if there are better ways .. but ..
Another way to do this is to abort any merge you made so far (git merge --abort)
Then do

git checkout -b update

git add -A
git reset --hard Eluna/master

git pull Rochet2/objscale

git checkout master
git merge update
git branch -D update

What this does is basically create a new branch, get the latest Eluna, merge latest objscale with it (and here you should merge any other stuff you use, like transmog, reforging .. whatever).
Then once all those are merged together, it changes back to the original branch and merges the update branch to it and then deletes the update branch.

 

[Arius]

Well I was trying to do it a way which you wrote in your last post, but sadly I get an error http://scr.hu/0j3a/q1sgi

 

[Rochet2]

Everything you do you should do in the source root folder.
What is this "build" folder? Sounds like it is the folder that contains the trinitycore.sln file, which is where you should not be executing commands at.