[00:42] <stgraber> if someone's wondering, ubuntu-system-settings is being held in saucy-proposed Unapproved because it's seeded and so not strictly ubuntu-touch specific for the time being
[00:43] <stgraber> to solve that, someone would need to fix at least indicator-bluetooth so it stops pulling ubuntu-system-settings on Lubuntu
[00:45] <stgraber> (I can be convinced of letting it through before indicator-bluetooth is fixed, but I want the name of someone working to fix the larger problem so this doesn't happen again)
[03:44] <stgraber> so slangasek let ubuntu-system-settings in after spending some more time tracking the source of the seed entry for lubuntu, tedg also proposed a branch to fix the indicator-bluetooth problem, so hopefully once that lands ubuntu-system-settings will be auto-accepted into proposed from that point on
[06:20] <didrocks> Mirv: hey, how are you?
[06:21] <dpm> morning didrocks, I've updated row 114 of the landing asks page, does that look ok to you? The reason I'm asking is because I wanted to hold on with the merge in the app so that it happens around the same time as the seeds change (core apps merges land on the core apps PPA and then to the image directly)
[06:21] <dpm> I just wanted to give a heads up and ask if there is anything I need to do on my side to ensure it runs smoothly
[06:22] <didrocks> dpm: well, you can merge it and we will do the seed change this morning, sounds good?
[06:22] <didrocks> dpm: just don't upload to the ppa or whatever is needed after the merge before 11am ;) (as we are going to run an image build)
[06:23] <didrocks> dpm: but basically, we shouldn't hear about a request before the things are merged to turnk
[06:23] <didrocks> trunk*
[06:23] <dpm> didrocks, that was the issue: it's already merged. I added a note not to merge it, but this morning I noticed one of the developers top-approved
[06:23] <didrocks> dpm: ok, so we just need the seed change on our side, right?
[06:24] <dpm> didrocks, yeah, I sent a MP for the seed change and added it to the notes in the spreadsheet
[06:24] <didrocks> ok, scheduling the seed change
[06:24] <didrocks> dpm: won't be for that image, for next one though
[06:24] <didrocks> (probably 68)
[06:24] <dpm> didrocks, there is no urgency at all for this. I just wanted to make sure it's all coordinated
[06:24] <dpm> thanks!
[06:25] <didrocks> yw ;)
[06:25] <didrocks> ogra_: I think we should respin an image, I don't see any from the night
[06:25] <didrocks> now that proposed was opened and so on
[06:33] <Mirv> didrocks: hey, fine
[06:33] <Mirv> didrocks: how about you?
[06:37] <didrocks> Mirv: I'm good, thanks!
[06:37] <didrocks> Mirv: in case you have time, I added history-service for you, I think it will be nice to get in soon
[06:37] <didrocks> I've handled libunity/home-scope
[06:38] <didrocks> do you think you will be able to do that one?
[06:41] <Mirv> didrocks: ok, thanks, I'll handle it
[06:44] <Mirv> didrocks: constant DNS problems, somehow always on the sdk stack checks
[06:46] <didrocks> :/
[06:46] <didrocks> retoaded: ^
[06:47] <didrocks> retoaded: can you please prioritize the latest fixes needed for that? It's kind of a real pain for us
[07:31] <vila> didrocks: : my understanding is that retoaded *is* working on that
[07:32] <didrocks> vila: do you have any ETA?
[07:32] <vila> he didn't give one :-/
[07:32] <didrocks> vila: can you fetch that for me? that would be helpful :)
[07:32] <vila> but he said he was running some tests before switching so that sounds like RSN
[07:33] <didrocks> vila: please keep us posted
[07:33] <vila> as best as I can
[07:57] <ogra_> didrocks, bah, i thought robru would do one
[07:57] <ogra_> didrocks, firing up a build
[07:57] <didrocks> ogra_: thanks! (yeah, I didn't see one as well)
[08:21] <asac> didrocks: he said todayish
[08:21] <asac> he wanted to swap out the machine doing dns
[08:22] <didrocks> ok, let's cross fingers
[08:23] <asac> didrocks: so the image we just kicked is 67?
[08:23] <didrocks> the archive freeze already start to get us slower
[08:23] <didrocks> asac: yep
[08:24] <asac> didrocks: did you see what was implemented to not slow us down too much?
[08:24] <didrocks> we are waiting for 2+ hours on the scope crash fix to get allowed in proposed
[08:24] <asac> omg
[08:24] <didrocks> asac: still the case for all common components
[08:24] <asac> they told me <5min additional time
[08:24] <asac> is that because its not touch only?
[08:24] <asac> yeah common components.
[08:24] <didrocks> asac: yeah, talking "touch only" doesn't make sense (not the first time I'm telling that), we have a lot of common components
[08:24] <didrocks> it's not a minority
[08:25] <asac> i didnt say it is good
[08:25] <seb128> didrocks, well, it's the same rule as other cycles, it's not "touch only", it's "unseeded"
[08:25] <seb128> seeded packages need rt review
[08:26] <asac> touch is seeded as well :) ... but is considered unseeded :/
[08:26] <didrocks> seb128: yeah, I just raised it for people discussing in vUDS, but it seems the discussion wasn't needed :/
[08:27] <seb128> asac, I'm just you can ask them to disable the bot and manual review your packages as well
[08:27] <seb128> asac, but then don't complain that reviews create delays ...
[08:27] <asac> :)
[08:27] <asac> nonono ... plz not
[08:28] <seb128> haha
[08:28]  * asac dist-upgrades and waits
[08:30] <asac> didrocks: will be right there... have to reboot this machine. has troubles with wifi and i am sure it would go wild on hangout :). just go ahead i guess
[08:31] <didrocks> ok
[08:32] <didrocks> sil2100: joining?
[08:32] <didrocks> ogra_: ?
[08:33] <lool> asac: you coming?
[08:35]  * ogra_ wonders why his daily DSL disconnect now happens exactly when the meeting starts
[08:35] <sil2100> didrocks: will join in a moment
[08:36] <didrocks> sil2100: we started
[08:50] <ogra_> hmm, that changes are gigantic http://people.canonical.com/~ogra/touch-image-stats/20130927.changes
[08:57] <lool> checking for updates!
[08:57] <lool> 60 MiB!
[09:02] <lool> ogra_: hmm I've pushed seed changes, but ./update doesn't pick them up; any idea?
[09:02] <ogra_> lool, hmm not really, did you apt-get source the latest meta ?
[09:03] <ogra_> it changed quite a bit
[09:03] <lool> ogra_: 1.076?
[09:03] <ogra_> yeah, the last from the archive
[09:03] <ogra_> there were a bunch of structural changes
[09:05] <lool> ogra_: still, I had added to touch
[09:06] <ogra_> SHRIEK !!!!!!!!!!
[09:06] <ogra_> ogra@anubis:~/Devel/packages/ubuntu-touch-meta$ grep seeds update.cfg
[09:06] <ogra_> seeds: sdk sdk-libs sdk-libs-dev touch
[09:06] <ogra_> seed_base: http://people.ubuntu.com/~ubuntu-archive/seeds/
[09:06] <ogra_> seed_base: bzr+ssh://bazaar.launchpad.net/~xnox/ubuntu-seeds/
[09:06] <ogra_> lool, mind to rip out the xnox line ?
[09:06] <ogra_> :)
[09:06] <lool> right
[09:07] <ogra_> sigh, how did i miss that last night
[09:07] <lool> that's what I was thinking: using wrong branch, but I also found a mistake in my change with the new structure
[09:08] <lool> ogra_: running
[09:10]  * ogra_ installs 67 on maguro
[09:14] <lool> hmm who marked mtp as DONE?
[09:14] <ogra_> me
[09:14] <lool> it's not DONE until it's promoted!  :-)
[09:14] <lool> it's INIMAGE
[09:14] <ogra_> it is in 67
[09:14] <ogra_> oh, ok
[09:15] <xnox> ogra_: yeah, i used my branches to test that the split is good =/ sorry about that.
[09:15] <lool> uploaded ubuntu-touch-meta
[09:15] <ogra_> xnox, nah, my fault, i should have catched it before uploading it
[09:35] <asac> how do i enable mir again?
[09:35] <asac> touch /userdata/.mir_display?
[09:35] <ogra_> heh
[09:36] <ogra_> close
[09:36] <ogra_> .display-mir
[09:36] <asac> in /userdata?
[09:36] <ogra_> yep
[09:36] <asac> or /home/phablet?
[09:36] <ogra_> err
[09:36] <ogra_> oh
[09:36] <ogra_> right
[09:36] <ogra_> ~/.display-mir
[09:36] <asac> why do we use /userdata/writeable_image vs. /home/phablet/.display-mir ?
[09:36] <asac> note the - vs _
[09:36] <ogra_> userdata is for .writable_image ---
[09:36] <asac> i prefer - :)
[09:37] <ogra_> userdata isnt writable for the user
[09:37] <asac> ic
[09:37] <asac> since i am root with adb it doesnt matter, but you can do mir on the terminal then. makes sense
[09:37] <ogra_> you wont be root in adb in the final release
[09:37] <ogra_> (i hope)
[09:37] <ogra_> and adb will be off
[09:37] <asac> err
[09:38] <asac> ok adb off is ok
[09:38] <asac> then if its on i want to be easy root
[09:38] <ogra_> you have sudo
[09:38] <ogra_> like always in ubuntu
[09:38] <asac> do we really need to invest in that?
[09:38] <asac> when will this be done :P
[09:38] <ogra_> we agreed on it a few times
[09:39] <ogra_> dunno, sergiusens was on it iirc
[09:40] <ogra_> so there is an update desktop wants to sync from debian that we also have seeded ... ( grilo 0.2.7-1 see #ubuntu-touch) ... i guess we can just nod it off ?
[09:48] <asac> i dont know
[09:48] <asac> grilo was something we had core app folks care about
[09:48] <asac> so check with them
[09:48] <asac> i think we had weither balloons or mhall asking for a landing there
[09:49] <asac> also check with didrocks about exact timing and yes/no about landing or not
[09:49] <asac> :)
[10:00] <asac> so whats up with landing no. 46?
[10:01] <asac> do we retry that in 69?
[10:01] <asac> its still listed as in 67
[10:05] <didrocks> I guess landed 46 was done tonight, that's for lool ^
[10:05] <didrocks> I didn't track that one (and wasn't in the loop)
[10:12] <lool> looking
[10:12] <didrocks> Mirv: ok, all the content-hub stuff is now deciphered, can you finish req #42? (we need to have content-hub rebuilt and just published it, seb128 confirmed it works)
[10:13] <lool> asac: someone has to fix systemd for it to pass autopkgtests; I've poked Marc (uploader) and Steve L also took a quick look, but I don't know where things stand to fix it
[10:14] <lool> it's not caused by the change though
[10:14] <lool> since it was a data / config change
[10:16] <asac> lool: what is this blocking?
[10:16] <lool> just this fix right now
[10:16] <cjwatson> The autopkgtests were already fixed
[10:16] <asac> i mean ... what would this hanging around in proposed block
[10:16] <cjwatson> It just seems that proposed-migration hasn't noticed for some reason
[10:17] <lool> cjwatson: should we do a no source change reupload of systemd?
[10:17] <lool> cjwatson: or would you hint it in?
[10:17] <cjwatson> No, don't reupload, I'm investigating
[10:17] <cjwatson> I'll hint it if I have to but hopefully I can fix it properly
[10:19] <cjwatson> (For clarity: as I understand it, it wasn't a systemd problem but a test runner problem)
[10:19] <cjwatson> Yeah, I/O errors
[10:19] <lool> ah right, someone mentioned fs corruption on #ubuntu-release
[10:21] <lool> cjwatson: do you know who runs the autopkgtests jenkins?
[10:21] <cjwatson> Why?  It's already been addressed
[10:21] <cjwatson> (But jibel et al I believe)
[10:24] <cjwatson> If I may I'm going to spend some time debugging this since it isn't the first time it's happened
[10:24] <cjwatson> And it doesn't sound like you need systemd absolutely desperately
[10:25] <lool> Sure
[10:25] <lool> I missed the chat with jibel, glad it's addressed
[10:26] <Mirv> didrocks: ok (content-hub)
[10:29] <jibel> lool, lot of autopkgtest failures last night caused by IO errors on one of the nodes in the lab
[10:29] <jibel> lool, all the failed jobs have been restarted
[10:32] <retoaded> didrocks, vila: yes I am working on the DNS. As soon as it is verified the DHCP/PXE boot/DDNS portion is working then the new DNS servers will be stood up.
[10:35] <vila> retoaded: thanks ! Before didrocks asks, any ETA ? ;)
[10:36] <retoaded> vila, will be testing the PXE boot portion later this morning (once rfowler gets in) hopefully. That should give me verification on the DHCP/DDNS as well. If all goes as it should then I will start phasing it in today.
[10:36] <psivaa> asac: ogra_: rerun notes app test on maguro and there is still 1 failure..i need to go out for about 30 mins.. will come back and run the rest
[10:37] <vila> retoaded: \o/ Let's cross fingers ;) didrocks ^
[10:37] <ogra_> psivaa-afk, well ... https://bugs.launchpad.net/notes-app/+bug/1231880 *might* be related
[10:38]  * vila upgrades and reboot
[10:39] <psivaa-afk> ogra_: probably but i remember that the current failure, test_note_focus_on_second_click_outside was the culprit in 65 before we backed out the keyboard changes..
[10:39] <psivaa-afk> looks like it's back
[10:41] <ogra_> ah,, k
[10:42] <ogra_> hmm didnt we have a fix for the home scope crash ?
[10:44] <ogra_> but given the amount of updates we had, the dashboard looks awesome
[10:47] <cjwatson> lool: systemd copied to release, but got more hints on underlying cause and still investigating
[10:56] <lool> cjwatson: thanks
[10:57] <cjwatson> I think I need to catch it in the act next time and run proposed-migration with adt_debug turned on.  But at least now I know where to look.
[11:07] <asac> ogra_: didrocks: popey: did we release 66?
[11:08] <asac> psivaa-afk: right. notes-app is understood. just try to make it as good as possilbe. we ignore it for a day still
[11:08] <asac> ogra_: didrocks: popey: the dashboard agrees at least that 66 should go out and i thought i had seen someone last night confirming that 66 was good
[11:08]  * asac thought it was released :)
[11:08] <popey> nope, it wasn't
[11:10] <asac> popey: ogra_: didrocks: any reason not to release 66?
[11:14] <didrocks> ogra_: we have the fix for it
[11:15] <didrocks> asac: home scope crash + content-hub regression, knowing that 67 is just around the corner, let's wait for that one
[11:16] <didrocks> we have 60% of tests result for 67, not sure how long it will take to get the end
[11:16] <asac> didrocks: but 66 is a good build :)
[11:16] <didrocks> psivaa-afk: plars  once you are around ^
[11:16] <asac> anyway, we can wait
[11:16] <asac> and have 66 in the banks
[11:17] <didrocks> I see maguro's tests are running
[11:17] <didrocks> and mako as well
[11:17] <Mirv> (content-hub published)
[11:18] <didrocks> Mirv: \o/
[11:18] <didrocks> Mirv: thanks ;)
[11:18] <asac> didrocks: so you want to skip even 67?
[11:18] <asac> that was a big one
[11:18] <didrocks> asac: hum, I want to publish 67 if it's good
[11:18] <asac> yeah
[11:18] <asac> didrocks: but not 66?
[11:18] <didrocks> I want the big one ;)
[11:18] <asac> ah ok
[11:18] <asac> yeah
[11:18] <asac> kk
[11:18] <didrocks> asac: depends, if 67 is screwed, yeah 66 for the week-end
[11:19] <asac> wow http://people.canonical.com/~ogra/touch-image-stats/20130927.changes
[11:19] <asac> 67 wont be screwed :)
[11:19] <didrocks> with all those changes? no risk :p
[11:19] <asac> lets just get it out soon so folks feel the big velocity we are currently having
[11:19] <asac> didrocks: well, but the results look pretty good already
[11:19] <asac> all the things that usually are risky are donish
[11:20] <asac> webbrowser, unity8 etc.
[11:20] <didrocks> yep
[11:20] <ogra_> yeah 67 looks releasable
[11:20] <asac> not yet done though :)
[11:20] <didrocks> let's wait for the end (core apps)
[11:20] <ogra_> but its close
[11:20] <didrocks> not sure how long it is for the dashboard to see the results?
[11:20] <didrocks> (some tests already finished, but not in the UI)
[11:20] <didrocks> like terminal
[11:21] <ogra_> didrocks, did you see Laney's sync request in #ubuntu-touch ?
[11:22] <ogra_> seems desktop wants a new grilo
[11:22]  * ogra_ guesses its ok to pull it in
[11:22] <Laney> not desktop, it's a sponsor request from ricotz
[11:22] <Laney> so I guess GNOME
[11:22] <ogra_> ah, k
[11:22] <didrocks> I was excpected a landing ask ;)
[11:23] <didrocks> Laney: what's the diff? was it tested on a phone?
[11:23] <Laney> bug fixes, probably not
[11:23] <ogra_> didrocks, do you want to have all desktop people adding for landing asks when there is a overlap ?
[11:23] <ogra_> *asking
[11:23] <Laney> I don't think random contributors have the means/motivation to do that kind of testing
[11:23] <ogra_> or foundations if there is a change to ubuntu-minimal
[11:23] <didrocks> ogra_: just discussing on IRC giving clear answer is good
[11:24] <ogra_> yeah, thats what i thinl
[11:24] <ogra_> *think
[11:24] <didrocks> Laney: the sponsor should (if working for canonical) that he won't regress the touch image though
[11:24] <didrocks> Laney: can you get that short testing in place before sponsoring?
[11:28] <Laney> It's a bit of a shift of work from sponsoree to sponsor :/
[11:32] <didrocks> well, the sponsor don't upload bindly, he ensures that what the sponsoree (who doesn't have upload rights for a good reason) isn't breaking desktop, touch, server…
[11:38] <seb128> didrocks, that's getting ridiculous...
[11:38] <seb128> imho just drop the upload
[11:38] <seb128> Laney, ^
[11:38] <seb128> Laney, we have better thing to do that testing every simple update on every form factor/image
[11:38] <didrocks> seb128: how do you know it's a "simple update"
[11:39] <seb128> let get somebody from the community sponsor it
[11:39] <didrocks> like jbicha's "simple commit" which adds a dep on universe?
[11:39] <seb128> didrocks, it's an upstream bug fix version, we sure can stop taking bug fix versions
[11:39] <Laney> I just wanted to help with clearing the FFe / sponsor queue
[11:39] <didrocks> seb128: that's why I asked for the diff
[11:39] <seb128> Laney, well, seems there is no way to do that without spending days in paperwork
[11:39] <seb128> didrocks, bug fix versions never required a FFe or diff or whatever
[11:40] <didrocks> seb128: did I ask for a FFe?
[11:40] <didrocks> I just want to know if the diff is safe
[11:40] <seb128> the net result of those crazy requirements is that people are going to stop trying to get any fix out
[11:40] <didrocks> nobody told if it was safe or not
[11:40] <didrocks> and why
[11:41] <seb128> didrocks, go on the bug and ask ricotz to provide those details, it's not fair to hit the sponsor for doing sponsoring
[11:42] <seb128> didrocks, we don't have knowledge of what that stack is doing and how to test it
[11:42] <seb128> didrocks, either we trust upstream or we don't take their fixes
[11:42] <didrocks> so if we don't have knowledge and don't test, that seems risky to me
[11:45] <plars> asac: mir seems to be broken on 66, and the new keyboard tests too (you know that already I'm sure)
[11:45] <plars> didrocks: hang on, let me check on 67
[11:45] <plars> didrocks: the dashboard scans every 15 min
[11:45] <plars> didrocks: most results seem to be there on 67 now
[11:47] <psivaa> plars: didrocks: i've just kicked off notes app test again
[11:47] <seb128> didrocks, well, depending of the "risky" definition, we can sure ban all upstream bug fix updates that we don't have the bandwith the gold certify, I'm not sure it's a smart move though
[11:47] <plars> psivaa: and I just started calendar
[11:48] <plars> psivaa: but it's the same 2 tests on calendar that periodically fail
[11:48] <plars> flaky
[11:48] <psivaa> plars: right
[11:50] <Mirv> didrocks: content-hub stuck in Unapproved queue
[11:50] <asac> plars: keyboard tests are enabled? i think its fine for them to fail if they never passed
[11:50] <asac> we just cant protect them from busting their tests then
[11:53] <seb128> asac, what's the recommended way forward if a community people want to get a bug fix update in but doesn't have the hardware to run our touch tests?
[11:56] <asac> interesting question
[11:56] <asac> seb128: you have a specific case?
[11:57] <asac> i believe during final release preps we should have balloons step in and double check every merge
[11:57] <asac> to ensure we dont regress
[11:57] <asac> at least would be one optionm
[11:57] <asac> e.g. we help our default apps out
[11:57] <seb128> asac, the grilo update ricotz asked for
[11:57] <seb128> which was previous discussed between laney and didrocks
[11:58] <asac> seb128: ricotz?
[11:58] <Laney> I'd usually do some light testing on my desktop before sponsoring and otherwise trust upstream and the contributor if they are known
[11:58] <asac> is he a core app dev that doesnt have a phone?
[11:58] <asac> Laney: you should have a phone
[11:58] <asac> otherwise you cant really sponsor touch stuff right now
[11:58] <Laney> I do have a phone, that's not the point
[11:58] <Laney> it's not "touch stuff"
[11:58] <asac> well you can, but you need a peer with a phone
[11:59] <seb128> asac, that's an insane requirement for sponsoring
[11:59] <Laney> it's a gnome component that mediascanner depends on
[11:59] <asac> its light testing
[11:59] <seb128> no it's not
[11:59] <asac> you just do light testing on phone for stuff that affects the phone
[11:59] <asac> otherwise ask for help sponsoring that in the landing team
[11:59] <seb128> asac, how do we test that stuff if we don't have knowledge of where it's used and how it works?
[11:59] <plars> asac: they are not, I'd like to confirm they work (or at least that something passes) so that I know everything is right on our end but when I tried it they were not... going to try again when that stuff goes back in
[11:59] <asac> its just better if you help them clear their work earlier
[12:00] <asac> seb128: thats where the landing asks come into play. Those asks allow you to identify what tests would be good to run
[12:00] <asac> in this way we build organizational know how
[12:00] <asac> over time and you will be better able to assess the impact fater a while on your own
[12:00] <asac> so yeah. if you cant assess the risk, ask for help to better assess the risk
[12:00] <seb128> asac, it's a community request for GNOME, we don't have the bandwith to do that detailled testing just to sponsor things for them
[12:00] <asac> i think thats a general rule all core-devs etc. have to apply
[12:00] <asac> already anyway
[12:01] <seb128> asac, your rules are just locked contributors and community flavors out, there is going to be nobody left to reach the bar you set
[12:01] <seb128> asac, that's an universe package
[12:01] <seb128> not a coredev thing
[12:01] <asac> anyway. we can discuss later. as i said, whatever we do now is just the start and we improve
[12:02] <asac> we lack automation that allows us to give better self-service facilities for everyeone
[12:02] <seb128> asac, well, meanwhile what do we tell to those community people? "go away, we don't want of your fixes because you don't have a device to test touch"?
[12:03] <lool> ogra_, popey: Good to promote 67?
[12:03] <lool> (tests looks good!)
[12:03] <popey> looked good to me when I tried it a couple of hours ago
[12:04] <asac> seb128: no. tell them that we will help them and will test for them, and explain to them the situation so they understand
[12:04] <asac> then either you help them pre test
[12:04] <seb128> asac, I don't understand the situation and why we do all those google document crazyness myself, I doubt I can explain it to the community
[12:04] <asac> or we will test the stuff once its about to go into the archive for them
[12:04] <asac> seb128: thats not what you explain
[12:05] <asac> seb128: you explain that ubuntu phone is trying to work till the last moment of release to get a nice phone together
[12:05] <seb128> asac, you are sure you guys have the bandwith to manually test by ourself everything that gets uploaded?
[12:05] <ogra_> lool, asac, popey ... i'd be ready ...
[12:05] <asac> and due to the increased risk of doing that during the end we want to be sure that nothing is slipping through etc.
[12:05]  * ogra_ has the hand on the trigger ... 
[12:05] <asac> i am sure they understand that we want to be a bit careful
[12:05]  * ogra_ pulls it slowly down  ... 
[12:05] <seb128> asac, well, those component are used by Ubuntu GNOME and you are blocking their fixes
[12:06] <seb128> asac, they could make the reverse argument, they try to get a release out as well
[12:06] <asac> well, we are not blocking their fixes
[12:06] <asac> we are preventing our breakage
[12:06] <asac> thats a different way to see it
[12:06] <seb128> you do, because they didn't test on your image
[12:06] <asac> we can start making a ban on those kind of gnome things
[12:06] <asac> :)
[12:06] <seb128> asac, do you test your changes on Ubuntu GNOME to make their you don't create issues for them?
[12:06] <asac> and work over time to remove dependencies
[12:06] <asac> but thats not the way i want to go
[12:06] <asac> we do...
[12:06] <asac> we have automation for desktop
[12:06] <asac> we dont have automation for touch
[12:06] <seb128> desktop being Unity
[12:06] <seb128> not GNOME
[12:07] <seb128> or xfce
[12:07] <ogra_> *kaching*
[12:07] <ogra_> 67 is out
[12:07]  * popey preps email
[12:07] <ogra_> popey, please mail :)
[12:07] <ogra_> 20130927/67
[12:07] <popey> i always flash mine OTA before mailing
[12:08] <ogra_> might take a second until it is mirrored
[12:08] <popey> mine sees it
[12:08] <popey> 60.7MB \o/
[12:08] <popey> It's a monster
[12:08] <ogra_> yeah, its a huge changeset
[12:08] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/20130927.changes
[12:14] <popey> mail sent
[12:17] <ogra_> thx
[12:18] <ogra_> lool, i assume landing #46 will rather be in image 68 ?
[12:18] <seb128> sil2100, what's the rational for http://bazaar.launchpad.net/~unity-team/unity/trunk/revision/3538 / where is this requirement noted?
[12:19] <seb128> noted->written
[12:20] <sil2100> seb128: first of all, it's pulling in an universe package from main
[12:20] <seb128> which one?
[12:20] <sil2100> telepathy-indicator
[12:20] <sil2100> saucy/universe
[12:21] <seb128> shrug
[12:21] <sil2100> I think the commit message is missing a word, but I was in a hurry
[12:21] <sil2100> ;)
[12:21] <seb128> sil2100, that package was in main until a week ago
[12:21] <seb128> without it empathy's integration in unity stops working
[12:21] <sil2100> uh
[12:21] <cjwatson> Right, it could be moved back with zero paperwork
[12:21] <seb128> that's why we need it back
[12:22] <Laney> Why did it move out?
[12:22] <sil2100> Ok then, once this is back in main, let's re-add it to lp:unity then
[12:22] <cjwatson> Good question, we have no records that would help
[12:22] <seb128> Laney, because the GNOME guys dropped the recommends from empathy to move it to unity
[12:22] <cjwatson> Ah
[12:22] <Laney> fair enough, sounds fine then
[12:22] <seb128> and didn't wait for the unity side to land
[12:22] <cjwatson> I'll move it back to main now
[12:22] <sil2100> cjwatson: thanks
[12:22] <cjwatson> done, please revert that unity change
[12:23] <seb128> sil2100, cjwatson: thanks
[12:23] <sil2100> I'll re-add it to lp:unity then
[12:23] <cjwatson> (pending a publisher run but I expect you won't manage to release before then anyway)
[12:23] <sil2100> didrocks: ^
[12:24] <sil2100> didrocks: should I do a direct push? I guess it would be nice to re-build unity again so that we release it with the recommends...
[12:24] <sil2100> didrocks: since it sounds urgent
[12:29] <lool> ogra_: looking
[12:48] <ralsina> lool: we have a big fix for click-update-manager ready in trunk, but we'll have a bunch of UI improvements including much better error reporting in a few hours. Should we land what we have now or wait for that? Current trunk is a big improvement anyway.
[12:55] <lool> ralsina: what you land in trunk must be releasable at any time
[12:55] <ralsina> lool: it is at this time
[12:56] <lool> ralsina: I'm assuming you're only working on top priority things for 13.10, so as soon as you have more than low priority bugs to land, it's best to ask for a landing slot
[12:56] <ralsina> lool: ok, so asking for one now. I'll add it to the spreadsheet
[12:56] <lool> ralsina: so just land them in trunk, get a landing slot now; what's a good description of the changes?  UI and error reporting improvements?
[12:56] <ralsina> lool: that one is not in trunk yet, I'll just add it to the spreadsheet, nevermind
[12:59] <lool> ralsina: is this scope and updater, or just updater?
[12:59] <ralsina> lool: just updater
[13:00] <lool> ralsina: Added line 111 of plan; landing number 51
[13:00] <ralsina> lool: 111? That's powerd compatible with mir
[13:01] <lool> ralsina: line 111 of first sheet?
[13:01] <ralsina> ah, ok
[13:01] <ralsina> never had one added directly to the plan
[13:02] <lool> there's a first time for everything  ;-)
[13:04] <asac> did 67 go out? :)
[13:05] <ogra_> long ago
[13:07] <dobey> sil2100: gatox says you're planning to integrate tests for click-update-manager into the daily release? i proposed this branch last night, but there's a missing build-dep i need to find, and i expect qmltestrunner might segfault after that.
[13:07] <sil2100> dobey: you proposed it to cu2d?
[13:09] <dobey> sil2100: no, to click-update-manager. i don't think cu2d needs any changes for this
[13:09] <sil2100> hmmm
[13:09] <didrocks> sil2100: direct push is fine
[13:10] <sil2100> didrocks: did that, thanks ;)
[13:10] <didrocks> sil2100: we can build unity8 meanwhile anyway ;)
[13:10] <sil2100> dobey: ok, but autopilot tests need adding in cu2d, since we shouldn't run integration tests on build time
[13:11] <ogra_> didrocks, yeah, seems thats the last bit missing for an 68 build
[13:11] <didrocks> ogra_: yeah, but but but, we got 67 \o/ we can already celebrate ;)
[13:11] <asac>  \o/
[13:11] <dobey> sil2100: right
[13:11] <didrocks> ogra_: the lightdm stuff landed? (sorry, still catching up)
[13:11] <sil2100> dobey: anyway, I guess you need qtdeclarative5-dev-tools
[13:11] <ogra_> didrocks, will be in 68
[13:11] <asac> 68 would be a dream today, but it shouldnt come at the price of a long friday :)
[13:11] <didrocks> ogra_: flying? ;)
[13:12] <ogra_> didrocks, would be nice to have 68 building before the meeting tonight, so MM gets a chance
[13:12] <didrocks> asac: agreed, at least, "being prepared for 68" will be a nice goal
[13:12] <sil2100> dobey: I'll take care of the autopilot parts
[13:12] <didrocks> ogra_: agreed
[13:12] <didrocks> ogra_: but seems hard, all depends on sil2100 I guess
[13:12] <didrocks> sil2100: no pressure :p
[13:12] <dobey> sil2100: ok, thanks
[13:12] <didrocks> sil2100: is unity8 pushed to trunk as per #ubuntu-unity?
[13:13] <sil2100> didrocks: no, I was thinking about it - you think we can just merge it manually? Since the tests will be ran on cu2d during build anyway, right?
[13:14] <didrocks> sil2100: scrollback what I told on #ubuntu-unity ~15 minutes ago please
[13:14] <didrocks> sil2100: I think yeah, we are in agreement (just sync with Saviq)
[13:14] <didrocks> then, let's start/force unity8 to build
[13:14] <didrocks> so that we meet our deadline
[13:15] <sil2100> Argh
[13:15] <sil2100> Ok
[13:16]  * ogra_ considers to be superbrave today and types "touch .display-mir" into the terminal app on maguro and reboots
[13:16] <fginther> morning
[13:18] <lool> kgunn, sil2100, didrocks: I've added a slot for unity-mir fix for autopilot tests; would that me image 69?
[13:18] <lool> sil2100: can I mark you down for it?
[13:18] <lool> kgunn is digging the details, it's probably not in trunk yet
[13:18] <lool> but being worked on
[13:18] <kgunn> lool: i spoke too soon...i don't think we're there yet....i'll get back asap tho (its on my radar)
[13:18] <kgunn> lool: right
[13:19] <kgunn> not on trunk
[13:19] <lool> kgunn: that's ok
[13:19] <didrocks> kgunn: lool: sure, keep us posted
[13:19] <didrocks> kgunn: lool: no ABI break on mir?
[13:19] <didrocks> only unity-mir?
[13:19] <kgunn> didrocks: right it'd be unity-mir
[13:19] <sil2100> lool: so it got fixed?
[13:19] <lool> kgunn: I do see a noticeable speed difference when switching between screens of the home scope
[13:20] <lool> sil2100: it's being worked on
[13:20] <ogra_> hmm, Mir on maguro is still pretty slow, but at least got less crashy
[13:20] <lool> sil2100: since you did the first landing, can I put your name on the one with the fix?
[13:20] <lool> kgunn: speed difference between SF and Mir that is
[13:20] <sil2100> lool: yes ;) Would be nice if they could poke me once it's done
[13:21] <lool> the SF user experience felt as fluid as it could be, the Mir one not so much
[13:21] <lool> win 77
[13:21] <lool> ups
[13:23] <kgunn> lool: there are optimizations that we will work on in t-series, but not for v1....such as bypass, full use of hwc asset, dirty region
[13:24] <kgunn> lool: also triple buffering
[13:34] <didrocks> lool: we are at 67, not 77 ;)
[13:34] <didrocks> (what? IRC? can I flash my phone with it?)
[13:35] <seb128> didrocks, you don't get it, lool lives in the futur, he's testing images before they are made
[13:35] <didrocks> ah… that explains
[13:35] <didrocks> lool: how the final image looks like then?
[13:35] <didrocks> can we publish it and be done? ;)
[13:35] <ogra_> didrocks, i think he just typoed ... that was the year of the wine he had for lunch ;)
[13:36] <ogra_> that cheapo 77 stuff
[13:36] <didrocks> ogra_: ahah ;)
[13:37] <lool> didrocks: final is awesome, but I am bit too drunk from the release party to tell you about what's in it
[13:37] <lool> ;-)
[13:38] <didrocks> heh
[13:40]  * ogra_ grins
[14:08] <lool> dobey, ralsina: Uninstall doens't work for me
[14:08] <lool> dobey, ralsina: Getting a pkcon error on a preinstalled app
[14:09] <lool> also still not getting reliable results when searching for stuff
[14:09] <ralsina> lool: yes, preinstalled apps can't be uninstalled
[14:09] <ralsina> lool: the next revision will give you an error for that
[14:09] <cjwatson> ralsina: wrong (now)
[14:09] <dobey> lool: it worked fine here. i uninstalled ubuntu one
[14:09] <ralsina> cjwatson: interesting :-)
[14:09] <cjwatson> ralsina: I added support for that in click 0.4.8
[14:09] <dobey> and ebay and amazon and a bunch of things
[14:09] <ralsina> lool: I guess I need to see the pkcon error then
[14:09] <cjwatson> ralsina: you should be checking the _removable field in the manifest
[14:10] <ralsina> cjwatson: yes, it's in alecu's next branch
[14:10] <cjwatson> ralsina: (which will be 1 for everything at the moment, but potentially 0 in the future)
[14:10] <cjwatson> ok
[14:10] <cjwatson> ralsina: it doesn't really remove from disk, of course, but it hides from the user's view
[14:20] <dobey> qmltestrunner: could not find a Qt installation of '' <- anyone else know what this very informative error message actually means?
[14:33] <cjohnston> asac: are we having a call?
[14:40] <dobey> nobody? :(
[14:41] <cjohnston> dobey: where are you seeing that
[14:42] <dobey> cjohnston: in jenkins on a branch i'm trying to add running of the qml unit tests to.
[14:42] <dobey> https://jenkins.qa.ubuntu.com/job/click-update-manager-saucy-amd64-ci/13/console
[14:47] <dobey> i have no idea what it's looking for and not finding
[14:47] <cjohnston> vila: fginther seems to be out.. any thoughts ^?
[14:51] <vila> cjohnston: nope and since it's a pbuilder cow env, it's gone already
[14:51] <vila> cjohnston: only thought is that we need a way for devs to reproduce locally
[14:51] <cjohnston> dobey: hopefully fginther will be back in a minute and may have more insite
[14:51] <cjohnston> insight
[14:52] <vila> dobey: have you tried building that package locally ?
[14:53] <cjohnston> also a good start
[14:54] <lool> dobey, ralsina: So not sure why by my Installed list is full of blank space; happens from time to time, not sure of the triggers
[14:54] <lool> need to paste you the pkcon error
[14:54] <dobey> vila: the tests run locally (though qmltestrunner crashes). but i have lots of stuff installed that isn't installed in a clean environment. most notably, the "ubuntu-sdk" and the qtcreator package for it, depend on lots of extraneous things. i could "fix" it by simply depending on ubuntu-sdk, but that's really not appropriate to do for a package build
[14:54] <lool> [unity-scope-click] - DEBUG: click-scope.vala:192: Error building preview: Problem running: pkcon -p remove com.ubuntu.dropping-letters;0.1.2.2;all;local:click (Child process exited with code 7).
[14:55] <lool> dobey, ralsina: http://paste.ubuntu.com/6163049/
[14:55] <lool> cjwatson: ^
[14:55] <dobey> lool: oooh. i think i know why that is happening for you and i didn't see it now (just realized something and didn't think anything of it before)
[14:56] <lool> click list for phablet shows com.ubuntu.dropping-letters     0.1.2.2
[14:56] <dobey> lool: is your root mounted as ro or rw at the moment?
[14:56] <lool> dobey: ro
[14:56] <cjohnston> fginther: https://jenkins.qa.ubuntu.com/job/click-update-manager-saucy-amd64-ci/13/console  any thoughts?
[14:56] <cjwatson> lool: please file that as a click bug for me
[14:57] <cjwatson> dobey,ralsina: ^- pretty sure this is my fault, I'll deal with it
[14:57] <ralsina> cjwatson: ack
[14:57] <dobey> cjwatson: ah ok, thanks
[14:57] <bfiller> fginther: this MR is not landing for sometime now: https://code.launchpad.net/~renatofilho/ubuntu-ui-toolkit/fix-1213046/+merge/186223
[14:58] <cjwatson> lool: FWIW I believe this only happens if you attempt to remove a preinstalled app before you installed any apps otherwise
[14:58] <fginther> cjohnston, first thought is there is a missing dependency
[14:58] <cjwatson> lool: so workaround: install something else first
[14:58] <bfiller> fginther: looks like some alarm tests are failing on sdk. Are all sdk MR's failing because of this? need ot get it resolved
[14:58] <cjohnston> dobey: ^
[14:59] <fginther> bfiller, yes, I spoke to renato about that one. Something was merged into ubuntu-ui-toolkit right before the run for http://jenkins.qa.ubuntu.com/job/ubuntu-ui-toolkit-ci/738/ that changed the alarm code
[14:59] <dobey> cjohnston, fginther: yes, that much is obvious. but how can i tell which one it is?
[14:59] <fginther> bfiller, I'll forward you the email
[14:59] <bfiller> fginther: how do we fix it?
[14:59] <bfiller> (i'll wait for mail)
[15:00] <vila> dobey: so basically you answered yourself, if your deps are not complete you can't expect to run in a clean env
[15:00] <vila> dobey: start a fresh chroot and test there ?
[15:00] <dobey> vila: tell me what dep i am missing, and i will happily add it.
[15:00] <cjohnston> dobey: that isn't CI's job
[15:01] <lool> cjwatson: Yes, that's how it looks; FYI Rick said he can't uninstall his Click apps either, so will try to repro this now
[15:01] <vila> dobey: I know even less than you... that's your package ?
[15:01] <lool> cjwatson: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1232066
[15:01] <dobey> cjohnston: i'm not asking about CI
[15:02] <dobey> vila: it's a package of a somewhat simple qml app, yes
[15:02] <didrocks> sil2100: do you have the bug handy for tha autopilot regressions?
[15:02] <cjwatson> lool: Rick's apps aren't preinstalled, so that won't be the same
[15:03] <cjohnston> dobey: your asking us what is missing..
[15:03] <dobey> cjohnston: i was asking if anyone had seen that error before and might have some idea as to wtf it means
[15:04] <dobey> ie, how to figure out what is missing
[15:04] <dobey> cjohnston: i also asked in #ubuntu-touch where nobody replied
[15:04] <vila> dobey: right, never seen that, no idea what is missing
[15:05] <lool> cjwatson: exactly
[15:05] <vila> dobey: I agree that the message is terse though
[15:06] <didrocks> plars: around?
[15:06] <plars> didrocks: yes
[15:06] <didrocks> plars: do you mind installing unity + all the scope + unity8 from the daily-build ppa on your phone and run the unity8 AP tests?
[15:06] <plars> didrocks: sure, let me reprovision first, give me a bit
[15:07] <didrocks> thanks ;)
[15:07] <sil2100> didrocks: you mean, the mir ones?
[15:07] <didrocks> sil2100: hum, no, autopilot alone
[15:08] <didrocks> it was maybe Mirv…
[15:09] <fginther> dobey, this is a qt dependency for which I have very little experience. I agree the qmltestrunner output doesn't help. Do you have pbuilder or sbuild setup locally?
[15:09] <asac> cjohnston: that fell through. sorry. you are gone next week too, rigth?
[15:09] <asac> cjohnston: lets have a fresh start the week afer
[15:10] <cjohnston> asac: correct.. I can do any time today or when I come back
[15:10] <cjohnston> your call
[15:10] <cjwatson> lool: http://bazaar.launchpad.net/~click-hackers/click/trunk/revision/284
[15:10] <dobey> fginther: yes, though i don't know what to look for in there once it does fail
[15:10] <asac> cjohnston: enjoy vacation. i am also gone for next week so... :)
[15:11] <cjohnston> :-)
[15:11] <josepht> woohoo! a whole new dashboard next week then :)
[15:13] <dobey> fginther: will jenkins auto-retry if a build fails due to "apt-get update" failing?
[15:14] <lool> cjwatson: running into other bugs to get to test the other thing, sorry takes a while
[15:15] <fginther> dobey, nope, it's not that smart, I can retrigger if you send me the failing job
[15:15] <dobey> fginther: http://s-jenkins:8080/job/unity-scope-click-ci/43/rebuild
[15:16] <fginther> dobey, re-triggerd
[15:16] <dobey> fginther: thanks
[15:18] <ogra_> didrocks, hmm, i thought we wanted to keep 69 relatively clear for the MM landing (you just moved the TZ stuff to 69 ... that should better be 70 (monday))
[15:19] <didrocks> ogra_: I think it's landing right now, so should be 68
[15:19] <didrocks> (changed)
[15:19] <ogra_> didrocks, whats landing right now ?
[15:20] <ogra_> didrocks, i just agreed with pitti to keep iot til monday
[15:20] <didrocks> ogra_: the tz landing, I told "ack for today"
[15:20] <didrocks> ogra_: it's not ready?
[15:20] <ogra_> since he will be gone soon and not be around for questions or rollback
[15:20] <didrocks> ok
[15:20] <didrocks> so Monday it is
[15:20] <ogra_> it hasnt been tested, needs an android rebuild and will even take several hours to land
[15:21] <ogra_> since the packages have to be built in order
[15:21] <didrocks> ogra_: ok, you pinged me about it, I thought everything was rightly tested ;)
[15:21] <ogra_> so we have to do piecemeal uploads
[15:21] <didrocks> ok, Monday sounds better
[15:21] <ogra_> right
[15:30] <mandel> lool, ping
[15:32] <balloons> doanac, sergiusens fyi, going to try and have a merge proposal for every core app today to land click testing support. The work is done, save 2 holdout apps
[15:35] <doanac> balloons: that's good news. thanks!
[15:35] <doanac> sergiusens: autopilot got their test breakage fixed. so it should be good to land also
[15:35] <doanac> and i have a patch for the CI end of things
[15:38] <sil2100> didrocks: regarding autopilot testing on the phone...
[15:38] <sil2100> didrocks: https://bugs.launchpad.net/webbrowser-app/+bug/1231492
[15:38] <didrocks> sil2100: give me good news
[15:38] <didrocks> sil2100: still? :/
[15:38] <sil2100> didrocks: I see the solutions here did not yet land?
[15:38] <didrocks> sil2100: mirv told that it landed
[15:38] <didrocks> sil2100: remember that you need to launch app tests first
[15:38] <didrocks> sil2100: and then unity8 tests
[15:38] <didrocks> or reboot in between
[15:38] <sil2100> I know, started off with apps tests
[15:40] <didrocks> ok :/
[15:41] <plars> didrocks: do you have a specific package list?
[15:43] <didrocks> plars: unfortunately, not. look at the source packages for the unity and unity8 stacks in http://people.canonical.com/~platform/cu2d/results
[15:43] <didrocks> plars: and just install those that are on the phone (should be all of them but compiz and nux)
[15:43] <didrocks> and unity itself
[15:43] <didrocks> (you will need libunity-core*
[15:44] <plars> didrocks: all the scopes you need are on that page too?
[15:45] <didrocks> plars: yeah ;)
[15:58] <lool> mandel: pong
[16:01] <ogra_> asac, hangout ?
[16:02] <asac> robru: comning?
[16:10] <plars> didrocks: well, I got 3 test failures, and I still get the home scope crash but it's very possible that I missed some package
[16:12] <lool> kgunn: Did you add to the first sheet of Landing Plan?
[16:12] <kgunn> lool: crap...my bad
[16:12] <kgunn> lool: i'll put it on the ask sheet
[16:12] <kgunn> sorry
[16:13] <lool> ok
[16:22] <didrocks> plars: probably yeah ;)
[16:22] <didrocks> thanks for testing plars
[16:24] <lool> didrocks: I'd like to add https://code.launchpad.net/~bfiller/mediaplayer-app/remove-no-display/+merge/188092 to Landing plan; probably 70
[16:24] <lool> it's needed for video scope activation to demonstrate video playback
[16:24] <plars> didrocks: was it supposed to fix that?
[16:24] <lool> I've tested it locally, it fixes video scopes activation here
[16:25] <didrocks> plars: yeah, I guess you missed the home scope
[16:25] <didrocks> (already in archive, but not in an image yet)
[16:26] <plars> didrocks: I'm pretty sure I got that one, let me double check though
[16:26] <lool> didrocks: I'll take it as a yes  ;-)
[16:27] <plars> root@ubuntu-phablet:/# apt-cache policy unity-scope-home
[16:27] <plars> unity-scope-home:
[16:27] <plars>   Installed: 6.8.2+13.10.20130927.1-0ubuntu1
[16:27] <plars>   Candidate: 6.8.2+13.10.20130927.1-0ubuntu1
[16:27] <plars> didrocks: I would assume that's the right version since it has a buildstamp from today
[16:30] <didrocks> plars: hum, that's weird
[16:30] <didrocks> lool: yea, please do ;)
[16:30] <didrocks> lool: sorry, was still in this hangout
[16:39] <lool> cjwatson: so I can confirm removal of regulalry installed clicks work and so does removal of preinstalled clicks once you've installed another one
[16:39] <lool> dobey, ralsina: There are a couple of bugs with click removals from scope
[16:39] <lool> reporting htem
[16:41] <cjwatson> lool: cool
[16:42] <ralsina> lool: awesome
[16:45] <lool> ralsina, dobey: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1232129 and https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1232130
[16:48] <dobey> first one is actually unity. and second one is probably the click tool
[16:48] <ralsina> lool: 1232129 is a dupe, I'll find the original and mark it
[16:48] <ralsina> lool: it's also AFAIK a unity8 bug (the scope asks for the refresh, nothing happens)
[16:48] <balloons> plars, just looking over today's runs.. FYI, the rss reader regression is an sdk bug, but a workaround went in: https://bugs.launchpad.net/ubuntu-rssreader-app/+bug/1231137
[16:50] <cjwatson> dobey: not the responsibility of click, I think - the scope should do it
[16:50] <cjwatson> dobey: click in general doesn't know about process lifecycle
[16:51] <dobey> cjwatson: nor does the click scope. is there some way to make the "running apps" scope know about things being removed?
[16:51] <cjwatson> Not sure
[16:51] <cjwatson> Maybe tedg could help
[16:59] <didrocks> ogra_: needing anything from me before I leave?
[16:59] <didrocks> (for the iso spinning and so on…)
[16:59] <ogra_> didrocks, i dont think so
[16:59] <didrocks> ogra_: that was the right answer! :)
[16:59] <didrocks> thanks ;)
[17:00] <ogra_> :)
[17:01] <ogra_> enjoy your weekend
[17:05] <lool> FYI, this will eventually need a coordinated landing: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1232130 but it's still being worked on; will open a slot once we have code
[17:05] <ogra_> sounds like a 70 thing
[17:15] <lool> ogra_: Actually thinking the video scope activation might be worthwhile to get with the mmedia stuff  :-)
[17:15] <lool> but it's marked for later
[17:15] <lool> will leave it there; it's stuck in upstream merger anywau
[17:15]  * lool steps out
[17:15] <ogra_> well, not sure if that wouldnt taint clean MM testing on the image
[17:19] <dobey> well, i found the reason for the insane qmltestrunner qtchooser error
[17:20] <dobey> apparently none of the qt*5whatever packages depend on qt5-default. so everyone has to explicitly build-dep on it :(
[17:26] <lool> dobey: ubuntu-sdk?
[17:26] <lool> dobey: but that's not a bdep
[17:29] <dobey> lool: right, ubuntu-sdk would install it, along with a bazillion other packages
[17:47] <cwayne_> hey guys, can we get ubuntu-touch-customization-hooks into the landing plan?
[17:47]  * cwayne_ would add it but don't have write access to the doc
[17:50] <cwayne_> asac, ^
[17:53] <cjohnston> cwayne_: does your lead not have access?
[17:56] <cwayne_> cjohnston, no, we're in PES, not UE
[17:57] <cwayne_> so we're not quite setup the same way i mean
[17:57] <cjohnston> ahh
[18:11] <fginther> cwayne_, I don't have write access. cyphermox, robru, do either of you have write access to the landing plan? ^ cwayne
[18:12]  * ogra_ can add it to landing asks ... 
[18:12] <fginther> ogra_, thanks :-)
[18:12] <ogra_> it wont be processed until monday anyway though
[18:12] <cwayne_> ogra_, no worries, just wanted to get it in asks before i forgot :)
[18:12] <fginther> ogra_, does asac own that doc (or who do I talk to get write access)?
[18:13] <ogra_> asac or didrocks
[18:13] <fginther> thx
[18:39] <robru> asac, oops, sorry for missing the meeting this morning, just waking up now, feeling quite ill. anything pressing you need me to take care of before i go back to bed?
[18:41] <ogra_> toi think we are fine, there is only one pending image build i do and the next landing should only be rsalveti with multimedia ... who has cyphermox to drive stuff through
[18:41] <ogra_> robru, ^^^
[18:41] <cyphermox> aye?
[18:41] <robru> ogra_, ok
[18:41] <cyphermox> robru: go get better, please :)
[18:42] <ogra_> cyphermox, i'll do an image build now, from then on we wont land anything but ricardos and jims multimedia stuff
[18:42] <robru> cyphermox, ;-)
[18:42] <ogra_> cyphermox, in case that needs a rebuild of anything we need you to do that
[18:42] <ogra_> (for bits in CI)
[18:43] <ogra_> once everything landed there should be a mutlimedia-dedicated image build being done
[18:43] <cyphermox> sure, just ping when there is something
[18:43] <ogra_> yeah
[18:43] <cyphermox> ETA for last rebuild if there are some?
[18:43] <cyphermox> I was planning to go for drinks with a friend tonight ;)
[18:44] <ogra_> cyphermox, depends on rsalveti and jhodapp
[18:44] <ogra_> cyphermox, they are working on some last fixes
[18:45] <cyphermox> ack
[18:47] <rsalveti> yeah, in progress, hopefully in ~2-3h
[18:47] <cyphermox> ok
[19:17] <ogra_> image 68 is in flight (for whom is intrested)
[19:26] <lool> cool
[19:26] <lool> ogra_: without multimedia I take it
[19:26] <lool> there's a regression in ubuntu-download-manager that I might push through tonight if it lands fast
[19:27] <ogra_> yeah, i think thats fine
[19:27] <ogra_> and right, without MM ... thats for 69
[19:27] <ogra_> and i guess it will build very late in the USian day
[19:27] <ogra_> :)
[19:29] <lool> you mean the BRazilian day  :-)
[19:29] <lool> I guess it's half half
[19:32] <ogra_> heh, yeah
[19:34] <lool> ralsina: ping here if something is ready  :-)
[19:34] <lool> ralsina: cyphermox might be around later than I am
[19:34] <ralsina> lool: ack!
[19:35] <cyphermox> I'll still be around for at least an hour
[19:35] <cyphermox> and then I'll be out for an hour or two and back online later
[19:37] <lool> added in LP
[19:57] <vila> lool: no. Just no. Don't call the Landing Plan LP. It's hard enough with MiR these days ;)
[19:58] <vila> lp is launchpad
[19:58] <vila> I meant (?ilp) is launchpad ;)
[19:59] <vila> Call it The Plan instead ;)
[20:06] <ralsina> lool, cyphermox: gatox says mandel's u-d-m branch looks good and no obvious regressions. It has a jenkins failure though, so after that's cleared, it's good to go
[20:07] <ogra_> image 68 is done btw
[20:08] <cwayne_> ogra_, with lightdm + u-t-s? :D
[20:09] <ogra_> cwayne_, yeah
[20:13] <cyphermox> ralsina: what's u-d-m?
[20:13] <ralsina> cyphermox: ubuntu-download-manager, sorry
[20:14] <cyphermox> ok. so I can start that build now, is that what you mean?
[20:26] <cyphermox> ralsina: ^ ??
[20:32] <ralsina> cyphermox: no, we still have not merged, but it will be done as soon as we make jenkins happy
[20:33] <cyphermox> which merge is that?
[20:33] <ralsina> cyphermox: https://code.launchpad.net/~mandel/ubuntu-download-manager/clear-cache/+merge/188141
[20:35] <cyphermox> oh, shiny
[20:37] <mandel> cyphermox, I'm dealing with this, that branch should never land
[20:37] <mandel> cyphermox, it will create corrupted downloads due to race conditions
[20:38] <ralsina> mandel: strangely enough it did not, but sure, let's do the real fix :-)
[20:39] <mandel> ralsina, thanfully those tests were failing!
[20:41] <cyphermox> robru: you back?
[20:43] <robru> cyphermox, sure, what's up?
[20:51] <lool> mandel: good that you catched it  :-)
[20:51] <plars> unity8 tests are running now on build 68
[20:52] <ogra_> it looks beautiful up to now
[20:52] <mandel> lool, no problem, I'm writing a better implementation as we speak and will propose with tests in a few mins
[20:53] <ogra_> (not that the dashboard has much yet though :) )
[20:53] <ogra_> cwayne_, do you have any code branch i should add to the landing sheet for the customization stuff ?
[20:54] <cwayne_> ogra_, it's actually been merged into trunk already, so just lp:ubuntu-touch-customization-hooks
[20:54] <ogra_> thx
[20:56] <cwayne_> ogra_, thanks for adding it :)
[20:56] <ogra_> :)
[20:57]  * cwayne_ will try to ping around monday to get someone on my team write access
[21:12] <ralsina> lool: inconsistent results of click-update-manager tests so re-checking on monday because we are not sure if it's a problem with elopio's device or what.
[21:14] <lool> ralsina: you mean not landing the download manager?
[21:15] <lool> or click-updater?
[21:23] <ralsina> lool: click-updater
[21:23] <mandel> lool, correct fix proposed here => https://code.launchpad.net/~mandel/ubuntu-download-manager/count-ref-cache-management/+merge/188170
[21:24] <ralsina> lool: elopio and mmcc are doing another round of click-updater tests from scratch though. I really want that on monday.
[21:24] <mandel> lool, barry is running the integration tests, I was planning to do that on monday, but hey, better now :P
[21:36] <lool> ok
[21:56] <robru> hmmm, looks like autopilot-intel is down, does anybody know how to get that back up?
[22:08] <lool> robru: There's some kind of remote power management to reboot it, but I don't know how it's handled; raise it with #is?
[22:08] <robru> lool, ok, thanks
[22:37] <rsalveti> lool: robru: cyphermox: can any of you check what is the state of qtvideo-node?
[22:38] <rsalveti> it's merged already, but needs to first land it in the ppa
[22:38] <robru> rsalveti, yes, i see there's a trunk commit from 21 minutes ago. you're wanting that built and packaged?
[22:38] <rsalveti> robru: yup
[22:39] <robru> rsalveti, there's a problem with the builder at the moment. I pinged #is to look at it, not sure on an ETA. I'll try poking at it here
[22:40] <rsalveti> ok, thanks
[22:44] <robru> rsalveti, so, i might be able to trick it into building, but any autopilot tests are going to fail (it's the autopilot machine that's down). as far as i understand it should be able to build in the PPA at least, but we won't be able to get it in distro until some europeans wake up. is that ok for now?
[22:50] <rsalveti> robru: well, guess not much we can do
[22:50] <rsalveti> was planning to land this today, but anyway, lets put it on hold then
[22:50] <robru> rsalveti, well, it should be in the PPA shortly if you want to test it manually. best I can do right now, sorry
[22:51] <rsalveti> robru: yeah, no worries, thanks
[22:51] <robru> rsalveti, https://launchpad.net/~ubuntu-unity/+archive/daily-build/+packages?field.name_filter=qtvideo&field.status_filter=published&field.series_filter= there is it :-)
[22:51] <rsalveti> robru: cool, thanks
[22:52] <robru> rsalveti, actually if you got ahold of an archive admin, you could copy that into distro manually.
[22:52] <rsalveti> yeah, will see, that might be the way to go
[22:52] <robru> rsalveti, it'll definitely be the fastest way if you're in a hurry.
[23:33] <cyphermox> robru: how are things looking atm?
[23:55] <plars> can't seem to get mako to pass completely on those notes tests