[01:35] <Akiva-Mobile> Is this possible: http://askubuntu.com/questions/259234/where-do-i-find-a-terminal-lens-for-unity
[01:36] <Akiva-Mobile> I want a command input where sudo actually works, and I don't have to open up the terminal.
[08:33] <didrocks> popey: you know what? sil2100 really rocks, current autopilot failures: 10 on nvidia, 9 on ati and 14 on intel :)
[08:33] <popey> woot
[08:33]  * popey looks forward to 0, 0, 0
[08:33]  * popey is a dreamer
[09:22] <mmrazik> didrocks:  remember the failing test for dict_union in cupstream2default.cfg ?
[09:22] <mmrazik> we are now hitting it :-)
[09:22] <mmrazik> https://bugs.launchpad.net/cupstream2distro-config/+bug/1137400
[09:22] <mmrazik> or rather a variation of that test-case
[09:23] <didrocks> mmrazik: I guess we should add a dict() around the call to ensure we don't have a set, but a dict type
[09:23] <didrocks> funny though :)
[09:23] <didrocks> mmrazik: I'm finishing something for the scope guys, they, I'll rereview the config FYI
[09:50] <didrocks> pstolowski: mhr3: hey, here we go: https://code.launchpad.net/~didrocks/libunity/add-json-scope-file/+merge/151168 and https://code.launchpad.net/~didrocks/unity/generate-recommends-from-default-scope/+merge/151170
[09:51] <didrocks> pstolowski: mhr3: hope you will like it, I had again to touch perl on a Friday, pwaaa :p
[09:58] <mhr3> didrocks, wrong target branch, we're using ~unity-team/libunity/libunity-7.0
[09:59] <mhr3> (the json file is already there)
[09:59] <mhr3> didrocks, can you try to merge it in that one?
[09:59] <didrocks> mhr3: hum, I want to have it right now in our current trunk so that we can have the unity branch merged
[09:59] <didrocks> mhr3: then, we can remerged against libunity-7.0, isn't it?
[10:00] <mhr3> oh, didn't notice the other one is for unity itself
[10:01] <didrocks> mhr3: so if you approve those, I'll then propose a version based on that for libunity-7.0
[10:01] <didrocks> mhr3: do you want trunk remerge against 7.0? maybe that what will make more sense
[10:03] <didrocks> while, I'm are it, free karma: https://code.launchpad.net/~didrocks/libunity/small-cleanup/+merge/151174
[10:03] <didrocks> popey: sil2100: ^
[10:03]  * popey looks up
[10:03] <mhr3> wow, i sooo don't get what does the perl thing do :P
[10:03] <didrocks> mhr3: I have no clue as well… OH WAIT! :-)
[10:03] <mhr3> some string concatenation, but what is in there...
[10:03] <mhr3> lol
[10:04] <didrocks> mhr3: yeah, parsing json in shell would have been better, if we could :p
[10:04] <didrocks> or python, but *meh*
[10:04] <popey> didrocks: done
[10:04] <didrocks> thanks popey :)
[10:04] <mhr3> didrocks, so just explain to me, how do those scope ids get in the json?
[10:05] <didrocks> mhr3: I think you will populate those as we discussed, right?
[10:06] <didrocks> the json is the place and only place when we put package -> scopenames for what we want to install by default
[10:06] <sil2100> No free karma for me :( ;)
[10:07] <mhr3> didrocks, let me check the doc that we wrote when we talked about this.. long time ago :)
[10:07] <didrocks> sil2100: you'll get a lot of karma for the appmenu/qt stuff :)
[10:07] <didrocks> sil2100: so, I think you can ping agateau
[10:08] <didrocks> sil2100: I'm sure he would be wanting to help us, even if he doesn't work here anymore :)
[10:08] <sil2100> didrocks: ok, will do!
[10:08] <sil2100> didrocks: btw. you had those corruptions when using qt5 staging, right?
[10:09] <didrocks> sil2100: when rebuilding the package here with the same change
[10:09] <didrocks> (it was before it hits staging)
[10:10] <didrocks> sil2100: but TBH, if we do have appmenu support, let's not care about the corruption
[10:10] <sil2100> didrocks: right, and anyway appmenu is rather high-priority by itself anyway
[10:11] <mhr3> didrocks, pstolowski, can we jump on a quick hangout?
[10:11] <didrocks> indeed :)
[10:12] <didrocks> mhr3: 5 minutes?
[10:12] <mhr3> k
[10:12] <didrocks> want to finish a review first
[10:21] <mhr3> pstolowski, ^
[10:28] <mmrazik> didrocks: I'll setup autolanding for cupstream2distro-config. There are too many branches with too many dependencies to merge manually
[10:29] <mmrazik> pushing changes in .cfg directly to trunk is IMO ok but if somebody needs/wants a MP then lets autoland it
[10:30] <mmrazik> didrocks: now when I see your comment on fginther's branch. cu2d-update-stack is not going to work with misc-head.cfg due to the window-mocker but I think that is a typo?
[10:31] <mmrazik> err... srry... it will work. It won't with one of the other MPs
[10:34] <didrocks> mmrazik: right, I answered on your other MP :)
[10:34] <didrocks> mmrazik: agreed on autolanding
[10:38] <mhr3> didrocks, btw will the json parser handle comments properly? would be nice to add some info to the json file itself
[10:39] <mhr3> hm, i don't even remember how to do comments in json :/
[10:39] <didrocks> mhr3: no comments are posible in json
[10:39] <mhr3> ah, that explains why i dont remember it :)
[10:39] <didrocks> :-)
[10:40] <didrocks> possible*
[11:03] <didrocks> mhr3: interesting, did you notice the merge test failure? https://jenkins.qa.ubuntu.com/job/libunity-ci/distribution=raring,flavor=amd64,label=pbuilder/27/console
[11:03] <didrocks> mhr3: I doubt it's the typo fix which changed that :p
[11:04] <mhr3> didrocks, yea, i thought it's something transient
[11:05] <didrocks> mhr3: happens on both and reliably it seems now, snif :(
[11:06] <mhr3> well, clearly it's not caused by your mp
[11:06] <didrocks> yep
[11:07] <mhr3> it's not like you touched any code
[14:14] <didrocks> mterry: if cyphermox is not around/available to look at the indicator stack, I think you can as well review the packaging changes and manually publish :)
[14:14] <mterry> cyphermox, you around?
[14:17] <didrocks> mterry: I was puzzled to see a compiz version, but all the parameters are fine in fact :)
[14:17] <didrocks> mterry: it's just that branch was merged yesterday, after the snapshot
[14:17] <mterry> didrocks, snuck in
[14:18] <didrocks> ;)
[14:23] <cyphermox> hey hey
[14:23] <cyphermox> yeah, let's publish indicators :D
[14:27] <mmrazik> didrocks, jibel: when you have some time: https://code.launchpad.net/~mrazik/cupstream2distro-config/lp1137330/+merge/151176
[14:28] <cyphermox> didrocks: mterry: any reason I should wait before publishing? (just checking)
[14:29] <mterry> cyphermox, no
[14:30] <cyphermox> ack
[14:30]  * cyphermox pushes the button
[14:31] <cyphermox> ... and there was much rejoicing
[14:31] <cyphermox> didrocks: libcolumbus transition! :D
[14:40] <cyphermox> ok, so all we're waiting for is for hud to pull libcolumbus into main, the MIR is already approved
[15:08] <mhr3> mmrazik, any way to get more info on https://code.launchpad.net/~didrocks/libunity/add-json-scope-file/+merge/151168 ?
[15:08] <mhr3> the failure doesn't make much sense really
[15:10] <mmrazik> mhr3: those are your tests, you should be able to make them more verbose :-)
[15:10] <mmrazik> but seriously -- don't really know
[15:10] <mmrazik> I guess gtester might have some verbose mode?
[15:10] <mhr3> can we just try re-running them until they succeed? :)
[15:10] <mmrazik> I would try to reproduce locally in pbuilder first
[15:10] <mhr3> i tried, works fine, that branch didn't even touch any real code
[15:11] <mmrazik> mhr3: I guess you can try re-approve but it won't fix a flaky test
[15:12] <mhr3> the way i see it, the failure it mentions can only happen if malloc fails
[15:12] <mhr3> or glib is broken... or something
[15:33] <j-johan-ewards> Hey everyone.... what's the chance that lp:unity/phablet will supplant the nux version?
[15:34] <j-johan-ewards> I just saw a comment from smspillaz to that effect on /r/linux
[15:34] <j-johan-ewards> Was thinking of scratching an itch or two, but... is it worth the effort?
[15:45] <didrocks> fginther: hey, is lp:compiz/raring really configured for autolanding? https://code.launchpad.net/~ps-jenkins/compiz/latestsnapshot/+merge/151239 isn't merged
[15:45] <didrocks> mterry: ^
[15:47] <fginther> didrocks, I'll take another look
[15:47] <didrocks> thanks
[15:59] <fginther> didrocks, I was able to manually fire the job. it is merged now
[16:00] <didrocks> thanks fginther
[16:49] <mmrazik> didrocks: what should I do with https://code.launchpad.net/~mrazik/cupstream2distro-config/qa-stuff/+merge/151229 once it has landed?
[16:49] <mmrazik> the stacks needs to be regenerated, I assume
[16:50] <mmrazik> who should do that?
[16:50] <mmrazik> (just trying to figure out a process when I'm touching stuff that I don't necessarily own)
[16:51] <didrocks> mmrazik: I would do that as we need to cleanswap/remove the old jobs. But I want to discuss first with cyphermox
[16:52] <didrocks> mmrazik: so you can merge it, this won't change for me until we redeploy
[16:52] <mmrazik> didrocks: ok
[16:55] <cyphermox> what's up?
[16:55] <didrocks> mmrazik: look at the MP, basically, spreading the misc between a "qa" one and a "misc" one
[16:55] <didrocks> oupss
[16:55] <didrocks> cyphermox: ^
[16:56] <didrocks> cyphermox: is that fine with you?
[16:57] <cyphermox> sure
[16:57] <cyphermox> I follow both?
[16:57] <didrocks> cyphermox: yeah, it's still the same components
[16:57] <didrocks> just split
[16:57] <cyphermox> all good
[16:57] <didrocks> cyphermox: do you want me to redeploy once it's merged?
[16:58] <mmrazik> it has merged, btw
[16:58] <cyphermox> sure, feel free
[16:58] <didrocks> ok
[16:58] <didrocks> I need to delete the other manually