=== JoeGazz84|Vaca is now known as JoeGazz|Around === nhaines_ is now known as nhaines === johnoxton__ is now known as johnoxton === johnoxton__ is now known as johnoxton [18:24] here cjohnston [18:24] cprofitt: i have a bug for you if you like [18:24] sure. [18:29] cprofitt: bug #892436 [18:29] Launchpad bug 892436 in loco-team-portal "Broken link on http://loco.ubuntu.com/about/ (affects: 1) (heat: 8)" [Undecided,Confirmed] https://launchpad.net/bugs/892436 [18:31] what is the new url? [18:31] ~ltp-devs [18:34] I may have to work on this when I get home... [18:34] I do not have my keys on my work machine [18:34] thats fine.. [18:34] an easy way for getting you in and started though s what i figured [18:35] yes, then you can show me how to do the merge process [18:35] which is a step I have not done [18:35] not a problem [18:35] super easy [18:35] im not sure what my availability will be tonight but ping and ill try to be around [18:36] alright [18:36] I have a cub scout pack meeting to attend too [18:37] but I will try to ping you when I am free [18:38] wait... [18:39] cjohnston: is this the link on the wiki or inside the portal? [18:39] should be inside the portal [18:39] the team name changed [18:39] which should 404 alink or two [18:40] k [18:45] cjohnston, and cprofitt there are links to loco-directory-devs in the wiki too I think [18:45] svwilliams: ok.. if you guys run into them, please feel free to fix :-) [18:46] ok [18:49] cjohnston: I only found one example of that changed url [18:49] very possibly true [18:49] it was in /loco-directory/templates/about.html [18:50] we dont link to it alot afaik [18:50] and that is the right page [18:50] alright... so I will get setup at home later tonight and you can teach me the merge [18:50] the bzr part or the lp part or both [18:51] both [18:51] I have not done either [18:51] I should make sure I'm on for the lesson :-) [18:51] I haven't done it yet either [18:51] I know I have to change the file... then there is a process to upload it via bzr [18:51] svwilliams: you have done it all [18:52] you could teach it already [18:52] yup the light clicked on [18:52] i have the emails to prove it [18:52] he is talking about the up to lp [18:52] propose for merge [18:52] I was thinking a bzr merge [18:52] if that is even possible ... it is in git [18:52] ya.. he is talking about commit/push [18:53] ahh ok cprofitt if cjohnston's not on and I'm on I can try and help [18:53] I should be on tonight [18:53] sounds goog [18:53] good even [18:53] ;-) [18:53] I used bzr to pull the code... is it not on bazaar anymore? [18:54] cprofitt: it is [18:54] k [18:55] :-) sorry cprofitt we use git at work so I get confused by which system allows for each commands [18:55] all lp projects are bzr right? [18:55] except the kernal team [20:55] cjohnston: ping [20:55] sir [20:55] just about ready for some help if you have time [20:56] i have probably 8 minutes [20:56] looks like I need to make a new branch [20:57] ok.. so you already pulled it and made the changes? [20:57] pulled it, changes are seconds from happening [20:57] then you need to commit [20:58] bzr commit -m "enter text about your commit here" [20:58] then you would push [20:58] bzr push lp:~yourlpusername/loco-team-portal/some-name-or-bug-number-here [20:59] so if your working on bug # 123 bzr push lp:~cprofitt/loco-team-portal/123 would work [20:59] do I need to cd in to the loco-directory folder on my machien? [21:00] you can do it either in the directory that was created or the sub directories [21:00] its not specific [21:01] hmm... I get a connection error [21:02] * cprofitt looks at ssh keys [21:02] I wonder if I restored these [21:04] got that resolved [21:04] bzr: ERROR: Permission denied: "+branch/cprofitt/loco-team-portal/892436/": : Project 'cprofitt' does not exist. [21:04] do I need to register a branch first? [21:05] nvr mind [21:05] I see I was missing the ~ before my name [21:05] cjohnston: should be up ther enow [21:05] I see it [21:06] thanks for walking me through that [21:08] cjohnston: was that it? [21:10] mhall119: should I propose a merge or is that something you guys review and propose? [21:11] cprofitt: link it to the bug [21:11] then propose a merge [21:11] on the propse a merge page [21:11] there is a button for extra options [21:11] under extra options [21:11] fill out the commit message [21:12] i know it seems like your doing it twice, but if you have multiple commits to one branch, you need to do a commit message for the entire branch [21:12] we use Tarmac to do our merging for us, so without the commit message entered on LP, Tarmc wont work [21:15] k [21:16] do I choose a reviewer? [21:16] nope [21:16] and what do I fill out in the commit message? [21:16] just leave that blank [21:17] a description.. ex "Updated link to LoCo Team Portal Developers to reflect new URL." [21:17] * cjohnston is out [21:17] thanks cjohnston [21:17] if you have more questions, ill be back in a few hours [21:17] thank you cprofitt [21:17] sorry for rushing off [21:17] np === JoeGazz|Around is now known as JG84|Food