[00:36] <sergiusens> thomi, the test from lp:autopilot fail for me
[00:37] <thomi> cjwatson: yes, I suspect this is a naming collision. Sorry if I caused any confusion
[00:37] <thomi> sergiusens: which ones, and how? also, perhaps #ubuntu-autopilot is a better channel for this?
[00:37] <sergiusens> thomi, http://paste.ubuntu.com/6747837/
[00:38] <thomi> sergiusens: do you have all the build-deps installed?
[00:38] <thomi> looks to me like you're missing python-junitxml and/or python3-junitxml
[00:38] <sergiusens> thomi, I did apt-get build-dep python-autopilot
[00:39] <sergiusens> thomi, that was it.
[00:39] <thomi> sergiusens: that will get the build-dep for autopilot in archive
[00:39] <thomi> sudo mk-build-deps -i
[00:39] <thomi> is the magic you want :)
[00:45] <cjwatson> thomi: ok
[07:33] <Saviq> ev, no, I did not
[09:33] <ev> Saviq: fginther is still looking into it: https://app.asana.com/0/8736198969650/9504356304887
[09:34] <ev> psivaa: I'm getting alerts on PD for wazn-adt - can you have a look?
[09:38] <Saviq> ev, yes I saw, thanks
[09:39] <psivaa> ev: i'm on it
[09:39] <ev> thanks guys
[09:52] <psivaa> ev: ok, i was unaware that the acknowledgement will be unacknowledged if that's not resolved within 30 mins.  may be it's better to increase that timeout to reduce the hassle to you
[09:52] <psivaa> that's now resolved btw
[09:59] <ev> psivaa: no, I definitely want to know if no one has ack'ed it within 30 minutes
[09:59] <ev> and whoop! thanks
[10:02] <psivaa> ev: i acked at 0903 but that got unacked at 0933 because it was n't resolved. but fine if you want to keep it that way
[10:03] <psivaa> not sure if we'll be able to resolve all the issues within 30 mins after ack'ing
[10:03] <ev> oh, right
[10:03] <ev> I see your point now
[10:03] <psivaa> :)
[10:03] <ev> retoaded: any thoughts on what we should do here? Should the policy be to downtime the check in nagios when you're investigating and it'll take more than 30 minutes?
[11:21] <davmor2> rsalveti: bug updated with the unity8.log and unity8.log.1.gz I'm assuming the latter will contain yesterdays log but I put them both up to be sure :)
[11:29] <davmor2> didrocks: any images you plan on promoting today?  I spent yesterdays time digging into the app failing to start.  :(   on a plus side looks like it is only maguro and might explain the random failures again.  Me can't wait for his n4 to arrive now :)
[11:30] <didrocks> davmor2: there is a rssreader promoition
[11:30] <didrocks> sorry, reformulating
[11:30] <didrocks> davmor2: there is rssreader AP tests failure blocking promotion
[11:33] <davmor2> didrocks: okay I don't want to upgrade just yet incase rsalveti needs me to look at anything else.  So I'll leave testing till latter on then :)
[11:34] <didrocks> ok
[11:37] <retoaded> psivaa, ev. I don't think it's so much that the acknowledgement gets unacknowledged as it is that nagios sends another alert to PD when it runs it's check again and the issue is still there.
[11:39] <ev> retoaded: yeah, but wouldn't scheduling downtime for the alert in nagios fix psivaa's problem?
[11:39] <ev> I'd agree that PD is probably not the right place to say "this is going to take a while"
[11:40] <ev> though I'd also agree that having to perform some tasks in PD and others in nagios isn't ideal :)
[11:40] <retoaded> ev, as for policy in cases like this, hmmm ..... Most issues we see are able to be resolved quickly. Since there are some that can't be then we would need to/should a) add a comment to the incident in PD and b) schedule the downtime in nagios to prevent repeated alerts for an issue already being worked.
[11:46] <ev> retoaded: can I ask that you hijack https://wiki.canonical.com/UbuntuEngineering/CI/Alerting for this, filling it out with what you've just said and also the instructions for scheudling downtime?
[11:46] <retoaded> ev, sure
[11:47] <ev> star, thanks!
[12:21] <ev> retoaded: not sure how useful too many users logged in is
[12:21] <ev> in nagios, that is
[12:24] <retoaded> ev, from my perspective, more people logged in = more chance something could get broken. It's about the only thing I take the pessimistic view on
[12:24] <ev> :)
[12:24] <ev> fair enough
[12:25] <retoaded> ev, although I will admit the default nagios check is bs. It gives total logins instead of unique logins. Might be the first candidate for a plugin to fix or replace
[12:27]  * ev nods
[12:29] <sil2100> Who here has an Ubuntu tablet?
[12:30] <popey> sil2100: which model?
[12:30] <sil2100> popey: any I guess, just something that would be a tablet form-factor
[12:31] <popey> so nexus 10 then.
[12:32] <ogra_> you mean nexus7 doesnt qualify for tablet formfactor ?
[12:32] <ogra_> (you should tell that to the deciders that will make us drop everything but N4 and N7 ;) )
[12:33] <sil2100> ;)
[12:39] <sil2100> Well, I just need someone with a N7 or N10 to test a package for me
[12:59] <sil2100> Who here has a N7 or N10?
[13:29] <sil2100> didrocks: hmm... would it be somehow possible that the intel machine's otto didn't use the latest desktop image?
[13:30] <sil2100> Wait
[13:31] <sil2100> didrocks: actually yes, I see that the intel machine uses trusty-i386-20140113-0008 while nvidia already trusty-i386-20140114-0008 <- who should I ping to get this resolved?
[13:31] <sil2100> vila: ^ ?
[13:32] <vila> sil2100: cihelp's vanguard is cjohnston right now ;)
[13:33] <sil2100> vila: ok ;) Just remembered that you had experience with otto and q-jenkins
[13:33]  * cjohnston has no experience with that stuff
[13:33] <sil2100> cjohnston: ^ could you maybe take a look why intel in otto still uses the previous image?
[13:33] <vila> sil2100: yup, but we try to disseminate that knowledge through the vanguard rotation
[13:34] <vila> cjohnston: most of the knowledge should be documented in https://wiki.canonical.com/UbuntuEngineering/CI/Playbook/Otto
[13:35] <cjohnston> vila: that's where I'm lookin
[13:35] <cjohnston> ty
[13:35] <vila> cjohnston: yw
[13:37] <cjohnston> sil2100: I'll log this and attempt to chase it down
[13:50] <sil2100> cjohnston: thanks!
[14:07] <elopio> ping ci-help: so, for running tests using the OSK we need to restart maliit with testability.
[14:08] <elopio> this can be similar to how we run unity8 tests, that assumes unity is not running, and it's started on each test.
[14:08] <elopio> but I don't know where is the code that kills unity8 for jenkins. Can I get some help copying that for the maliit case?
[14:11] <didrocks> sil2100: yeah, the CI team should be your contact
[14:13] <vila> elopio: cihelp not ci-help or nobody will notice ;) And you should should ping the vanguard indicated in the topic line. And hi and Happy New Year !
[14:14] <elopio> thanks vila. Happy New Year for you too.
[14:14] <elopio> and ping cjohnston.
[14:16] <cjohnston> elopio: looking
[14:16] <fginther> morning
[14:18] <cjohnston> fginther: any suggestions on elopio's request?
[14:18] <fginther> elopio, have you tried asking in #ubuntu-unity to see what unity8 is doing?
[14:18] <elopio> fginther, cjohnston: there's a process_helper.py on unity that's what I'm going to copy to ubuntu-keyboard.
[14:18] <elopio> the part that I'm missing is how to make sure maliit is not running.
[14:19] <elopio> I can ask them.
[14:19] <fginther> elopio, cjohnston, I know that there is a unity8 restart in our test runner, but I recall this might no longer be the right way to do it
[14:19] <kenvandine> i need to head out for a bit, i might not be back in time for the meeting
[14:19]  * kenvandine waves
[14:19] <fginther> elopio, does OSK only need to be restarted for OSK tests or for all tests?
[14:20] <elopio> fginther: eventually, for all tests. For now, only for ubuntu-ui-toolkit tests.
[14:20] <fginther> elopio, hmmm
[14:21] <elopio> fginther: there are alternatives, but I thought that what unity was doing was the right way according to CI.
[14:21] <ogra_> note that the maliit upstart job depends on unity8 running
[14:21] <ogra_> might be a bit trickier than the unity case
[14:23] <elopio> ogra_: but we always have unity8 running, where's the tricky part?
[14:23] <fginther> elopio, it's not such a big deal how its done, it's just something we (unity8, OSK, and CI) need to get right and agree upon
[14:26] <elopio> fginther: do you think we can agree on something this week? Should I start pinging people to discuss about it?
[14:32] <sil2100> popey: do you have an N7? ;)
[14:32] <sil2100> (or any other UT enabled tablet?)
[14:34] <fginther> elopio, yes, I don't think agreeing upon a method should be too much work
[14:38] <popey> sil2100: both my N7's are android atm
[14:39] <elopio> bfiller, Saviq: I think you are the ones that should be involved in that discussion ^^, re: restarting services with testability enabled.
[14:39] <elopio> please, point somebody else if I'm wrong :)
[14:40]  * popey afk
[14:41] <Saviq> elopio, yeah, that's probably me
[14:50] <rsalveti> davmor2: I'd check the bug with ricmm_, as it seems to be app lifecycle related
[14:50] <rsalveti> davmor2: updated the bug as well
[14:52] <davmor2> rsalveti: great thanks
[14:53] <sil2100> cihelp: does anyone from the CI team have a tablet with UT installed?
[14:53] <cjohnston> sil2100: I think balloons has a N10
[14:59] <davmor2> ricmm_: https://bugs.launchpad.net/bugs/1268693 rsalveti has asked me to run this past you.  On the maguro there is an issue possibly caused by constantly opening and closing an app that at some point in a test run the app locks up with just the grey app holder visible.
[15:04] <sil2100> cjohnston: thanks, will poke him then
[15:04] <sil2100> balloons: hi! Are you around already?
[15:12] <sergiusens> didrocks, sil2100 can we add http://paste.ubuntu.com/6748287/ to the release plan? I forward ported to trunk as well  (https://code.launchpad.net/~sergiusens/autopilot/app_uris/+merge/201525 veebers said the code was fine)
[15:12] <sergiusens> not sure when trunk is happening; but we need that for gallery and media player
[15:13] <didrocks> sergiusens: trunk release should come within the week, can we just wait for it?
[15:13] <sergiusens> I tested btw, and bfiller might do that as well
[15:13] <sergiusens> didrocks, ask bfiller  :-)
[15:14] <didrocks> bfiller: ? ^
[15:14] <sergiusens> didrocks, I don't trust ETA's from anyone any more ;-)
[15:14] <didrocks> sergiusens: well, just look at the still failing AP tests for instance, I agree with you :)
[15:15] <didrocks> balloons: hey btw, any news on rss reader app? it's what is blocking image promotion FYI
[15:15] <sergiusens> didrocks, fwiw, I don't even trust my own ETAs ;-)
[15:16] <didrocks> ahah ;)
[15:16] <sil2100> ;)
[15:17] <ricmm_> davmor2: that sounds like a race with upstart app launcher
[15:17] <ricmm_> where an app hasnt finished being stopped by the time you ask it to start the new one
[15:18] <ricmm_> in which case the app manager gets out of sync, because it assumes that upstart has done its job
[15:18] <ricmm_> however maguro is slow
[15:19] <davmor2> ricmm_: could well be
[15:20] <balloons> sergiusens, lol
[15:21] <balloons> didrocks, no good news to pass along, sorry mate
[15:21] <didrocks> balloons: it's the priority one? do we know where this regression come from?
[15:22] <balloons> no changes have been released with rss reader
[15:22] <didrocks> balloons: but you are working on digging it, right?
[15:22] <balloons> yes, I'm attempting to tweak things anyway ;-)
[15:23] <didrocks> balloons: so, it started on image 122, let me get you the diff
[15:24] <didrocks> I thought it was the python-gobject issue, but even with the revert, it didn't change
[15:24] <didrocks> balloons: quite a huge diff: http://people.canonical.com/~ogra/touch-image-stats/20140110.1.changes
[15:24] <didrocks> balloons: I'm seeing some openssl change, I would suggest that you try to revert it on your device and rerun the tests
[15:25] <balloons> hmm.. I just saw the ssl change as well
[15:25] <didrocks> that's my best guess from the list
[15:26] <sil2100> cjohnston: hi! Any luck with otto and the image?
[15:27] <cjohnston> fginther: ^
[15:28] <fginther> sil2100, sorry, too many fires this morning
[15:29] <bfiller> sergiusens, didrocks : sorry was on standup, what is the question?
[15:35] <fginther> sil2100, cjohnston the update job (http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-setup_otto/83/) failed on the intel node. Looks like jenkins couldn't connect to the node.
[15:35] <fginther> sil2100, I've manually updated the node, it should be on a trusty-i386-20140114-1534 container now
[15:35] <sil2100> fginther: oh, was that a singular failure? Thanks!
[15:36] <fginther> sil2100, yes, it appears to be an isolated failure, but one I've never seen before
[15:39] <didrocks> bfiller: it seems the gallery and media player needs an autopilot backport. As autopilot is getting released this week normally, I wonder if you can wait on that one rather than backporting the AP changes (which involves quite a lot of overhead)
[15:39] <bfiller> didrocks: yes we can wait
[15:44] <didrocks> thanks ;)
[15:49] <sergiusens> didrocks, so if I go to devel proposed the rss reader app should be broken, right?
[15:51] <ogra_> yes
[15:52] <didrocks> sergiusens: yeah, it is, balloons is trying to fix it
[15:52] <ogra_> well, the tests should be ... not sure the app exposes any breakage :)
[15:57] <sergiusens> ogra_, didrocks who do I talk to about stuff stuck in proposed due to dependencies?
[15:58] <ogra_> depends
[15:59] <ogra_> :)
[15:59] <ogra_> whats the issue with the dependencies ?
[15:59] <ogra_> if they are stuck, #ubuntu-release, if they are wrong in the package  the package maintainer
[16:03] <cjwatson> #ubuntu-release is generally happy to help you diagnose such things
[16:03] <sergiusens> ogra_, I'm the mintainer; there's just no android emulator for arm* :-)
[16:03] <ogra_> just create one then :P
[16:04] <ogra_> so we can run it on the chromebooks :)
[16:04] <cjwatson> I can't obviously see anything to do with android that's stuck in -proposed
[16:26] <sil2100> fginther, doanac: it seems the jenkins intel otto node is down
[16:26] <sil2100> Could anyone reanimate it?
[16:26] <fginther> sil2100, looking
[16:27] <fginther> sil2100, oops, left it offline when I was doing the manual lxc update
[16:27] <fginther> sil2100, doanac it's online now
[16:29] <sil2100> Thanks :)
[16:32] <sil2100> didrocks: are your free for some packaging ACKs?
[16:35] <sil2100> kenvandine: hey! Maybe you have some free moments right now?
[16:38] <sil2100> ogra_: could you ACK some packaging changes for me before releasing?
[16:38] <sil2100> http://q-jenkins.ubuntu-ci:8080/view/cu2d/view/Head/view/Unity8/job/cu2d-unity8-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity-mir_0.2+14.04.20140114.1-0ubuntu1.diff <- cmake switch
[16:38] <ogra_> sure
[16:39] <ogra_> hmpf, i have no vpn set up here
[16:39] <sil2100> http://q-jenkins.ubuntu-ci:8080/view/cu2d/view/Head/view/Platform/job/cu2d-platform-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_platform-api_0.20+14.04.20140114.1-0ubuntu1.diff <- test package addition, but pitti seemed to work on that so I say safe ;p
[16:39] <sil2100> http://q-jenkins.ubuntu-ci:8080/view/cu2d/view/Head/view/Platform/job/cu2d-platform-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_qtubuntu_0.53+14.04.20140114.1-0ubuntu1.diff <- double build changes
[16:39] <ogra_> i cant get to them
[16:39] <sil2100> hmmm, let me see if they're on the public jenkins
[16:40] <sil2100> Ah, here they are, one moment
[16:40] <sil2100> https://jenkins.qa.ubuntu.com/view/cu2d/view/Head/view/Platform/job/cu2d-platform-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_qtubuntu_0.53+14.04.20140114.1-0ubuntu1.diff
[16:40] <sil2100> https://jenkins.qa.ubuntu.com/view/cu2d/view/Head/view/Platform/job/cu2d-platform-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_platform-api_0.20+14.04.20140114.1-0ubuntu1.diff
[16:40] <sil2100> jenkins.qa.ubuntu.com/view/cu2d/view/Head/view/Unity8/job/cu2d-unity8-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity-mir_0.2+14.04.20140114.1-0ubuntu1.diff
[16:41] <sil2100> Ah, the last one is not there...
[16:41] <sil2100> Let me pastebinit
[16:42] <ogra_> heh "GNU-based desktops"
[16:42] <didrocks> sil2100: in meetings
[16:42] <sil2100> ogra_: here's the unity-mir one: http://paste.ubuntu.com/6751346/
[16:43] <ogra_> sil2100, hmm, afaik pitti had issues with the platform-api fix and needed a qemu patch first
[16:43] <ogra_> do you know if he fixed that already ?
[16:44] <ogra_> sil2100, apart from that packaging wise it looks fine
[16:44] <ogra_> ACK
[16:44] <sil2100> I don't know, I just know that platform-api works fine on the devices right now
[16:45] <sil2100> ogra_: thanks!
[16:45] <ogra_> yeah, but it fails the tests in cross envs iirc
[16:45] <ogra_> (you cant build it in sbuild cross or pbuilder cross with that)
[16:46] <davmor2> ogra_: gnu-based desktops, is that were you cause a stampede to speed up the processing.
[16:46] <ogra_> davmor2, heh, likely
[16:46] <ogra_> if you get them fast enough you win a stallman for home
[16:47] <davmor2> ogra_: no you don't want it to stallman you'll never get it to go again man
[16:47] <ogra_> heh, *I* surely dont want a stallman for home
[16:47]  * ogra_ herad stories
[16:47] <cjwatson> why is platform-api running tests in cross envs at all?
[16:48] <ogra_> cjwatson, ask pitti/tvoss
[16:48] <cjwatson> usually cross-builders disable tests
[16:48] <ogra_> they were the ones complaining about missing qemu syscalls
[16:48] <cjwatson> ogra_: I don't care enough to chase it down :)
[16:48] <ogra_> (which they hit and thus make their tests fail)
[16:48] <cjwatson> missing qemu syscalls sounds more like PPAs ...
[16:49] <ogra_> that too
[16:49] <cjwatson> our normal cross-building infra these days doesn't involve qemu
[16:49] <ogra_> well, pitti was using sbuild i think
[16:50] <ogra_> not sure though, we only discussed the qemu patch i gave them
[16:50] <cjwatson> sbuild disables tests when cross-building
[16:50] <ogra_> ah
[16:50] <cjwatson> assuming the package honours DEB_BUILD_OPTIONS=nocheck
[16:56] <cjwatson> well, platform-api is blocked for cross-building anyway due to the usual problem with non-trivial toolchain dependencies plus some other random bits of multiarch metadata that I haven't chased down
[16:57] <ogra_> then it is fine
[16:57] <ogra_> as long as PPAs dont fail
[16:59] <cjwatson> that's an entirely different question, haven't checked
[16:59] <cjwatson> of course devirt PPAs won't care about qemu anyway
[16:59] <sergiusens> didrocks, robru can you check https://code.launchpad.net/~sergiusens/goget-ubuntu-touch/package_arch/+merge/201628 ?
[17:01] <didrocks> will be there in 2 minutes
[17:02] <balloons> didrocks, sent along a mail with the updates.. I'm going to keep working on this stuff.. lots to do atm
[17:07] <robru> sergiusens, in a meeting, will check it in ~30
[17:10] <ogra_> sergiusens, approved
[17:11] <ogra_> (trivial enough, especially after seeing the discussion in #ubuntu-release)
[17:11] <sergiusens> balloons, I ran the clock app in the amulator yesterday, I had no issues
[17:11] <sergiusens> well, aside from thrashing :-)
[17:11] <balloons> sergiusens, ty. I was going to try again at some point.. I haven't done so with the updates
[17:12] <balloons> sergiusens, actually I was hoping you could try and land the calendar
[17:12] <balloons> you have a maguro right?
[17:12] <sergiusens> balloons, I have a mako now ;-)
[17:13] <sergiusens> balloons, maguro is dead, long live mako
[17:13] <balloons> sergiusens, well, whatever: https://code.launchpad.net/~nskaggs/ubuntu-calendar-app/fix-test-timing-issues/+merge/201120
[17:14] <sergiusens> balloons, is that you requesting me to check that? :-D
[17:15] <balloons> sergiusens, if you would. If it works for you too, and blast those maguro's anyhow, let's just merge it.
[17:15] <balloons> I need to move on to other things
[17:15] <sergiusens> balloons, I can test on the emulator as well, it's slow enough :-)
[17:16] <balloons> ty sergiusens
[17:16]  * balloons crosses fingers
[17:17] <didrocks> balloons: excellent! thanks a bunch :)
[17:17] <didrocks> sergiusens: feel free to land whatever balloons is giving you if this fix the AP tests flakyness btw
[17:29] <didrocks> dobey: any reason why ubuntu-purchase-service is priority extra and not optional?
[17:30] <didrocks> no COPYING/LICENSE file in tarball
[17:31] <didrocks> robru: I'm going to reject the NEW package, can you get those fixed? (mostly for the missing license file) ^
[17:34] <didrocks> robru: please get those changes in and rebuild a new package + get some ack for the change (only ubuntu-purchase-service)
[17:44] <robru> didrocks, well dobey did revert all my packaging work.
[17:45] <dobey> robru: which was none of the things didrocks just mentioned
[17:45] <didrocks> can you guy get those done and move on, please? ;)
[17:45] <didrocks> guys*
[17:45] <robru> k, i'm submitting a branch.
[17:45] <didrocks> thanks!
[17:45] <dobey> didrocks: i copied the debian/ dir from another project that's already in ubuntu and editied, so extra would have come from that
[17:46] <dobey> didrocks: not sure what you mean about the license file and tarball though.
[17:46] <didrocks> dobey: no COPYING/LICENSE GPL3 file, better to include it in tarball
[17:46] <dobey> oh, there isn't one in trunk. huh
[17:46] <didrocks> ah, it's not in the package I reviewed
[17:47] <didrocks> so not sure which version is was based on
[17:47] <dobey> didrocks: right. it's a native package though. so "tarball" confused me :)
[17:47] <didrocks> dobey: hum, bzr branch lp:ubuntu-purchase-service
[17:47] <didrocks> no COPYING or LICENSE here
[17:48] <robru> didrocks, https://code.launchpad.net/~robru/ubuntu-purchase-service/didrocks-new/+merge/201635
[17:48] <dobey> didrocks: right, i just looked
[17:48] <didrocks> robru: approved
[17:48] <didrocks> robru: once merged, can you kick another one and just publish it? (it's a +1 on the packaging change ;))
[17:48] <dobey> slow down :)
[17:52] <robru> dobey, ... no
[17:53] <dobey> yes
[17:53] <robru> dobey, i think you approved the wrong one...
[17:53] <dobey> no
[17:54] <dobey> the tree contains LGPL-3 code as well, so it needs COPYING and COPYING.LIB
[17:54] <robru> dobey, in that case, debian/copyright also needs to be updated, to identify where the lgpl code is
[17:54] <dobey> ok
[17:55] <dobey> didrocks: sorry i totally overlooked this. too much going on :)
[17:56] <robru> dobey, indeed I see a bunch of files by grepping for 'Lesser'. want me to just add it to my merge or are you doing it?
[17:56] <dobey> robru: you can add it to your merge
[17:57] <robru> dobey, ok
[17:57] <dobey> no point making 2 branches to fix the same thing
[17:57] <didrocks> thanks guys, and please fix debian/copyright :)
[17:58] <didrocks> (I didn't run license-check -r * --copyright when I saw the missing copyright file)
[18:03] <robru> dobey, is any of this actually GPL? why don't we just make the whole package LGPL?
[18:05] <ahayzen> Hi, I made some changes to a branch 5 hours ago and Jenkins hasn't kicked in any ideas wht is going on? https://code.launchpad.net/~andrew-hayzen/ubuntu-ui-toolkit/fix-swipe-delete-001/+merge/199906
[18:05] <dobey> robru: the qml/UbuntuPurchase.qml is GPL3
[18:05] <robru> dobey, ok then. https://code.launchpad.net/~robru/ubuntu-purchase-service/didrocks-new/+merge/201635
[18:05] <robru> didrocks, ^
[18:06] <dobey> now to wait for jenkins to approve it
[18:07] <didrocks> great
[19:44] <thomi> cjohnston: any chance you could build flake8 for trusty here? https://launchpad.net/~cjohnston/+archive/flake8
[19:44] <thomi> cjohnston: oh wait, I see it's in the archive now, nvm. I wonder when that happened
[19:44] <cjohnston> :-)
[19:45] <cjohnston> I was lookin, you had me stumped
[19:45] <thomi> I can stop installing it into virtualenvs now :)
[21:59] <sergiusens> robru, had you had a chance to happrove my MR?
[22:13] <balloons> sergiusens, before I get any farther along, can you have a peek at https://code.launchpad.net/~nskaggs/phablet-tools/add-lp-branch-support/+merge/201685 and give me your opinion
[22:15] <sergiusens> balloons, heh, just did ;-)
[22:15] <sergiusens> added a comment
[22:15] <sergiusens> balloons, we should migrate all the apps to cmake imo; even if we don't compile anything
[22:15] <sergiusens> that way we can keep building the deb and the click with one ruleset
[22:16] <balloons> hmm..
[22:17] <sergiusens> balloons, give me a couple of slack and I'll propose something you will love
[22:17] <sergiusens> ;-)
[22:17] <balloons> so, if we migrate to cmake it should build the click apps.. So, the only missing piece is pushing them to the device?
[22:18] <sergiusens> balloons, yup; and that should be easy enough if we standarize a bit
[22:18] <balloons> sergiusens, as long as I can get the desired workflow I'll be happy
[22:18] <balloons> right.. I thought you might have some ideas.. So show me up :-)
[22:18] <sergiusens> balloons, one thing that you might be able to help with is; is the way we do testing the way we want to do it; and do we have a migration plan?
[22:19] <balloons> what do you mean "is the way we do testing the way we want to do it?"
[22:19] <sergiusens> I mean, is everyone sufficiently happy with this mechanism to provision the tests?
[22:19] <sergiusens> balloons, another thing is, we need to figure out how to use autopilot without installing it
[22:19] <balloons> ahh.. at the moment I don't think provisioning is easy as a normal app dev or test writer
[22:20] <balloons> that's part of the goal here
[22:21] <sergiusens> balloons, yeah, but do we want to add is as part of the click package?
[22:21] <sergiusens> balloons, or keep it that way
[22:22] <sergiusens> balloons, I'll make it easy to provision
[22:22] <balloons> sergiusens, honestly the route I'm proposing still isn't ideal
[22:23] <balloons> Ideally we'd have a simple test runner that supports testing against a device or the emulator with a single switch, and requiring nothing from me except my branch (local or lp ;-) )
[22:24] <sergiusens> balloons, that can all be doable; imagine running 'make device-test'
[22:24] <balloons> right.. ideally the app devs would rather have it more integrated into qtcreator
[22:25] <balloons> I assume making it part of the build would make that easier
[22:25] <sergiusens> balloons, we can externalize it; I can add that to phablet-click-test-setup easily (test provision)
[22:27] <balloons> sergiusens, well, how much hacking time is required? :-)
[22:28] <sergiusens> balloons, not much; we just need to standarize
[22:28] <sergiusens> balloons, how about we set some time to chat tomorrow?
[22:29] <balloons> sergiusens, sounds like a plan. I'd like to get this up and running asap. We need an easier way to provision for app devs
[22:29] <balloons> the migration work is just that, but I'm happy to do it if it gets us where we need to be
[22:29] <sergiusens> balloons, we chat tomorrow; implement that tomorrow night :-)
[22:30] <sergiusens> balloons, can you set something up and probably invite any other people you think are relevant?
[22:30] <balloons> sergiusens, I'll do so now
[22:30] <balloons> sergiusens, 1500 utc ok for you?
[22:30] <sergiusens> balloons, yup
[22:33] <sergiusens> balloons, I'll try and get some notes down to review before then and share on the appointment
[22:34] <balloons> sergiusens, sent, feel free to invite whomever you wish..
[22:43] <sergiusens> balloons, ack; I see some heavy weight names there ;-)


[11:48] <jared> jea: if you have a chance to draft up a wiki regarding the ML that would be awesome, I'm happy to jump in and help finalise I have assessments due next week though so I'll be pulling all nighters over the weekened to get them in.
[11:48] <jared> Also, anyone else is able to jump in if they want to assist.
[11:49] <jea> let me read that email
[11:50] <jared> The requirements for verification appear significantly lower than previous requirements for approval.
[11:50] <jea> ok, I shall look at doing it now
[11:51] <jea> It would help slightly if we had had a meeting in the last few months
[11:51] <jared> Yeah, if you don't have time that's fine. I'm getting the impression there is little impetus for much these days.
[11:58] <jea> jared: should it be wiki.u.c/AustralianTeamVerificationApplication2013 or wiki.u.c/AustralianTeam/VerificationApplication2013 ?
[11:58] <jared> Everything should really be under w.u.c/AustralianTeam/* to make life easier I think
[11:58] <jea> good, that is what I thought
[12:01] <jea> your email is<EMAIL_ADDRESS>[12:01] <jared> Yeah, that's the one on the wiki
[12:01] <jea> ok
[12:03] <jea> can I look up mailing list subscriber numbers?
[12:03] <jared> Yeah it's in the admin console I believe you have access to.
[12:04] <jared> I gotta head off to get some stuff organised for the morning. If you get a list of stuff you need just sing out and I can either put it in or show you how it's found
[12:04] <jea> ok
[20:54] <jared> jea: awesome work, I'll have a check over the weekend