[05:02] <Mirv> alecu: please comment on the bug #1297297 marking it "verification-failed" in case you want to stop the SRU process for it and have it removed from trusty-proposed where it now is
[05:04] <alecu> Mirv: sorry, I've not seen it landing, I just saw it as Approved
[05:05] <Mirv> alecu: yeah, it seems the automated message was missing probably because it got into -proposed on release day, but it's indeed there
[05:05] <alecu> great then, let's keep it
[05:05] <Mirv> alecu: ok, so either verify it 'done' or 'failed' after testing so that the package can move in trusty archives
[05:05] <alecu> Mirv: I proposed to reject that merge proposal, because our /devel branch now gets rid of that code altogether
[05:06] <Mirv> right, but it still probably makes sense to have that crash workaround in trusty too?
[05:06] <alecu> Mirv: yes, indeed
[05:06] <Mirv> ok, good to know
[05:06] <alecu> Mirv: but, I will not be able to verify it: the bug is very hard to reproduce
[05:06] <alecu> I only managed to do it once after turning off and on my router about 50 times
[05:07] <alecu> Mirv: I can do the usual testing for the package, though.
[05:07] <Mirv> alecu: right. I guess your team knows the best anyhow on how to verify it. like testing that it does not seem to be regressed in other ways, and that while testing you didn't get crashs.
[05:07] <Mirv> alecu: I think usual testing should be enough, since you're the upstream too there
[05:07] <alecu> great
[05:13] <alecu> Mirv: I'll test it later today (was heading for bed right now...), thanks for pointing this out!
[05:17] <Mirv> alecu: yep, good night, I was expecting you to answer in 12h or so :)
[07:10] <mardy> didrocks: hi! Did you discuss using a branch other than trunk for synchronizing with the archives, in your last meeting?
[07:10] <didrocks> mardy: hey, it wasn't in the discussion IIRC
[07:24] <mardy> didrocks: that's a pity, having to work on other branches (I created "master") is not fun at all
[07:24] <didrocks> mardy: talk with jfunk. He's the one handling those calls and agenda
[07:25] <didrocks> mardy: anyway, this will be automated in the airline, as discussed some months ago
[07:25] <didrocks> mardy: until then, if you want to go to that path, as you did, you can, but you have to deal with it yourself
[07:26] <mardy> didrocks: OK, thanks
[07:30] <didrocks> yw
[08:16] <sil2100> Choo chooo, time for some coffee
[08:19] <didrocks> :)
[08:24] <ogra_> bah, the shell crashed over night while the phone was sitting on my nightstand :(
[08:39] <popey> ogra_: it usually crashes for me in some way (unity/mir or something) when I wake it up after sleep
[08:39] <ogra_> it has done that for the first time for me
[08:40] <ogra_> i usually read on it in bed before sleeping ... usually it is still up in the morning
[08:46] <davmor2> Morning all
[09:40] <popey> Mirv: when you have a moment could you please push http://s-jenkins:8080/view/click/job/filemanager-app-click/lastSuccessfulBuild/artifact/out/com.ubuntu.filemanager_0.3.163_armhf.click file manager to the click store?
[09:58] <Mirv> popey: ok, in a bit
[09:58] <popey> thanks Mirv
[10:07] <bzoltan1> ogra_: do you know who one can tell from adb/shell that the device is up and running with a healthy shell?
[10:08] <ogra_> bzoltan1, adb shell pgrep unit8 ... but that will not tell you andthing about the health or if it is actually visible on screen indeed
[10:08] <ogra_> *unity8
[10:08] <ogra_> *anything
[10:09] <popey> cihelp, can someone cleanup so i can build reminders please? s-jenkins:8080/view/click/job/reminders-app-click/15/console
[10:09] <popey> hudson.util.IOException2: remote file operation failed: /home/ubuntu/jenkins/workspace/reminders-app-click at hudson.remoting.Channel@135a132e:cyclops-node10
[10:12] <psivaa> popey: looking
[10:13] <popey> thanks
[10:14] <bzoltan1> ogra_: that is something, thanks... I try to detect  from the QtCreator if the emulator is up or not
[10:18] <psivaa> popey: that job appears going ok now. on a different node though. pls ping us back if you still see issues
[10:20] <popey> ok, ta
[10:36] <Mirv> popey: just to reassure, http://s-jenkins:8080/view/click/job/filemanager-app-click/122/artifact/out/com.ubuntu.filemanager_0.3.163_armhf.click ? the previous url timed out since there is .164 now
[10:36] <popey> Mirv: yes, 163 please
[10:39] <popey> thanks Mirv
[10:40] <Mirv> popey: np, https://myapps.developer.ubuntu.com/dev/click-apps/159/
[10:55]  * didrocks goes for a run
[12:37] <sil2100> Jumping out for a minute to drive my girl to the train station
[12:37] <sil2100> brb
[12:54] <sil2100> Back
[12:57] <ogra_> Front
[13:05] <seb128> Rear
[13:06] <kgunn> didrocks: my apologies....can we chat now? had a family issue come up i need to take care of in 30 min
[13:07] <didrocks> kgunn: sure, no worry
[13:07] <davmor2> sil2100: surely you drive a car not a girl that's just cruel
[13:08] <kgunn> didrocks: https://plus.google.com/hangouts/_/canonical.com/quick-sync-on
[13:08] <didrocks> kgunn: yeah, already there!
[13:10] <dbarth> sil2100: o/ line 36ready;
[13:11] <dbarth> sil2100: i removed one branch though, but that makes the silo request more coherent (ie, all for fixing google apps)
[13:11] <sil2100> dbarth: o/
[13:11] <sil2100> dbarth: the bugs are SRU ready there?
[13:11] <sil2100> davmor2: ;p
[13:12] <davmor2> sil2100: you're only doing that because you know I'm right ;)
[13:12] <dbarth> sil2100: they are SRU'ed yes
[13:15] <sil2100> dbarth: thanks! Will assign in a moment, need to resolve something first
[13:16] <dbarth> sil2100: cool
[13:20] <sil2100> uh
[13:20] <sil2100> bregma: why did you run merge-and-clean with the ignore flag?
[13:20] <sil2100> didrocks: ^
[13:21] <sil2100> bregma: compiz and unity are still in UNAPPROVED, they didn't even get to -proposed yet - it seems very risky to me
[13:21] <bregma> the binaries are in unapproved, no?
[13:21] <sil2100> Yes, but what if they get rejected still?
[13:21] <sil2100> You'll have the release in trunk, but there will be nothing in the archive
[13:21] <bregma> if they don't get approved we need to do new patches anyhow
[13:22] <sil2100> Trunk will be out-of-sync with the archive, which is exactly what we don't want happening
[13:22] <sil2100> Please don't use the ignore flags without asking the landing team before doing that - or maybe you talked already with didrocks or Mirv about this?
[13:22] <bregma> apologies
[13:23] <seb128> bregma, sil2100: one other issues is that "syncs" are not real copies, they are pointers to the librarian, when you clean the ppa the original sources is going to be garbage collected
[13:23] <sil2100> seb128: yeah, they're around for 7 days after deletion though, but only 7
[13:23] <seb128> so the items in the queue might become un-usable
[13:23] <seb128> right
[13:23] <seb128> hopefully the SRU team gets to those before they are claimed abck
[13:23] <seb128> back
[13:23] <sil2100> didrocks: ^ just so you know that such a situation happened
[13:24] <didrocks> one sec, back from meeting
[13:24] <didrocks> backlogging
[13:24] <bregma> hopefully it won;t take >7 days for approval for these fixes, they're for pretty serious bugs
[13:24] <sil2100> dbarth: soooo, anyway, regarding the silo! So, webbrowser-app seems blocked by your earlier SRU - I can free it as it's already in -proposed, but it would be awesome if you could assign someone from your team to do the testing of the package in proposed
[13:24] <didrocks> bregma: please don't use flags without coordinating with the LT
[13:24] <didrocks> first
[13:25] <sil2100> dbarth: working on changing it from verification-needed to verification-done :)
[13:25] <sil2100> dbarth: as long as you tell me it's being worked on and tracked, then I will 'land' the silo and assign the other one
[13:26] <didrocks> bregma: well, please push for your SRUs to get approved now
[13:26] <didrocks> bregma: we won't do the tracking, it will be off our radar
[13:26] <dbarth> sil2100: i did the testing personally and commented on the bug
[13:26] <sil2100> \o/
[13:26] <dbarth> sil2100: but i thought we'd need someone external
[13:26] <sil2100> FAST
[13:26] <dbarth> sil2100: i did it this week ;)
[13:26] <sil2100> dbarth: ok, yeah, it's best if it's not the one fixing the bug ;p
[13:26] <dbarth> right, judge and party
[13:27] <sil2100> dbarth: but if you already said +1 on it, at least we know it's not completely broken
[13:27] <dbarth> sil2100: that, i can attest
[13:27] <sil2100> Ok, so I'm landing that and tracking so it doesn't get lost
[13:27] <sil2100> Thanks!
[13:27] <dbarth> sil2100: i'd say land, yes, since it goes in -proposed
[13:27] <dbarth> sil2100: hold on though
[13:27] <dbarth> sil2100: to check we're talking of the same bug
[13:28] <dbarth> sil2100: we're talking about line 22, right?
[13:28] <sil2100> dbarth: yeah, I see the comment on one of the bugs tehre
[13:28] <dbarth> ok, we're good then
[13:28] <sil2100> There is still this one without comment, but well, we can land it in trunk anyway, as -proposed is -proposed
[13:28] <sil2100> https://bugs.launchpad.net/webbrowser-app/+bug/1309138
[13:29] <dbarth> sil2100: yup please, i tested it 3 times in silo, so i doubt it can go that wrong
[14:39] <seb128> didrocks, sil2100, bregma: compiz/unity SRU accepted
[14:40] <didrocks> great!
[14:40] <didrocks> thanks for the hint
[14:42] <seb128> yw!
[14:44] <sil2100> o/
[14:45] <sil2100> Thank you :)
[15:46] <alecu> Mirv: I've installed #302 on the phone from scratch, installed the click-scope from proposed and I've followed the test plan for it.
[15:46] <alecu> Mirv: everything works fine for me.
[15:46] <alecu> Mirv: should I tag that bug as verified? https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1297297
[16:01] <didrocks> robru: around the corner?
[16:02] <didrocks> ogra_: nothing for you I guess, but you can join
[16:02] <ogra_> ah, then i'll take the opportunity to skip today
[16:02] <ogra_> :)