[11:30] <Silverlion> o/
[12:06] <popey> Hello!
[12:10] <Silverlion> popey: aloha
[12:12] <popey> hows things?
[12:13] <Silverlion> popey: pretty busy
[19:09] <silverlion> toddy ping?
[19:10] <toddy> silverlion: pong
[19:10] <silverlion> toddy excuse me ^^ are you from german loco team?
[19:10] <toddy> silverlion: yes, that is correct
[19:11] <silverlion> can we have a chat in query (german)? I'd like to join the loco team
[19:11] <toddy> yes, we can
[19:29] <balloons> silverlion, ping
[19:29] <silverlion> balloons, go ahead
[19:30] <balloons> silverlion, I was curious about 2 things. 1) would you like to be a track lead for the users track for UOS next week? 2) Any sessions you would like to propose for UOS?
[19:31] <silverlion> 2) I'm afraid I have to work so no time for sessions
[19:31] <silverlion> as to 1) the same
[19:32] <silverlion> if I'm lucky I could be online on nov 14 th (friday) evening so for me it's better not to take responsibility (yet)
[19:37] <balloons> silverlion, no worries :-)
[19:37] <balloons> thanks for letting me know
[19:38] <silverlion> balloons, I'll let you know when I'm available on friday
[19:38] <silverlion> if I can help - why not ;)
[19:38] <silverlion> but track lead is a little bit too much for me atm
[19:39] <balloons> silverlion, perfect, just let me know. A track lead isn't as scary as you think, you would not be the only one :-) The idea is to have several and good coverage in case people need help
[19:40] <silverlion> balloons, what would be my tasks as track lead?
[19:41] <balloons> silverlion,if presenters have trouble starting a presentation or get confused, you can help. You also can help schedule sessions if someone needs to move or change something
[19:42] <balloons> presenters now run there own sessions, so for you to host one for someone would be rare


[16:47] <ojwb> morning
[19:02] <ibeardslee> morning
[19:05] <mwhudson> morning
[19:25] <Atamira> morning
[19:37] <chilts> morning
[20:11] <mwhudson> Xorg is sure friends with my cpu a lot in quantal


[00:58] <OvenWerks> zequence: ubuntustudio-menudoes not seem to have been properly released... or the released version was not put back into https://code.launchpad.net/~ubuntustudio-dev/ubuntustudio-menu/ubuntustudio-menu
[00:59] <OvenWerks> The changelog says unrelesed since 2014-03-28 but the changes listed seem to be in the trusty menu.
[01:00] <OvenWerks> *unreleased
[01:05] <OvenWerks> The uploaded version is correct. It appears whoever uploaded it changed their local branch correctly and created the src package and uploaded it but never pushed the branch back.
[01:06] <OvenWerks> micahg: ^^^ should I fake it?
[01:07] <micahg> OvenWerks: that's what I usually do, apply the diff to the branch and commit/tag
[01:07] <OvenWerks> micahg: where would I get the diff from? would it just be the changelog?
[01:09] <micahg> pull-lp-source ubuntustudio-menu and diff the bzr branch against it
[01:09] <OvenWerks> micahg: it just seems to be the change of the word UNRELEASED to trusty.
[01:09] <micahg> against the unpacked source
[01:09] <micahg> ah, if that's it, just fake it :)
[01:10] <OvenWerks> Even the time stamp was not changed.
[01:10] <micahg> certainly makes it easier
[01:11] <OvenWerks> ok will do. I will have to make sure I check cahngelogs before I start tweaking...
[01:11] <micahg> diff from 0.18 to 0.19: http://launchpadlibrarian.net/171354168/ubuntustudio-menu_0.18_0.19.diff.gz
[01:14] <OvenWerks> micahg: So do I need to roll back 0.19 Unreleased to 0.18 and add the diff?
[01:14] <micahg> no
[01:14] <OvenWerks> Good
[01:16] <micahg> if you want to know if there's any difference, alternatively, you can bzr diff -rtag:0.18.. , output that to a file and diff against that change
[01:16] <OvenWerks> Looking through the diff you gave me, it is just the one word.
[01:17] <micahg> ok
[01:18] <OvenWerks> commit comment of "release version 0.19" is ok?
[01:19] <OvenWerks> micahg: ^
[01:19] <micahg> debcommit -r would do that for you
[01:19] <micahg> (and tag at the same time)
[01:20] <OvenWerks> Ah, already edited the file.
[01:20] <micahg> no, that's with the edited file :)
[01:21] <OvenWerks> right that worked just fine.
[01:22] <OvenWerks> micahg: Thank you for the help.
[01:22] <micahg> sure, no problem
[01:22] <OvenWerks> now I can make the fix I wanted to in thge first place
[01:23] <micahg> let me know if you need sponsorship
[01:24] <OvenWerks> Ok, I will. I am just starting though with fixes there are some changes that need a bit more discussion before I am finished.