[beginner] updating via github

Glad it helped. As for the <master> thing, no idea?? Noticed that someone else posted somewhere with <origin>. I downloaded the full auriga zip so maybe that has something to do with it. Did you do this for the initial 'install' or did you use clone to download auriga?

Can't get it to say <master>, any ideas?

Think I have a problem with "logging in" to git bash. It says "Livingroom@Livingroom-PC" not "username@Livingroom-PC". Think I got this working earlier, anyone that can help?

Edit: As you probably understand, Livingroom isn't my Git username!

This thread is getting confusing with different people having different problems. There are several guides out there that will help you do this from the very beginning. Please try and start over with one of them (delete the "aeon" folder from the "skin" directory to start over), and if you still can't get it to work create a new thread documenting your attempt. I will try to find time today to write up a guide for the Git GUI and Git Bash on Windows today.

yazgar Wrote:Not sure if anyones gone through my walkthrough on page 2. Haven't had anyone say it didn't work though.

Thanks for the awesome guide, yazgar. I don't believe it is necessary to perform all of these steps, such as the key generation, however. Those steps are for users intending on contributing (and actually have permissions to push data to the server), and if someone is reading your guide for help setting git up, chances are they won't be contributing.

It should be as simple as installing msysgit, navigating to the skins directory, initializing the aeon repository, and pulling the data.

mojario Wrote:so i'm a bit stuck. also i was unable to have it say my directory with (master) after it.. not sure if thats of any concern


thanks for any help

May pay to wait for rickatnight11 to post his simplified guide mojario

Hey Mojario, Lets see if we can get this going for you and others. I haven't reread the older posts but lets start fresh anyway. First if you can just quote reply to this post and just fill in the answers to these questions so I can get an idea of where you're at. (I know some of them sound patronizing, pls don't be offended as that is not my intent, just don't want to miss something simple~ also it may help someone else who reads it.)

-running windows?

-what is the path that leads to your xbmc skin folder. ie c:program files\etc etc...\skin\

-Have you downloaded the auriga zip from the right place.



-have you downloaded and installed gitbash 1.6.2.2 ?

-if yes to the above, have you started gitbash and run the $ ssh-keygen -C "your@email.com" -t rsa command and then found / opened with notepad the .pub file it created.

-have you signed up on the github.com website? used the same email address as in gitbash and pasted the contents of the .pub file from notepad into the ssh box?

Lets just start with that.

Quote:Can't get it to say <master>, any ideas?

Think I have a problem with "logging in" to git bash. It says "Livingroom@Livingroom-PC" not "username@Livingroom-PC". Think I got this working earlier, anyone that can help?

Not sure where its pulling the "____"@livingroom-PC part from. Yazgar is the username I used to signup with github.com but its also my username on my laptop, on gitbash it has Yazgar@GAZ-PC ~ where GAZ-PC is my laptop network name. If you can navigate to your skin directory by typing something like $ cd C:/program files/xbmc/skin/auriga and then typing $ git pull git://github.com/djh/aeon.git auriga ,then it shouldn't matter too much.

Quote:It should be as simple as installing msysgit, navigating to the skins directory, initializing the aeon repository, and pulling the data.

I'd love to test this but after spending days getting it to work I'm not game. lol. Is that all you did, no ssh key or reg?

Quote:This thread is getting confusing...........Please try and start over with one of them (delete the "aeon" folder from the "skin" directory to start over), and if you still can't get it to work create a new thread documenting your attempt

Have to agree with rickatnight11, all the info is here, it maybe a matter of just stepping back and starting from scratch. ~Also feel free to copy/paste any of my previous post for that guide of yours if it helps.

Yeah, I didn't need to set up that info. It was just a simple clone and pull. I'm working on a guide right now that provides the minimum hassle to get things working. Will definitely use some your guide, thanks.

rickatnight11 Wrote:Yeah, I didn't need to set up that info. It was just a simple clone and pull. I'm working on a guide right now that provides the minimum hassle to get things working. Will definitely use some your guide, thanks.

Well that removes some of the harder steps. Distilling all this into a simplified guide should help lots. Good work.

Seems silly but I wanted to mention the mistake I made early on when trying to navigate to the skin directory in Gitbash. I was typing the path as windows explorer stated it - C:program files\xbmc\skin\auriga but in gitbash you have to use the / not \ ie C:program files/xbmc/skin/auriga. Spent an hour or more going in circles with that one. lol

Yeah, cross-platform standards will stickle you 'till the day you die.

rickatnight11 Wrote:Yeah, cross-platform standards will stickle you 'till the day you die.

I hear rumblings of Google releasing an OS. lol - "one ring to rule them all" perhaps.

So as not to go OT. Once you all have gitbash going, if you leave it running and want to check for a new update just use CTRL + P to save you retyping the whole git pull git://..blah..blah again.