[00:07] <asac> kgunn: let me read
[00:08] <asac> kgunn: so not sure i read correctly, but i think you say that you need more componments changed to make a MP test succeed?
[00:09] <asac> kgunn: if so, yes, you are right. in theory the silo and CI could be merged
[00:09] <kgunn> asac: yeah...that's it basically...the CI run either has additional components or access allowed to those components specifcally for the arm builds
[00:10] <asac> kgunn: right. so what we lack is a UI to propose multi component MPs
[00:10] <kgunn> so if silo == ci...that'd solve that problem
[00:10] <asac> kgunn: but thats where we are moving to kind of
[00:10] <asac> kgunn: think of the spreadsheet being a webUI where you put your MPs and then get answers on the complete set, can comment etc.
[00:10] <kgunn> sure...problem solve for the moment...i'll just supress my arm integration tests when i go to the train
[00:10] <asac> kgunn: right. for now we said, that if component tests are failing the lander can make the call to move on
[00:11] <asac> kgunn: the component test (which you call CI) are just there to support youre review decision, but we dont even have in the checklist that those must succeed
[00:11] <kgunn> yeah...and we feel safe because we see those tests passing all the time on ci
[00:11] <asac> kgunn: so the term CI is not aligned :) ... for me the WHOLE thing is CI. the MP thing is just a review bot :)
[00:11] <asac> hehe
[00:11] <asac> because we dont integrate there anymore
[00:13] <asac> i think CI made sense when it was just local focussed. but before the train was there, you didnt even havea chance to test, while once we connect a bot to the silo you at least get the real deal
[01:58] <robru-sick> bregma, please clean silo 1
[01:58] <robru-sick> bfiller_afk, please clean silo 12
[02:19] <bregma> robru-sick, it looks like lp:unity is fuxxored
[02:20] <bregma> been trying to merge for a while now, it just times out, can;t play with it remotely either
[02:26] <robru-sick> bregma, strange, I just branched lp:unity. not sure why that wouldn't be working.
[02:27] <robru-sick> bregma, can you manually push from lp:~ps-jenkins/unity/latestsnapshot-recup to lp:unity?
[02:28] <robru-sick> bregma, looks like bschaefer is pushing direct to lp:unity trunk, that could be a potential cause...
[02:29] <bregma> robru-sick, I'm still trying to check out the recup branch, but we've been trying to do some other stuff and it all ends in tears (or at least timeout)
[02:29] <bschaefer> robru-sick, yeeah i messed up
[02:29] <bregma> I suspect the LP database may be in a bad state
[02:29] <bschaefer> with the pushing bit
[02:29] <robru-sick> bschaefer, no worries, it can be fixed
[02:29] <asac> robru-sick: how are landings going tonight?
[02:30] <bschaefer> robru-sick, did a dam push :parent (in an lp:unity branch :/)
[02:30] <bschaefer> robru-sick, well thats always nice to hear
[02:30] <robru-sick> asac, there weren't too many that I saw today, just a couple small ones. lp:unity seems to be in a weird state (failing to merge & clean the silo) but shouldn't be too hard to fix
[02:31] <asac> robru-sick: ok. are we still double checking everything?
[02:31] <robru-sick> bschaefer, oh, so should both the recent commit and the recent merge be reverted?
[02:31] <robru-sick> asac, yes
[02:31] <bschaefer> robru-sick, correct the last two (as they were part of the same branch)
[02:32] <bschaefer> robru-sick, i attempted a push --overwrite after an uncommit on both revs, but it just hanged
[02:32] <asac> good
[02:32] <asac> thx
[02:32] <robru-sick> asac, no worries
[02:32] <robru-sick> bschaefer, hmmmm, i was just going to try that ;-) i wonder why it's acting like this...
[02:32] <asac> robru-sick: do we have a backlog or is everyone - except those with issues - kind of moving?
[02:33] <bschaefer> robru-sick, very strange indeed...it get a:
[02:33] <bschaefer> Connection Timeout: disconnecting client after 300.0 seconds
[02:33] <bschaefer> ConnectionReset reading response for 'Branch.set_last_revision_info', retrying
[02:33] <bschaefer> I get a:
[02:33] <bschaefer> when i just leave it
[02:33] <robru-sick> asac, i think everybody is kind of moving. the biggest blockage I was aware of was kgunn's mir landing, blocked by tvoss doing a platform-api landing, but that landing got booted and kgunn is on the way, despite some hiccups with build failures.
[02:33] <asac> good point
[02:33] <robru-sick> bschaefer, yeah, that's the same issue that just happened when trying to clean the silo.
[02:34] <asac> kgunn: do you feel this could have been done better?
[02:34] <asac> kgunn: e.g. without booting tvoss?
[02:34] <bschaefer> i wonder if its stuck trying to do something...
[02:35] <robru-sick> bregma, bschaefer : uhhh, why does lp:unity point at https://code.launchpad.net/~unity-team/unity/trunk-bad ?
[02:35] <bregma> robru-sick, I just did that, I'm just trying something
[02:36] <robru-sick> bregma, ok ok I won't interfere
[02:36] <robru-sick> bregma, bschaefer, asac: I gotta step out for dinner but I'll be around later if anybody needs anything from me
[02:36] <asac> sure
[02:36] <bschaefer> robru-sick, have a good dinner!
[02:36] <asac> bregma: what are you trying?
[02:36] <robru-sick> thansk
[02:36] <asac> bregma: if that helps to get a merge & publish?
[02:37] <asac> e.g. did someone just commit to trunk without a landing :)?
[02:37] <bschaefer> asac, that would be me
[02:37] <asac> direct commit to trunk?
[02:37] <bschaefer> asac, yuuup, trying to push to different branch but used :parent (thinking i was in my own branch)
[02:37] <bregma> asac, the merge and clean has already gone through, it;s just a matter of recovering the trunk and getting the saved merge into it
[02:38] <asac> bschaefer: heh. i see. yeah
[02:38] <asac> reset :)
[02:38] <asac> ic
[02:38] <asac> bregma: ok. no problem.
[02:38] <asac> you feel we should protect you guys from accidentially pushing? think foundations took the route of creating a new team
[02:38] <asac> so that noone can accidentially push
[02:39] <bschaefer> well it normally isn't to hard to recover, but when i attempted an uncommit, then bzr push --overwrite
[02:39] <bschaefer> thats when it started hanging
[02:41] <asac> ic
[02:41] <asac> who knows if the ci train resolves the target path early on
[02:41] <asac> hope that a -bad redirect could work
[02:42] <bschaefer> if a direct push directly causes this then there really is no point of having direct push access :)
[02:42]  * bschaefer hasn't done this before
[02:42] <asac> i think there shouldnt be a reason to direct push. but then i dont think we shouldnt be able to reset :)
[02:43] <bschaefer> I agree
[02:43] <asac> if you cannot push --overwrite, talk to wgrant
[02:43] <asac> he might be able to dive into that for you
[02:43] <asac> or cprov :)
[02:43] <wgrant> Hm hm?
[02:44] <asac> 03:39 < bschaefer> well it normally isn't to hard to recover, but when i attempted an uncommit, then bzr push --overwrite
[02:44] <bschaefer> well hopefully bregma can pull something off
[02:44] <asac> 03:39 < bschaefer> thats when it started hanging
[02:44] <cprov> oi
[02:44] <wgrant> push --overwrite won't override append_revisions_only.
[02:44] <asac> oh
[02:44] <wgrant> You'd need to unset that flag, push --overwrite, and then reset it
[02:44] <asac> ok i guess we should really move the trunk into a safe area where accidential pushes dont happen :)
[02:44] <asac> bregma: ^^ :)
[02:45] <asac> there is your solution
[02:45] <asac> but set that flag again after i guess
[02:45] <asac> wgrant: thanks for the hint
[02:45] <bschaefer> wgrant, thanks!
[02:46] <bregma> wgrant, how does one unset that flag?
[02:46] <wgrant> bregma: 'bzr config -d lp:unity append_revisions_only=False' should do it.
[02:47] <bregma> cool
[02:47] <wgrant> But it's also usually a good idea to have bot-managed branches owned by the bot.
[02:47] <asac> +1
[02:47] <wgrant> eg. Launchpad's trunks are all owned by ~launchpad-pqm
[02:48] <wgrant> I can't push to them even if I try.
[02:50] <asac> wgrant: that is not even a team
[02:51] <asac> wgrant: who can do stuff in case something goes bad?
[02:51] <asac> guess credentials are avail to trusted folks?
[02:51] <wgrant> asac: Right
[02:52] <asac> ok guess we could do that and give credentials to ci infra/vanguard folks for now
[02:52] <wgrant> Usually we'll do stuff from the bot's machine.
[02:52] <asac> right
[02:52] <asac> thats enough safety
[02:52] <wgrant> A team sort of defeats the purpose, because members of the team can still push to the branch
[02:52] <asac> ack
[02:52] <asac> well, if the team has zero business to push it is still ok i guess
[02:53] <asac> just an indirection more to grant that team access to the machine :)
[02:53] <wgrant> (I'd like to eventually have special delegated bot accounts that you can sort of sudo to, but this works for now)
[02:53] <asac> but yeah, we should just adopt that model
[03:10] <kgunn> asac: in this instance...the lock was on platform-api, but voss only needed to rebuild it (no code change)..so i could have been in a silo ssooner.....and of course i have silo hiccups of my own
[03:11] <asac> ok. i think its a special case of auto rebase (with zero change)
[03:12] <asac> kgunn: silo hiccups?
[03:12] <asac> infra issues? or personal problems :P?
[03:12] <kgunn> asac: sorry...of my own creation :)....no problem with silo itself
[03:12] <kgunn> personal probs :)
[03:13] <asac> hehe
[03:13] <asac> drugs and stuff ic
[03:13] <asac> :P
[03:13] <asac> j.k. (its late)
[03:14] <asac> kgunn: can you subscribe and attend the landing process vUDS session please?
[03:14] <asac> i think you have very valuable experience and could report
[03:15] <asac> and explain and help finding good balance
[03:15] <kgunn> you bet
[03:15] <asac> i assume that was on drugs :P
[03:15] <asac> lol
[03:15] <kgunn> and yes...it is late for you...good grief man go to sleep
[03:16] <asac> kgunn: i am in a different TZ :)
[03:16] <asac> kgunn: i am sitting next to salveti basicallyu
[03:16] <asac> still past midnight
[03:16] <kgunn> ah!! carnival hangover
[03:16] <asac> yep :)
[03:16] <kgunn> oh ash Wed actually...no more party till sunday
[03:16] <asac> hehe
[03:17] <asac> not even sure if there will be more parties. had enough, but have to slowly reduce the alcohol exposure :)
[03:18] <asac> ttyt
[03:18] <bschaefer> asac, thanks for the help!
[03:18] <asac> yw!
[04:00] <bfiller_afk> robru-sick: please land silo-002, testing complete even though the status isn't updating
[04:00] <robru-sick> bfiller_afk, oh ok
[04:02] <robru-sick> bfiller_afk, are you sure? the packages in the silo are from march 3rd. that rebuild you tried to do never happened...
[04:03] <bfiller_afk> robru-sick: I tested from the ppa, not sure a rebuild was necessary I was just confused that it was red so I tried to rebuild
[04:03] <robru-sick> bfiller_afk, ah ok, i thought there were new commits you wanted to trigger a build for
[04:04] <bfiller_afk> robru-sick: no, not sure how it got to that red status though. maybe someone tried building after it had already built?
[04:04] <bfiller_afk> let me double check the MR's
[04:04] <robru-sick> bfiller_afk, most likely yea, the current red status is caused by somebody hitting build after it build
[04:05] <robru-sick> bfiller_afk, although that somebody is you ;-) http://162.213.34.102/job/landing-002-1-build/54/console
[04:06] <bfiller_afk> robru-sick: I did try to rebuild it after I saw it was red, someone must have done it before me too?
[04:06] <robru-sick> bfiller_afk, the MPs look good thought, just confirmed there's no unbuilt commits
[04:06] <bfiller_afk> robru-sick: same, lets land it then
[04:07] <robru-sick> bfiller_afk, according to the build log, build 53 was started by Laney and was successful, build 54 was started by you and failed, and build 55 was started by you and also failed. each one approximately a day apart.
[04:07] <robru-sick> bfiller_afk, right, landing
[04:08] <bfiller_afk> robru-sick: hmn, that's weird. don't remember doing it but I am losing my mind so I must have
[04:08] <robru-sick> bfiller_afk, i dunno, maybe there was a glitch in the spreadhseet, who's to say? I have no idea what you say. but according to the backend, laney's build was fine and you're the one who did the failing builds ;-)
[04:09] <robru-sick> "no idea what you saw"
[04:09] <robru-sick> bfiller_afk, hit publish, just checking the packaging diffs here
[04:12] <robru-sick> bfiller_afk, hmmmm it's so late. need to find a core dev at this hour...
[04:13] <bfiller_afk> robru-sick: don't worry about it
[04:13] <robru-sick> bfiller_afk, then again Laney wrote all this code...
[04:13] <bfiller_afk> I'll tell laney tomorrow that it's all tested and he can get it in I'm sure
[04:13] <robru-sick> bfiller_afk, I was told I needed an ack from a core dev before I'm allowed to publish packaging changes. but if the packaging changes were written by Laney, is it my place to question them? hmmmmm
[04:13] <robru-sick> bfiller_afk, ok, sorry
[04:14] <bfiller_afk> robru-sick: no worries at all
[04:14] <bfiller_afk> robru-sick: Laney will know it's acked and get it punched in
[04:14] <robru-sick> bfiller_afk, ok
[04:14]  * bfiller_afk calling it a night
[04:14] <bfiller_afk> robru-sick: have  good one :)
[04:14] <robru-sick> bfiller_afk, goodnight! I'm also EOD 2 hours ago ;-)
[05:00] <kgunn> fginther: dude are you really on ?
[05:01] <kgunn> anyone in here know how to reconfig a silo ?
[05:02] <kgunn> cyphermox: ^ you happen to be on ?
[05:02] <kgunn> silo 3 if anyone can help
[05:02] <cyphermox> been trying to go to bed ;)
[05:02] <cyphermox> sure, I can
[05:02] <kgunn> hey thanks...and sorry
[05:02] <cyphermox> kgunn: the list of commits is correct in the spreadsheet in Pending?
[05:02] <kgunn> ooo....you're in montreal...late, really sorry
[05:02] <cyphermox> kgunn: don't worry about it
[05:03] <cyphermox> I was coding
[05:03] <kgunn> cyphermox: yeah...i just update the list of mp's...i removed one
[05:03] <kgunn> that was ...ummm...problematic :)
[05:04] <cyphermox> ok
[05:05] <kgunn> cyphermox: thanks a bunch...happy coding
[05:07] <cyphermox> in progress
[05:07] <cyphermox> very happy hacking in fact
[05:08] <cyphermox> we've had some progress this week
[05:10] <Mirv> hmm
[05:10] <Mirv> you guys are up late :)
[05:12] <Mirv> kgunn: unity-mir just seems to have failed to build at the silo https://launchpad.net/~ci-train-ppa-service/+archive/landing-003/+packages
[05:12] <Mirv> (armhf still building)
[05:13] <cyphermox> Mirv: I just reconfigured the silo
[05:13] <kgunn> Mirv: i just rekicked like 5 min ago
[05:13]  * Mirv finds http://162.213.34.102/job/landing-003-1-build/54/console
[05:13] <Mirv> great
[05:13] <kgunn> make me have a heart attack :)
[05:14] <kgunn> been wrestling with it all afternoon/evening
[05:14] <Mirv> kgunn: still, I believe this one is a new build https://launchpad.net/~ci-train-ppa-service/+archive/landing-003/+sourcepub/3957606/+listing-archive-extra
[05:14] <Mirv> "published 1 minutes ago"
[05:14]  * kgunn makes a note Mirv is an early bird
[05:14] <cyphermox> ah, I see yeah
[05:15] <Mirv> kgunn: wife wakes up at 6am so I have to be
[05:15] <cyphermox> it's indeed a build failure for amd64 and such
[05:15]  * cyphermox fades away
[05:17] <kgunn> Mirv: i may have done something naughty/not supported.... so i just had cyphermox do a reconfig (as i deleted a mp for unity-mir)...but then, when i went to the build page i typed "unity-mir" in the box to limit..but also checked forcerebuild....
[05:17] <kgunn> can i do that ?
[05:17] <kgunn> or if you reconfig...are you forced to rebuild all
[05:17] <kgunn> ?
[05:18] <cyphermox> if it didn't change it shouldn't be the biggest issue, but it would be nice to have everything rebuilt, otherwise you risk running into fun issues later on, with already-merged stuff
[05:19] <kgunn> alright...just force building all now...ug
[05:25] <Mirv> kgunn: yes, it should work
[05:25] <Mirv> sorry, I already got drifted to my usual Qt 5.2 universe
[05:25] <kgunn> Mirv: hmmm,,,,
[05:25] <kgunn> thats ok
[05:27] <Mirv> after reconfiging yes some sort of build needs to be done. sometimes force rebuild, or if simply adding more branches then it's not needed.
[05:27] <Mirv> ok, they're building again
[05:46] <Mirv> unity-mir seems to continue to fail.. on some mock stuff? error: 'class testing::NiceMock<testing::MockProcInfo>' has no member named 'gmock_command_line_'
[06:21] <Mirv> I'm merge+cleaning landing-002 since it has landed and I need to free up ubuntu-system-settings for Qt 5.2
[06:49] <kgunn> Mirv: ok...think there's a bug in the landing sheet...so i watched real close this time...
[06:49] <kgunn> you'll notice it tries to merge an mp https://code.launchpad.net/~andreas-pokorny/unity-mir/fix-1281075
[06:49] <kgunn> http://162.213.34.102/job/landing-003-1-build/57/console
[06:50] <kgunn> toward the bottom where i halted it
[06:50] <kgunn> ....and that's exactly the mp i had removed & had cyphermox reconfigure for
[06:50] <kgunn> and i note it really is not listed in the mp list...
[06:51] <kgunn> and this is happening after i did a full force rebuild
[06:55] <Mirv> kgunn: sounds right, since it's not listed in cyphermox's prepare-silo http://162.213.34.102/job/prepare-silo/376/console
[06:56] <Mirv> I guess the silo could be freed and reassigned as a measure
[06:56] <Mirv> then it could be ready by the time sil2100+didrocks come online
[06:57] <kgunn> Mirv: ok, thanks...so i'll leave it with you to decide, but i'll hope to be back at it in about 6 hrs
[06:58] <Mirv> kgunn: good night!
[06:58] <Mirv> I'll try to get it built
[06:58] <kgunn> thanks a bunch...see you in the morn
[07:31] <Mirv> kgunn: didrocks: interestingly maybe there was just a delay. I tried forcing one more rebuild of unity-mir, and now it has built.
[07:31] <Mirv> (kevin removed one unity-mir MR but the next build after cyphermox's prepare-silo still included that MR)
[07:40] <didrocks> Mirv: I guess they just didn't set the build-dep correctly
[07:52] <Mirv> I'm trying to fix the biggest powerpc issue by disabling qtbase tests on non-i386/amd64/armhf, in case that'd help to keep status quo for powerpc at least
[07:56] <didrocks> yeah
[08:02] <cjwatson> Mirv: you should get ppc64el builds for anything that goes into a silo now, in case that helps
[08:03] <cjwatson> Mirv: also did you notice the announcement about powerpc/ppc64el porter boxes?
[08:04] <cjwatson> (to ubuntu-engineering@)
[08:09] <tvoss> sil2100, around?
[08:22] <Mirv> cjwatson: yes, it gives even more failing builds :) I noticed the message, that's nice. the Qt landing is just so huge that I couldn't even think about powerpc, but now I think this workaround should restore status quo and then I can rebuild even some extra packages now that qtdeclarative is compatible with powerpc.
[08:24] <cjwatson> Mirv: Right, and hopefully the powerpc fix won't involve breaking ABI ...
[08:24] <cjwatson> Mirv: But I had a brief look and it seems to be being built with _LARGEFILE_SOURCE etc., so hopefully that's not too deep
[08:25] <cjwatson> (Also hopefully Qt isn't so broken on powerpc it can't build anything else, but I guess if largefile is the first test that fails then it isn't awful)
[08:26] <cjwatson> Did ppc64el get anywhere at all?
[08:27] <Mirv> cjwatson: powerpc did build before we enabled tests already, so I believe it will build now again after I run tests only on amd64/i386/armhf
[08:28]  * cjwatson nods
[08:30] <cjwatson> Of course a lot of your ppc64el failures are simply because the qtbase build predates ppc64el being turned on for ci-train
[08:41] <sil2100> tvoss: yes yes
[08:44] <sil2100> What the...
[08:46] <sil2100> bregma: hello!
[08:48] <sil2100> bregma: could you take a look at line 28 in the landings? I see some unity7 merges there, but all of them are already 'merged'
[08:49] <sil2100> Could it mean we had some spreadsheet problems?
[08:58] <sil2100> Mirv: I don't see your Qt landing in the spreadsheet - is that on purpose?
[09:00] <Mirv> sil2100: maybe it's just too big for you? :)
[09:01] <Mirv> sil2100: it's the line 14 but if you try to see it it scrolls down to line 15 already
[09:02] <sil2100> ah!
[09:02] <sil2100> Mirv: hah! Right! Stupid google ;)
[09:03] <seb128> sil2100, seems like the unity7 got cleaned merged back in http://162.213.34.102/job/landing-001-3-merge-clean/33/
[09:03] <seb128> sil2100, you ran 34 in the same silo a bit earlier with "only free silo" then?
[09:03] <sil2100> seb128: yes, since I saw a landing for unity7 and assigned a silo, but then noticed that all the merges there are already 'merged'
[09:04] <sil2100> So I freed the silo until I get more info
[09:04] <seb128> oh ok
[09:04] <Mirv> sil2100: to sum up pre-meeting, I will be blocked by the 1. mir landing 2. line 6 bfiller's landing and 3. unity-scope-click landing some time before EOD. but in case those three are still to be tried to be landed while also Qt 5.2 DPR bug remains unfixed and has not yet been decided to not be a blocker, I'm arranging so that I can leave those ~15 packages uncompiled for now
[09:05] <sil2100> Mirv: ok, awesome
[09:07] <Mirv> sil2100: regarding Mir kevin was still up when I woke up, and mathieu was helping him with the silo. unity-mir resisted compiling, but I got it compiled some time after kevin went to sleep. so I believe the silo would be ready to test
[09:11] <sil2100> Mirv: but since there seems to be an ABI break, shouldn't we include xorg-server in the Mir silo as well?
[09:15] <Mirv> sil2100: I'm not really familiar with the landing in general, I remember seeing didrocks talking with kgunn yesterday
[09:15] <didrocks> only if there is a libclient ABI break
[09:15] <didrocks> libmirclient*
[09:21] <sil2100> Ah, right, they only mention 'server' breakage
[09:21] <sil2100> Shock!
[09:28] <sil2100> hmmm
[09:44] <popey> Mirv: http://imgur.com/3PJd9G1,b9Q0VKc,pBu9F1W,B18ZwIN,JehiX1r,6swNKbI#5 "lol" ☻
[09:55] <sil2100> bregma: give me a poke once you're around!
[09:56] <seb128> bregma, he's leaving in Canada and it's like middle of the night there, wait a few more hours I think
[09:56] <seb128> ups
[09:56] <seb128> sil2100, ^
[09:56] <sil2100> seb128: oh, always thought he was from the EU timezone
[09:56] <sil2100> Whooops
[09:56] <sil2100> Thanks
[09:57] <didrocks> sil2100: let's look at what happened, do you remember which silo # was the unity7 landing?
[09:58] <seb128> sil2100, but if that's about the unity silo, he merged back yesterday, if there is an issue is on the gdoc side, e.g I don't think he's going to have lot of useful info on that part for you
[09:58] <sil2100> http://162.213.34.102/job/landing-001-1-build/49/consoleFull
[09:58] <seb128> didrocks, silo 1
[09:58] <sil2100> seb128: well, but we see the trunk is not as it's supposed to be
[09:58] <seb128> didrocks, http://162.213.34.102/job/landing-001-3-merge-clean/33/
[09:58] <seb128> is the merge back from bregma during the night
[09:59] <sil2100> seb128: there are actually release commits made by Stephen himself
[09:59] <sil2100> And trunk is very very different from the staging trunk that is prepared by CITrain
[09:59] <sil2100> seb128: hah, I see bregma only 'freed' the silo without merging it in ;/
[10:00] <didrocks> yeah
[10:00] <sil2100> Started by user Stephen M. Webb
[10:00] <didrocks> 2014-03-06 02:22:17,391 INFO Only free silo, ignoring all checks and merging branches
[10:00] <seb128> http://irclogs.ubuntu.com/2014/03/06/%23ubuntu-ci-eng.html#t02:20
[10:00] <sil2100> 2014-03-06 02:22:17,391 INFO Only free silo, ignoring all checks and merging branches
[10:00] <didrocks> http://162.213.34.102/job/landing-001-3-merge-clean/32/console
[10:00] <didrocks> robru-sick, I'm still trying to check out the recup branch, but we've been trying to do some other stuff and it all ends in tears (or at least timeout)
[10:00] <seb128> so yeah, it's in the night IRC backlog
[10:00] <didrocks> that what he told
[10:00] <didrocks> that's why he couldn't get the recup branch
[10:02] <didrocks> sil2100: in the case, if he doesn't want to --override, just ensure that trunk is tagged appropriately
[10:02] <sil2100> didrocks: ok
[10:05] <sil2100> brb, modem re-kick
[10:14] <sil2100> thostr_: silo assigned for you
[10:15] <thostr_> sil2100: thanks
[10:29] <dbarth> hiya
[10:29] <dbarth> sil2100: i have a new request in the spreadsheet, can i have a silo?
[10:29] <dbarth> line 33
[10:29] <dbarth> seb128: hey, i see you're on the entry, this should hopefully fix the dependency problem
[10:30] <seb128> dbarth, yeah, I was just reviewing the diff, looks fine to me
[10:31] <didrocks> dbarth: the fixes for online account and the other reverted components will come later on?
[10:31] <didrocks> dbarth: I wonder as well (Laney can help) if the new funcationality itself is asking for a FFe
[10:31] <dbarth> didrocks: the branches are still all on trunk afaics
[10:31] <seb128> dbarth, didrocks: I think that branch/diff applies on top of the code-before-revert
[10:31] <didrocks> (as it's not covered by touch FFe)
[10:32] <Laney> yes
[10:32] <dbarth> but yeah, there is another branch to disable the ap tests that fail
[10:32] <didrocks> dbarth: right, but it's not in the distro, so if you want to reland them, you need at least an empty MP
[10:32] <didrocks> and yeah, get a FFe as per Laney's ;)
[10:33] <dbarth> https://code.launchpad.net/~mardy/ubuntu-system-settings-online-accounts/fix-ap-tests/+merge/209463
[10:33] <dbarth> didrocks: i have a non-void branch for webbrowser-app
[10:33] <dbarth> didrocks: but so should i add one for each of the other components as well?
[10:33] <dbarth> ie, signon-ui, etc.
[10:33] <didrocks> dbarth: yeah, for all components where you have no other branches
[10:34] <didrocks> (there are 2 IIRC)
[10:34] <dbarth> ok
[10:34] <didrocks> friends-app and signon-ui
[10:34] <dbarth> sil2100: i stand corrected ;) will update the branch list quickly
[10:36] <dbarth> mardy: ping? i need 2 empty MPs for friends-app and signon-ui please
[10:37] <mardy> dbarth: ah, ok
[10:40] <mardy> dbarth: https://code.launchpad.net/~mardy/friends-app/silo/+merge/209635 https://code.launchpad.net/~mardy/signon-ui/silo/+merge/209634
[10:40] <dbarth> cool thanks
[10:41] <ogra> grr ... it would help if my manta wouldnt be constantly dead and out of battery :(
[10:42] <dbarth> sil2100: branch list ready, line 33
[10:42] <dbarth> (will have another request shortly for webapps as well btw)
[10:51] <dbarth> sil2100: line 34 is ready as well if i can get a silo for it
[10:51] <dbarth> thanks
[11:04] <psivaa> didrocks: on the gallery app and mediaplayer app test reruns mediaplayer came back with no failures but gallery-app has failed one test each on 2 reruns
[11:04] <psivaa> didrocks: galler-app crash was seen on both the reruns
[11:07] <didrocks> psivaa: ok, making sense, thanks a lot for the retries :)
[11:07] <psivaa> yw :)
[11:08] <didrocks> hum, seem sil2100 isn't around…
[11:08] <dbarth> didrocks: do you have time for my 2 requests maybe?
[11:08] <didrocks> dbarth: ready is still set to "No". Did you get the FFe then?
[11:08] <dbarth> oh i need an ffe for that?
[11:09] <dbarth> i hadn't looked at the comment
[11:09] <dbarth> reading
[11:09] <didrocks> dbarth: the previous uploaded needed it
[11:09] <didrocks> so if you want to reenable it, I think you need the FFe (see our discussion with Laney)
[11:09] <dbarth> ok, good, will do
[11:09] <dbarth> still i'd like to get silos, if available, to test that asap
[11:10] <didrocks> sure, can you turn ready to Yes?
[11:11] <didrocks> hum
[11:11] <didrocks> ERROR:root:signon-ui is already prepared for the same serie and destination in landing-006
[11:12] <didrocks> Timo, can you release the lock on signon-ui?
[11:12] <didrocks> Mirv: ^
[11:12] <didrocks> same for:
[11:12] <didrocks> ERROR:root:ubuntu-system-settings-online-accounts is already prepared for the same serie and destination in landing-006
[11:12] <didrocks> ERROR:root:webbrowser-app is already prepared for the same serie and destination in landing-006
[11:12] <dbarth> didrocks: done (33 and 34)
[11:12] <didrocks> ERROR:root:friends-app is already prepared for the same serie and destination in landing-006
[11:13] <didrocks> Mirv: just reconfigure without the MPs I guess, then, we'll readd them and rebuild
[11:13] <didrocks> dbarth: for 33, we need to wait for ^
[11:14] <dbarth> sure
[11:14] <didrocks> dbarth: for 34, those links are not MPs
[11:14] <dbarth> doh
[11:15] <dbarth> didrocks: they should now
[11:16] <didrocks> hum, same issue, Mirv: ERROR:root:unity-webapps-qml is already prepared for the same serie and destination in landing-006
[11:16] <didrocks> dbarth: FYI ^
[11:23] <dbarth> ah right, but that's the null MP here; hope we're not making too much of a mess here
[11:26] <sil2100_> grrrr
[11:31] <popey> have we had an update to dialer-app recently?
[11:31] <popey> or maybe pulse
[11:32] <popey> hmm, telephony-service...
[11:33] <didrocks> popey: ofono, 2 days ago, telephony-service, 3 days ago
[11:35]  * popey files bug
[11:35] <popey> (sorry)
[11:37] <didrocks> :p
[11:37] <sil2100_> ;p
[11:37] <didrocks> regression?
[11:38] <davmor2> popey:  what bug, I've just noticed that the loud speaker doesn't kick in immediately
[11:39] <ogra> davmor2, known issue ... iirc rsalveti pointed it out in one of his mails
[11:39] <ogra> loudspeaker is delayed
[11:40] <davmor2> ogra: :) \o/ one less regression
[11:40] <ogra> well, it is a regression, fallout of the switch to 4.4 (audio stack behaves differently), but a known one
[11:41] <popey> davmor2: bug 1288692
[11:41] <ogra> and ricardo is working on i t
[11:41] <ogra> popey, should work, as long as you are patient
[11:41] <popey> no, it stays on
[11:42] <ogra> hmpf
[11:42] <popey> ooh, now I see two dialer apps
[11:43] <davmor2> popey: meh it does switch down for me eventually
[11:44] <ogra> popey, stop using dual SIM, the mako isnt built for that :P
[11:45] <popey> hah
[11:49] <bregma> sil2100, didrocks, apparently there was corruption in the Unity trunk branch on Launchpad, I ended up fixing it remotely then merging and retagging manually
[11:50] <Mirv> didrocks: pong
[11:50] <bregma> everything should be OK now, although the spreadsheet seemed a little confused for a while
[11:50] <sil2100_> bregma: let me doublt-check
[11:51] <Mirv> didrocks: I thought we agreed yesterday on signon-ui being locked, and I didn't know the rest would need updates either
[11:52] <didrocks> Mirv: seems like we can have a better way to get out of the current situation, would it be painful to just get those 5 branches out temporarly, relanding them and then adding them back?
[11:52] <didrocks> Mirv: but to be quick, we need to ensure that dbarth has the FFe first
[11:52] <t1mp> hello
[11:53] <t1mp> how can I trigger jenkins CI testing on https://code.launchpad.net/~andrew-hayzen/ubuntu-ui-toolkit/fix-swipe-delete-002/+merge/202171 ?
[11:53] <Mirv> didrocks: sure, juggling can be made if just keeping track of changes. indeed 1. remove branches, 2. land elsewhere, 3. add branches back (with updated trunks) and rebuild
[11:53] <didrocks> Mirv: just add a comment on the spreadsheet maybe?
[11:54] <Mirv> didrocks: then if stuff is landed to the archive that has higher version number than in the Qt 5.2 PPA, it might break testing the PPA
[11:54] <Mirv> before those are added back
[11:55] <Mirv> but otherwise fine. so: signon-ui ubuntu-system-settings-online-accounts webbrowser-app friends-app unity-webapps-qml <- I can remove+reconfigure from Qt 5.2 landing temporarily when needed
[11:55] <t1mp> didrocks: is there a way for me to trigger CI on an MR proposed by someone who is not canonical?
[11:56] <didrocks> t1mp: this is a question for the vanguard, not CI Train
[11:56] <didrocks> Mirv: thanks, and sorry for that :)
[11:57] <Mirv> didrocks: sorry, just to repeat, shall I do that now or shall we wait for the FFe? :)
[11:57] <didrocks> Mirv: let's wait for dbarth to answer us on the FFe one
[11:58] <davmor2> ogra: did you figure out the issue with adb on manta
[11:58] <Mirv> ok, thanks
[11:58] <Mirv> elopio: hi!
[11:58] <didrocks> thanks to you :)
[11:58] <sil2100_> Damn, LP stopped working for me here..
[11:58] <t1mp> didrocks: ok, I'll try that. You have been helpful to me before so I thought let's try that again :)
[11:58] <t1mp> psivaa: is there a way for me to trigger CI on an MR proposed by someone who is not canonical?
[11:58] <ogra> davmor2, still on it. its a bit tricky, the N10 usb gadget is pretty different
[11:58] <Mirv> elopio: could you launch another AP run, but with the following PPA:s: ppa:ci-train-ppa-service/landing-006 + ppa:canonical-qt5-edgers/qt5-beta1 (note the "1")?
[11:58] <davmor2> sil2100: you breaking the T'interwebz again
[11:58] <didrocks> t1mp: I have no idea on that part at all TBH ;)
[11:58] <davmor2> ogra: and older too I would imagine
[12:00] <sil2100_> ;/
[12:01] <psivaa> t1mp: I think it should be possible. is there an MP that I can take a look at?
[12:01] <t1mp> psivaa: yes, please https://code.launchpad.net/~andrew-hayzen/ubuntu-ui-toolkit/fix-swipe-delete-002/+merge/202171
[12:02] <t1mp> psivaa: that one is ready to go in, except that I need CI and the packages it creates for testing
[12:05]  * didrocks quietly deployed an update
[12:07] <psivaa> t1mp: i could retrigger that job if you'd like.
[12:08] <psivaa> t1mp: if that's what you want.. dont understandt he 'I need CI and the packages...' bit :)
[12:09] <ogra> sigh ... i'm not actually sure the adb change is at fault at all here
[12:09] <ogra> my N10 doesnt start after a fresh flash
[12:09] <ogra> grrr ... because it committed suicide again ... thanks battery
[12:12] <t1mp> psivaa: before approving the MR, I like to see that all CI tests pass
[12:12] <t1mp> psivaa: and when CI runs, UITK .deb packages are created, which I can use to do some manual testing
[12:13] <t1mp> psivaa: CI never ran for that MR, only autolanding tests once after I approved. But since then there have been some changes (and we don't have autolanding anymore)
[12:13] <t1mp> psivaa: so if you can trigger CI for that MP, please do so
[12:14] <t1mp> psivaa: so I need results similar to this https://code.launchpad.net/~mzanetti/ubuntu-ui-toolkit/drop-bottombarvisibilitycommunicator/+merge/209446/comments/492707 for the fix-swipe-delete-002 MP
[12:16] <psivaa> t1mp: ok, 1 sec please
[12:18] <popey> didrocks: davmor2 latest image broke background music playback
[12:19] <davmor2> popey: :(
[12:20] <didrocks> popey: did it start on latest image or you just see it on latest image?
[12:21] <popey> it broke on this image I believe. Happy to roll back though to test on other images
[12:22] <ogra> didrocks, you talked about a mail from plars wrt mako, where is that ?
[12:22] <ogra> (not on the ML)
[12:23] <ogra> (since i cant boot my N10 i would like to at least collect more info)
[12:23] <didrocks> ogra: it was manta (on another CI list)
[12:23] <didrocks> let me fw it to you
[12:23] <ogra> thanks
[12:24] <didrocks> popey: do you mind trying? I see no clear suspect in the diff
[12:24] <didrocks> maybe apparmor-easyprof-ubuntu…
[12:24] <didrocks> but let's confirm per image first
[12:24] <ogra> 222 had indicator-sound
[12:24] <psivaa> t1mp: i've triggered a job for that MP here  http://s-jenkins:8080/job/ubuntu-ui-toolkit-ci/1842/console
[12:25] <popey> didrocks: which image do you recommend I try?
[12:25] <ogra> sigh, now it doesnt even show the battery anymore when pressing power
[12:25] <seb128> ogra, indicator-sound has nothing to do with the background playing/service afaik
[12:25] <didrocks> popey: just the one before, I guess you would have discovered it before
[12:25] <t1mp> psivaa: thank you
[12:25] <psivaa> t1mp: there could be a reason why they were not automatically enabled.. but i dont know. let's see what this job does
[12:25] <didrocks> I don't think indicator-sound is linked to that
[12:26] <ogra> seb128, no, but its the one sound related package in the last two images :)
[12:26] <popey> didrocks: I don't test every image (especially the evening ones) but sure, I'll go back one by one
[12:26] <didrocks> popey: yeah, I bet you would have caught it by yesterday, thanks!
[12:26] <didrocks> and we don't have that much changes
[12:26] <popey> k
[12:26] <seb128> popey, it might be easier to go a few back and do selective upgrading?
[12:27] <didrocks> ogra: fwed
[12:27] <seb128> I can imagine small updates being easier than having to download a full image every time
[12:27] <elopio> Mirv: http://q-jenkins.ubuntu-ci:8080/job/autopilot-release-gatekeeper/60/
[12:27] <elopio> it's running.
[12:27] <seb128> or can the system image "downgrade" by delta?
[12:27] <popey> seb128: I'm easy, I have fast internet
[12:27] <didrocks> seb128: that's what we do actually, try first to find the image and then apt-get install once we found the image which broke
[12:28] <didrocks> seb128: he doesn't live in north of France, they do know how to do Internet there as well :p
[12:28] <seb128> didrocks, well, if I had to download 5 full images and put them on the device it would take me half a day
[12:28] <Mirv> elopio: \o/
[12:28] <didrocks> seb128: < 1 min here I would say :p
[12:28] <seb128> didrocks, where downloading n-5 and doing small dist-upgrade takes an hour
[12:28] <seb128> lol
[12:28] <didrocks> longest is to flash the device
[12:28] <seb128> right, 5 times doing that is much longer than 1
[12:29] <seb128> but everyone has his own debug tricks I guess ;-)
[12:29] <didrocks> yeah ;)
[12:29] <didrocks> Mr "I don't dist-upgade"
[12:29] <didrocks> :p
[12:29]  * seb128 wins back the slow download by being smart :p
[12:29]  * didrocks pets his 1Gb connection
[12:30] <ogra> well, dist-upgrade is broken by design in our images
[12:30] <didrocks> ogra: stop thinking only about Touch! :)
[12:30] <ogra> didrocks, i'll start thinking about desktop again once we have the redonly images there (next release)
[12:31] <didrocks> I like how optimistic you are :)
[12:32] <Laney> yeah, seriously
[12:32]  * ogra isnt joking
[12:32] <didrocks> RE: I like how optimistic you are :)
[12:32] <didrocks> :)
[12:32] <ogra> :)
[12:33] <seb128> ogra, dist-upgrade is not supported on touch, yet it works fine most of time and is a valuable efforts saver
[12:33] <seb128> ogra, you tell me how you test silo's landing without apt-get btw ;-)
[12:35] <ogra> seb128, by having a bunch of dedicated buildds that give you images with the silo included
[12:35] <Mirv> I wonder why I'm getting "prepare-silo: error: unrecognized arguments: trusty"
[12:35] <ogra> (its on the TODO of foundations)
[12:36] <seb128> ogra, well, I mean today, how do I test my silos without using apt which is not supported?
[12:36] <ogra> seb128, apt-get install is
[12:36] <ogra> dist-upgrade isnt
[12:36] <seb128> same difference
[12:36] <seb128> they both do similar things
[12:36] <seb128> having a silo ppa and dist-upgrade or installing <list of binaries> does the same
[12:37] <ogra> well, asl long as dpkg gets along all is fine with that ...
[12:37] <Mirv> elopio: also the gatekeeper job seems failed
[12:37] <seb128> right
[12:37] <ogra> but there are enough packages where it simply doesnt
[12:37]  * Mirv tries to read backlog on possible discussion on CI breakage
[12:37] <didrocks> Mirv: oh, that maybe me :) do you have a link?
[12:37] <didrocks> Mirv: no for CI, but for prepare-silo
[12:37] <Mirv> didrocks: http://162.213.34.102/job/prepare-silo/393/console
[12:38] <didrocks> see my 13:05:51        * | didrocks quietly deployed an update
[12:38] <Mirv> elopio: it just says failure http://q-jenkins.ubuntu-ci:8080/job/autopilot-release-gatekeeper/60/console
[12:38] <Mirv> didrocks: very quietly :)
[12:38] <elopio> Mirv: yesterday it failed too. psivaa, can you give me a hand?
[12:38] <didrocks> Mirv: I need to show people I'm working :)
[12:38] <elopio> Mirv, psivaa: ERROR:phablet-flash:Device either not connected
[12:38] <Mirv> haha
[12:38] <didrocks> Mirv: oh, I did redeploy every job but the prepare one
[12:38] <didrocks> I bet that's it :)
[12:39] <didrocks> Mirv: retry?
[12:39] <psivaa> elopio: one sec please
[12:40] <Mirv> didrocks: looks good now, great!
[12:41] <didrocks> Mirv: sweet ;)
[12:41] <davmor2> popey: music is working for me in the music app once the screen has blanked
[12:41] <popey> davmor2: which image?
[12:41] <didrocks> Mirv: sorry, got all code changed, but didn't redeploy the prepare-silo one
[12:41] <davmor2> popey: current but let me double check
[12:41] <popey> #222 works here
[12:42] <davmor2> version version: 223
[12:43] <ogra> popey, check for apparmor log messages
[12:43] <ogra> (since that changed in 223)
[12:43] <popey> ok, will update and try again
[12:46] <psivaa> elopio: mako-07 is not coming up in adb devices.. would need someone to go down there to take a look
[12:46] <jdstrand> note, the apparmor-easyprof-ubuntu changes only added more access for desktop systems
[12:46] <elopio> psivaa: thanks. please let me know when I can re-run the job.
[12:48] <davmor2> popey: get ready for a quick hang out request
[12:48] <sil2100> Mirv: ping
[12:48] <popey> davmor2: ok
[12:48] <Mirv> sil2100: pong
[12:49] <davmor2> https://plus.google.com/hangouts/_/7acpjlh4jf0b067q7lmc1slud0?hl=en-GB
[12:49] <davmor2> popey: ^
[12:50] <popey> bah, music works on #223 now
[12:50] <popey> ffs
[12:50] <didrocks> popey: again a popey's bug!
[12:50] <didrocks> :)
[12:54] <popey> didrocks: figured it out
[12:54] <popey> didrocks: I had sf on, mir off, and that's when the music fails to play on screen blank
[12:56] <ogra> which is expected
[12:57] <didrocks> why did you get sf on?
[12:57] <didrocks> (like, any trick which failed?)
[12:58] <Mirv> sil2100: can you enlighten me about the possibility of bfiller's landing line 6 of going in before tomorrow?
[12:58] <popey> i had to enable sf to test stuff for kaleo, forgot to re-create .display-mir
[12:58] <sil2100> didrocks: eek, sorry to AGAIN ask the same question - but if we want to ignore a version that's been directly uploaded to the archive (we don't want it in te changelog) then what flag I should use? ;p
[12:58] <Mirv> so that I could start tomorrow by grabbing content-hub, gallery-app, camera-app, unity-scope-click into Qt 5.2 landing
[12:58]  * sil2100 thinks it's the 3rd time he asks that
[12:58] <sil2100> duuuh
[12:59] <davmor2> sil2100: you need to setup your own FAQ wiki page :D
[13:00] <sil2100> davmor2: a wiki-page for people with altzheimer? ;D
[13:00] <davmor2> sil2100: you have to remember the link though :D
[13:05] <sil2100> brb, location change
[13:11] <didrocks> sil2100: you mean, for building?
[13:17] <dbarth> didrocks, Mirv: stuck in a meeting  but i will do the FFE  before landing of course; just testing and verifying that the fix really works first
[13:17] <dbarth> hope you're not blocked; tell me if you do
[13:17] <didrocks> dbarth: we kind of are, as you dont' have the FFe done and acked, Mirv is trying to land qt 5.2 at the same time, so we need to ensure you can land before EOD
[13:18] <didrocks> dbarth: and for that, you need the FFe acked, so we can't give you a silo before being sure you will be able to land
[13:18] <dbarth> but if i don't land, you're stuck as well?
[13:18] <dbarth> ie, can you land qt5.2 (which is a priority) without us?
[13:19] <ogra> dbarth, well, can you wait for another week with yours ? 5.2 will likely cause us to stay in degraded landing mode for another week
[13:20] <ogra> i assume thats the reason why dider is pushing
[13:20] <Mirv> dbarth: yes so those packages you're targetting are already rebuilt in the Qt 5.2 landing silo. so they'd land as they are currently, just rebuilt.
[13:20] <dbarth> i'm ok to wait; asking oSoMon as well, since we're blocking him as well
[13:20] <dbarth> so?
[13:20] <dbarth> am i blocking you guys or not?
[13:20] <Mirv> dbarth: but if needed to land, we can temporarily remove those 5 packages from Qt 5.2 landing to do a landing in-between
[13:21] <Mirv> dbarth: well, you would be blocking if you plan to land tomorrow, but if you can finish all the way to merge + clean today then it doesn't block
[13:26] <didrocks> dbarth: ideally, I would prefer you to land first, be aware that landing Qt 5.2 can take still some days
[13:26] <didrocks> dbarth: and it will mean that Mirv is going to land the reverts to trunks
[13:26] <didrocks> Mirv: your branches contains the reverts, right?
[13:27] <didrocks> dbarth: so more work for you to rebase on that afterwards
[13:27] <didrocks> and osomon
[13:29] <Mirv> dbarth: the one revert, signon-ui, at the moment
[13:29] <didrocks> Mirv: you don't revert the other oens?
[13:29] <didrocks> ones*
[13:30] <didrocks> Mirv: you should, we don't want to reland half of the packages change
[13:30] <Mirv> didrocks: I fail to remember now which needed what reverts, but yes it's possible I need to rebuild 1-2 other packages now
[13:30] <Mirv> webbrowser-app
[13:30] <Mirv> friends-app
[13:31] <Mirv> and online accounts. check. I need to update those branches to be reverts instead of rebuilds
[13:31] <didrocks> Mirv: signon-ui and g-c-c-online-accounts
[13:31] <didrocks> in addition to webbrowser-app and friends-app
[13:31] <Mirv> yes, the online accounts
[13:33] <Mirv> ok, handling that now
[13:33] <didrocks> Mirv: maybe wait an hour if dbarth has good news from the release tam?
[13:33] <didrocks> team*
[13:34] <Mirv> didrocks: well it doesn't hurt if I rebuild better packages meanwhile. it shouldn't take too long
[13:34] <didrocks> ;)
[13:34] <didrocks> ok then
[13:38] <dbarth> didrocks: https://bugs.launchpad.net/webbrowser-app/+bug/1288743
[13:38] <dbarth> can i subscribe the release team with that?
[13:38] <didrocks> dbarth: looks good, please poke them as well :)
[13:38] <dbarth> well, done anyway, let's see
[13:39] <didrocks> dbarth: slangasek, Laney will be able to help ^
[13:39] <dbarth> ah, thanks for the nudge
[13:42] <didrocks> sil2100: (once you are back), please do assign both silo with Mirv's help once this FFe is acked by the release team ^ (I'll probably be exercising by then)
[13:49] <didrocks> sergiusens: hey, did you get a query from balloons to release sil2100's terminal-app branch?
[13:49] <didrocks> (to fix some AP tests)
[13:49] <sergiusens> didrocks, nope; but I was out until today; so I'd expect that
[13:49] <didrocks> renato_: any news on the eds for clock app fixes?
[13:50] <sergiusens> didrocks, I would think balloons is capable of doing it though
[13:50] <didrocks> sergiusens: ok, weird, it was planned yesterday but didn't, not sure why :) I'll check with him I guess
[13:50] <didrocks> sergiusens: welcome back! :)
[13:50] <renato_> didrocks, this is a bug on the SDK,  zsombi is working on that
[13:50] <sergiusens> didrocks, I can do it now if already merged
[13:51] <didrocks> renato_: do you have any idea of a release time? It's part of the image promotion blocker list
[13:51] <didrocks> sergiusens: I guess it is…
[13:51] <sergiusens> seems merged http://bazaar.launchpad.net/~ubuntu-terminal-dev/ubuntu-terminal-app/trunk/revision/41
[13:51] <didrocks> yeah ;)
[13:51] <didrocks> sergiusens: that would be fantastic! :)
[13:51] <renato_> looks like all releases on SDK is pending, I asked him yesterday and he did not give me any specific date
[13:51] <didrocks> renato_: waow, bzoltan any more infos?
[13:52] <bzoltan> didrocks: no, I have no info
[13:53] <renato_> didrocks, you can ask szombi on #ubuntu-app-devel
[13:54] <didrocks> rather than chasing one by one, can you guys help me? :)
[13:55] <didrocks> bzoltan: ^
[13:55] <didrocks> I don't want a full sdk release, just the one to make clock apps working again
[13:56] <renato_> didrocks, you are talking about the alarm on Sunday, correct?
[13:56] <didrocks> yep
[13:56] <didrocks> which is the latest blocker for clock apps
[13:56] <didrocks> right?
[13:56] <bzoltan> didrocks: zsombi is attending to the Qt52 standup right now and Kaleo and him are fixing the DPR and Datepicker bugs ...
[13:56] <didrocks> bzoltan: ok, can you catch with him again and tell me?
[13:57] <bzoltan> didrocks: I am positive that nobody from my team has looked it today
[13:57] <didrocks> bzoltan: so, I guess we won't have an image to promote before 5.2 then?
[13:57] <renato_> didrocks, szombi is working on alarm API since last week but he is blocked due this Datepicker bug on qt 52
[13:58] <sil2100> didrocks: sure!
[13:58] <didrocks> sil2100: ah, finally back!
[13:58] <bzoltan> didrocks: I do not know
[13:58] <sil2100> Finally INTERNETZ
[13:58] <didrocks> sil2100: I had to chase myself everyone to get infos meanwhile :/
[14:00] <sil2100> I'm at my girlfriends grandparents now, I think our ISP tries fixing our internet connection by disconnecting it
[14:00] <sil2100> sergiusens: so, terminal-app is pushed forward, yes?
[14:01] <davmor2> sil2100: Noooooooo we can't let you near the Interwebz youz breakzez it
[14:01] <sergiusens> sil2100, I'm pre testing and then pushing; consider it done in 10'
[14:01] <sil2100> didrocks: will keep an eye on those FFe's from the spreadsheet
[14:01] <sil2100> sergiusens: awesome news, thanks!
[14:05] <didrocks> sil2100: so, clock-apps has been discussed, remaining on the list is weather app AFAIK
[14:11] <cjwatson> didrocks: I'd like to try to land libclick before 5.2 if possible, currently waiting for our lander (stgraber) to wake up - do you think that might still be possible?
[14:12] <sil2100> grrr
[14:12] <cjwatson> or am I screwed?
[14:13] <didrocks> cjwatson: no, should be fine. Can you just get tested the existing impacted AP tests?
[14:13] <sil2100> cjwatson: how complicated is the landing?
[14:13] <cjwatson> sil2100: single package
[14:13] <cjwatson> it's just in click itself, in terms of source packages
[14:14] <sil2100> cjwatson: as didrocks said, fill it in and let's try landing
[14:14] <cjwatson> yep, waiting for Stéphane
[14:14] <sil2100> cjwatson: just make sure your lander tests it well!
[14:14] <cjwatson> well, I was going to test it I think
[14:14] <seb128> cjwatson, you can get any lander add the line for you
[14:14] <cjwatson> it's https://code.launchpad.net/~click-hackers/click/trunk/+merge/209698, ignoring the blatant lies there about the bugs fixed
[14:14] <seb128> cjwatson, I'm happy to put the line in there if you want, so we can start build, etc
[14:15] <Mirv> sil2100: hi, did you have any info on the line 6 landing, should it be simply put in today or how?
[14:15] <sil2100> Mirv: let me refresh my memory
[14:16] <seb128> cjwatson, should I add it or do you prefer to wait for stgraber?
[14:16] <sergiusens> popey, can you take a look? https://myapps.developer.ubuntu.com/dev/click-apps/157/
[14:17] <Mirv> sil2100: you saw the e-mail from bill probably regarding it?
[14:17] <popey> sergiusens: ack
[14:17] <cjwatson> seb128: please go ahead if you can, thanks
[14:17] <sil2100> Mirv: hmm, let me refresh my mailbox
[14:17] <rsalveti> ogra: popey: I'll check bug 1288692, but I know it was working with 219/220
[14:17] <rsalveti> the delay was expected as well
[14:18] <Mirv> sil2100: then there's Saviq's response there. is it that in order to land it unity8 should also be landed. is that then too before Qt 5.2 or after..
[14:18] <popey> rsalveti: I would prioritise that lower, I can't reproduce it now
[14:18] <Saviq> Mirv, we landed it in unity8 already
[14:18] <rsalveti> popey: alright
[14:18] <Saviq> Mirv, if that's about the 5.2 fixes...
[14:19] <seb128> didrocks, sil2100, cjwatson: click landing add to l36, if somebody wants to assign it a silo ;-)
[14:19] <Mirv> Saviq: no the ones needed for bill's landing https://code.launchpad.net/~mzanetti/unity8/disable-hud/+merge/209226 + https://code.launchpad.net/~mzanetti/ubuntu-ui-toolkit/drop-bottombarvisibilitycommunicator/+merge/209446
[14:19] <cjwatson> afterwards I'll be able to work on upstart-app-launch and such, but this gets us started
[14:20] <Saviq> Mirv, yeah, we won't land those yet
[14:21] <Saviq> Mirv, we just extracted just the tests disabling
[14:21] <Mirv> Saviq: sil2100: bfiller_afk: that will probably mean no landing of line 6 before Qt 5.2, so unfortunately the silo should be removed?
[14:22] <Mirv> it was just that Bill wanted the gallery/camera click conversion in for weeks, but does it seem now there is simply no way of doing that since unity8 + UITK are not going to get in yet?
[14:25] <sil2100> Mirv: what e-mail was that?
[14:25] <sil2100> Mirv: could you give me the titles?
[14:25] <Saviq> Mirv, uitk is blocked by 5.2, right? but we just made it so that the uitk change is not necessary straight away
[14:25] <sil2100> seb128: will assign ;)
[14:26] <Saviq> and unity8 is not yet blocked by 5.2 is it?
[14:26] <seb128> sil2100, thanks
[14:26] <popey> sergiusens: running terminal AP tests on device ...
[14:26] <Mirv> sil2100: the thread "Landing content-hub + 4 others + Mir before or after Qt 5.2?"
[14:27] <Mirv> Saviq: well everything's blocked unless we start juggling things and temporarily remove something from Qt 5.2 landing in order to land something critical elsewhere. like dbarth/sil2100 may be doing for signon-ui/online-accounts/etc
[14:28] <Mirv> Saviq: unity8 is not blocked currently in CI Train only because Mir landing is blocking unity-mir and it's a requirement for unity8
[14:29] <sergiusens> popey, sounds good; I got 100% on flo
[14:30] <popey> ok, I'm testing on mako
[14:30] <popey> #223
[14:31] <Saviq> Mirv, so yeah, row 6 looks like it could land?
[14:31] <sil2100> Re-reeading it
[14:32] <sil2100> I would say - let's land it
[14:32] <didrocks> sil2100: ensure the CI team is ready to switch on the dashboard
[14:32] <davmor2> popey: can I haz a go in your time machine please :)
[14:32] <seb128> cjwatson, https://launchpad.net/~ci-train-ppa-service/+archive/landing-004/ , the package is building
[14:33] <Saviq> Mirv, so line 6 is content-hub, camera-app, gallery-app, unity8, are any of those blocked in CIT?
[14:33] <didrocks> Saviq: as they are click apps, I think they need to update something as we discussed
[14:33] <sil2100> didrocks: ok, we'll poke plars and ev with that
[14:33] <sil2100> Mirv, sergiusens: so, should we try landing line 6?
[14:33] <cjwatson> seb128: thanks
[14:33] <seb128> yw!
[14:33] <sil2100> sergiusens: are you ready for the transition as well?
[14:33] <plars> sil2100: hi, what do you need updated?
[14:34] <seb128> cjwatson, arg, failed to build
[14:34] <seb128> cjwatson, https://launchpadlibrarian.net/168521477/buildlog_ubuntu-trusty-amd64.click_0.4.17_FAILEDTOBUILD.txt.gz
[14:34] <cjwatson> yeah, damnit
[14:34] <cjwatson> sorry, I'll fix it up
[14:34] <cjwatson> tested everything but the final assembly :-/
[14:34] <seb128> cjwatson, well, good news is that I can trigger a rebuild from your current branch, so just ping me when you get a fix in there
[14:35] <cjwatson> seb128: I'll need to bump the version though, right
[14:35] <sil2100> plars: once we land the transition of gallery and camera apps to click apps we need the dashboard updated to use click apps instead of the normal ones
[14:35] <cjwatson> because this is X-Auto-Uploader: no-rewrite-version
[14:35] <dbarth> Laney: ping?
[14:35] <Mirv> Saviq: sergiusens: sil2100: so those are blocked from Qt 5.2 point of view in CI Train because of the line 6 was there first. and my interest is getting line 6 sorted out so that I ould get the named packages and their dependencies into Qt 5.2 silo :)
[14:35] <dbarth> trying to see if the FFE makes sense and unblock things
[14:35] <sil2100> Mirv: let's try releasing that today so you ave it unblocked tomorrow
[14:36] <sil2100> ;)
[14:36] <Mirv> sil2100: +1 on that :)
[14:36] <plars> sil2100: it's an easy change for us, when do you expect that to change in image?
[14:36] <sergiusens> Mirv, if line 6 is gallery/camera; that's happening today
[14:36] <sil2100> plars: in the best case, I guess the next auto-image from cron shoud have it?
[14:37] <sil2100> sergiusens: ouuu yeaaaa
[14:38] <plars> sil2100: ok, let's confirm with didrocks. We can discuss in the landing call and I'll make sure the change goes in if so
[14:38] <didrocks> I just need an ETA of that landing, sergiusens, is everything's ready and we can publish?
[14:38] <sergiusens> didrocks, remember that this is complex ;-)
[14:39] <sil2100> plars: today is Thursday so I won't be around for the meeting sadly
[14:39] <sil2100> sergiusens: are you ready with everything on your side?
[14:39] <didrocks> sergiusens: right, that's why I'm anxious, we already can't promote an image and we are going to get confinement on some apps due to change to clicks :p
[14:39] <didrocks> sergiusens: so, hoping that there will be no unseen side-effects :p
[14:39] <sergiusens> didrocks, I would need to reconf the silo with unity8
[14:39] <didrocks> ok, so not really there yet
[14:39] <didrocks> remember as well that Mir is going to need a metapackage rebuild
[14:40] <sergiusens> didrocks, Mir?
[14:40] <didrocks> sergiusens: yeah, new packages, per platform, don't worry :)
[14:40] <sergiusens> didrocks, I do know that I need to fix the seeds if they are outdated (ubuntu-touch)
[14:41] <Laney> hello dbarth, I don't see it on the list
[14:41] <didrocks> sergiusens: yeah, ubuntu-touch is in and still valid in your silos for the next couple of hours
[14:41] <sergiusens> didrocks, I plan to start this after our team's standup
[14:41] <didrocks> it's in an hour and half?
[14:42] <sergiusens> didrocks, can't do it now since I have to present at the app dev days (going to wing it since it was asked while I was on holidays)
[14:42] <sergiusens> didrocks, yes
[14:42] <didrocks> hum, that will be tight
[14:42] <sergiusens> utc 16:30
[14:42] <didrocks> with the Mir landing
[14:42] <didrocks> and I don't want both in the same image
[14:43] <didrocks> (in case some tests are failing, it will be harder to decipher if it's Mir or the click conversion)
[14:43] <didrocks> sergiusens: so, just coordinate to kgunn to have an image kicked and tested in between please
[14:44] <sergiusens> didrocks, deciphering errors due to a package being click is easy
[14:44] <sergiusens> but I'll coordinate
[14:44] <didrocks> thx!
[14:45] <sergiusens> didrocks, is the meta going to be outdated after mir lands?
[14:45] <didrocks> sergiusens: yeah
[14:45] <popey> sergiusens: approved terminal
[14:45] <didrocks> it will force us to remove the change
[14:45] <didrocks> popey: \o/
[14:45] <Saviq> sergiusens, didrocks, I'm just running the u8 test suite with the unity8 branches, will ACK the branches in 5 or so
[14:46] <sergiusens> Saviq, are you adding the landing as well once that's done so we can reconf the silo?
[14:46] <Saviq> sergiusens, they're already there
[14:46] <Saviq> sergiusens, you can reconf now
[14:46] <sergiusens> oh, great
[14:47] <Saviq> sergiusens, I dropped the two click scope MPs
[14:47] <Saviq> sergiusens, as they were merged separately
[14:47] <sil2100> Saviq: which silo you mean?
[14:47] <sil2100> popey: \o/
[14:47] <Saviq> sil2100, 007, but I think sergiusens is on it?
[14:48] <balloons> ty popey for approving ;-)
[14:48] <dbarth> Laney: let me share the link
[14:48] <didrocks> sil2100: take care, it's ubuntu-touch-meta, not ubuntu-touch
[14:48] <didrocks> sil2100: for the source package
[14:49] <dbarth> Laney: https://bugs.launchpad.net/webbrowser-app/+bug/1288743
[14:49] <sergiusens> didrocks, sil2100 ^silo 7
[14:49] <popey> balloons: yw
[14:49] <sil2100> didrocks: oh, ok
[14:49] <sil2100> Right
[14:50] <didrocks> sil2100: letting you doing it?
[14:50] <Laney> dbarth: ok, I made it affect the package in Ubuntu
[14:50] <Laney> someone should get to it soon
[14:52] <dbarth> Laney: thanks for that, i forgot it was on the ubuntu package i needed it
[14:52] <sil2100> didrocks: you mean, with the ubuntu-touch change for camera and gallery app, right?
[14:52] <tvoss> didrocks, sil2100 can I get a silo for line 35?
[14:52] <Laney> I think it would have gotten to people via email anyway, but this makes it appear on the list that some of us use
[14:53] <davmor2> popey: can you open the notes app?
[14:53] <sil2100> tvoss: sadly, unity-mir is locked by the Mir landing right now
[14:53] <tvoss> sil2100, okay
[14:53] <sil2100> tvoss: we'll assign as soon as the landing is done, which shoud be soon
[14:53] <didrocks> sil2100: yeah, the source is called ubuntu-touch-meta
[14:54] <tvoss> sil2100, thx
[14:54] <sil2100> yea, doing
[14:54]  * didrocks fixes that in the spreadsheet
[14:55] <popey> davmor2: I would.. but http://imgur.com/yfKWZf0  HEY LOOK MY N KEY MOVED!
[14:56] <popey> davmor2: yes, i can open notes app
[14:57] <sil2100> didrocks, sergiusens: reconfigured the silo
[14:58] <davmor2> popey: yeah I got that from time to time if you click on where the n should be it still types it :)
[14:58] <davmor2> popey: I could never successfully reproduce it
[14:58] <davmor2> popey: I can't remember if I posted a bug for it
[14:59] <popey> davmor2: I just had a problem where press search in dash, keyboard comes up, press a key, the keypress goes through the keyboard and hits the app underneath it, launching it
[15:00] <popey> rebooted to get around it ☹
[15:00] <davmor2> popey: man that is an old bug that they fixed
[15:00] <popey> nope ☻
[15:00] <davmor2> popey: I think you need to fresh flash your phone to be honest :D
[15:00] <popey> shush
[15:01] <davmor2> popey: Ubuntu Netwalk, doesn't save highscores
[15:01] <popey> gah, typing through keyboard again
[15:02] <Mirv> sergiusens: sil2100: oh yeah!
[15:02] <Mirv> like sil2100 said
[15:02] <davmor2> popey: I can't reproduce that on mako, flo or manta
[15:03] <popey> davmor2: it's intermittent
[15:03] <Mirv> sil2100: are you ok to handle the d_barth FFe landing if it happens? ie you know to temporarily put aside the certain branches from Qt 5.2 landing, reconfigure it but leave it otherwise intact?
[15:04] <Mirv> sil2100: actually, if it'll need reconfiguring, you'll need a list of the manual packages. I can give you that
[15:04] <Mirv> sil2100: http://pastebin.ubuntu.com/7044512/
[15:04] <sil2100> Mirv: ok, will do that if that happens today during the evening - could you e-mail me the list so it doesn't get lost?
[15:04] <didrocks> Mirv: the spreadsheet has a field for it :)
[15:04] <didrocks> Mirv: please update it
[15:04] <Mirv> didrocks: !
[15:04] <Mirv> :)
[15:04] <Mirv> "there's a field for that"
[15:05] <didrocks> "Additional source packages to land" :p
[15:05] <Mirv> sil2100: updated
[15:05] <sil2100> didrocks: hmmm... me and sergiusens are a bit confused abour the ubuntu-touch change - the ubuntu-touch-meta branch has the gallery-app and camera-app removal already in the trunk, but it wasn't released yet, right? ;p
[15:06]  * sil2100 gets confused because of the new idea trunk = distro
[15:06] <sil2100> ;)
[15:06] <didrocks> sil2100: doesn't work for meta packages
[15:06] <sil2100> So, we should prepare a source package of that and simply attach that, ok
[15:07] <sil2100> All is clear for uss
[15:07] <sil2100> Mirv: thanks ;p
[15:07] <Mirv> I think seed update instead https://code.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/ubuntu-touch.trusty
[15:07] <sil2100> Yeah, this one is up-to-date with the removal from seeds
[15:07] <didrocks> sil2100: but you do have the source package prepared
[15:07] <didrocks> sil2100: it's the -meta
[15:08] <sil2100> I know I know
[15:08] <sil2100> I know now ;)
[15:08] <didrocks> yeah ;)
[15:08] <didrocks> and yeah, the airline as a plan so that you just give your branch
[15:08] <didrocks> and the seed update is done
[15:10]  * didrocks goes for a run
[15:11] <Mirv> ok, I got rest and hopefully get cured, I've had some flu symptoms it's mostly quite tiring
[15:11] <Mirv> s/got/go7
[15:11] <popey> fix your keyboard too maybe? ☻
[15:13]  * didrocks is going to listen to popey while running :p
[15:13] <popey> haha, i wasnt in it much
[15:13] <popey> got a UT mention in tho ☻
[15:13] <didrocks> popey: roh, sooo disappointed! :)
[15:13] <didrocks> heh
[15:13] <popey> i shouldn't go on that show when I have been drinking :D
[15:16] <cjwatson> HULK SMASH CTYPES
[15:16] <cjwatson> ahem
[15:23] <psivaa> t1mp: http://s-jenkins.ubuntu-ci:8080/job/ubuntu-ui-toolkit-ci/1842/console has finished success.. so i guess you'd have the required bits in there
[15:24] <t1mp> psivaa: thanks
[15:24] <t1mp> psivaa: the s-jenkins url doesn't work for me, but I already saw the results in the MR :) I'm already running tests with the debs
[15:24] <t1mp> :)
[15:25] <davmor2> cjohnston: stop, stop now.  The ctype evolves into an etype and man etypes are gorgeous assuming of course that they follow jaguar whole heartedly with their naming of types ;)
[15:25] <psivaa> t1mp: ack, there should be a public jenkins link for that job. but i'll skip that if you've already got what you needed :)
[15:25] <davmor2> cjwatson: ^ even
[15:26] <cjwatson> davmor2: trust me, the Python ctypes module has nothing to do with Jaguar quality
[15:26] <t1mp> psivaa: I got the links from here https://code.launchpad.net/~andrew-hayzen/ubuntu-ui-toolkit/fix-swipe-delete-002/+merge/202171/comments/493255
[15:27] <cjwatson> seb128: Right, sorry about that, that was way more painful than it should have been.  Could you retrigger silo 004 please?
[15:28] <cjwatson> versioned as 0.4.17.1
[15:29] <seb128> cjwatson, done
[15:29] <om26er> plars, ping
[15:29] <plars> om26er: hi
[15:30] <cjwatson> seb128: thanks
[15:30] <om26er> plars, in the unlock_screen script the blind unlock code path is useless, if the screen does not unlock with assertion there is no way blind swipe will, do you have any objection if I remove that part ?
[15:32] <plars> om26er: hmm, I'm a big fan of the the saying "if it ain't broke, don't fix it", but if you're really sure and you've tested the change well, we can give it a try.
[15:33] <om26er> plars, sure, from my testing if the screen failed to unlock due to some reason (it does not these days, unless unity does not start) the blind swipe didn't help either
[15:41] <seb128> cjwatson, build is happier this time ;-)
[15:42] <cjwatson> Yep
[15:43] <tvoss> sil2100, do you keep me posted on the unity-mir lock status?
[15:52] <sil2100> tvoss: will do, sure!
[15:52] <tvoss> sil2100, thanks
[15:53] <cjwatson> didrocks: http://162.213.34.102/job/landing-004-1-build/48/console seems to suggest that something needs to be changed there to check the ppc64el status too?
[15:53] <cjwatson> "arch: {i386,powerpc,amd64,armhf}, status: building"
[15:54] <sil2100> hm, got informed that my network issues have been fixed, but I think I'm still having packet loss here ;/
[15:55] <sil2100> Oh well
[15:55] <Laney> sil2100: is the touch metapackage blocked by landing-007?
[15:56] <sil2100> Laney: it might be, why you ask?
[15:56] <Laney> because I would like to upload it
[15:56] <Laney> that's a strangely opaque response
[15:56] <davmor2> Laney: How could James Bond ever stop the touch metapackage
[15:57]  * Laney shakes davmor2 
[15:57] <sil2100> Laney: hm, we're still not releasing the click landing, I mean not like 'now' - you want to push it through CITrain?
[15:57] <sil2100> Laney: or a direct upload to the archive?
[15:58] <Laney> I would just upload it
[15:58] <Laney> but I don't want to release all these random changes
[15:58] <cjwatson> sorry when you say click landing do you mean mine in silo 004, or the conversion of some apps to clicks?
[15:59] <Laney> the second thing
[15:59] <Laney> It's taken a lock on the metapackage
[15:59] <sil2100> Laney: hmm, so, I would say - you can release new ubuntu-touch-meta, just please backport the change you want to release to the bzr branch
[16:00] <cjwatson> thought so, I think when both are in flight it would help to be clear :)
[16:00] <sil2100> Laney: so that when we release it for silo 007 we have all your changes in as well ;p
[16:00] <sil2100> Laney: since sergiusens is busy right now and I'll have to jump out for practice in the nearest time and be back later
[16:00] <sil2100> So no need to over-complicate things
[16:01] <sil2100> I mean, block things
[16:01] <cjwatson> didrocks: though it did say "arch: ppc64el, status: published" eventually
[16:05] <sil2100> Laney: ~.
[16:05] <Laney> sil2100: The changes in the silo are already in trunk
[16:05] <Laney> nope, you didn't lose your connection
[16:05] <sil2100> grrr
[16:05] <sil2100> ;)
[16:05] <Laney> So I can't upload it without reverting those
[16:05] <sil2100> Laney: yes, I know, but the stuff you want to release is not, right?
[16:05] <Laney> yes it is
[16:05] <sil2100> Laney: ah
[16:06] <sil2100> Laney: then release only what you want and backport the changelog entry to the bzr repo
[16:06] <Laney> The metapackage works by checking out trunk of the seed branch and working out what to add
[16:06] <sil2100> ah
[16:06]  * sil2100 knows less about that
[16:06] <Laney> It doesn't play too well with having things committed but not ready to go
[16:06] <sil2100> brrr
[16:07] <sil2100> ogra: are there any plans on kicking an image right now?
[16:07] <sil2100> Laney: how urgent is your ubuntu-touch release?
[16:07] <Laney> not hugely
[16:08] <ogra> sil2100, not on my side ... i would actually like to upload the fix for adb for manta before
[16:08] <sil2100> Laney: could it wait till evening, like ~3h from now on?
[16:08] <cjwatson> $ click pkgdir com.ubuntu.weather
[16:08] <cjwatson> GObject.__init__() takes exactly 0 arguments (1 given)
[16:08] <cjwatson> bugger
[16:08] <Laney> It can certainly wait
[16:08] <Laney> I mainly want to observe that this is undesirable
[16:08] <Laney> Doing the seed out-of-band would likely be better
[16:08] <ogra> the seed was only uploaded there for testing
[16:08] <ogra> we can indeed upload it separately
[16:09] <sil2100> ogra: the camera/gallery change you mean?
[16:09] <ogra> yes
[16:09] <sil2100> Ok, so if someone can do a revert of that one and then prepare for re-adding it later today, than I +1 for that as well
[16:09] <ogra> revert ? just delete the package from the ppa before landing
[16:10] <Laney> yeah
[16:10] <Laney> But the changes there are already in the seed branch and not ready to go
[16:10] <sil2100> Ok, I'm confused, didn't you guys say that the seed change is in the branch?
[16:10] <ogra> oh, ok
[16:10] <ogra> yeah, branch != meta
[16:10] <sil2100> So someone needs to remove that from the bzr branch first then
[16:11] <ogra> well, yes
[16:11] <ogra> not "first" though
[16:11] <ogra> just needs to be removed
[16:11] <Laney> How long are we talking before this stuff is uploaded?
[16:12] <sil2100> The transition you mean?
[16:12] <Laney> yeah
[16:12] <ogra> do you mean the meta change ?
[16:12] <ogra> heh
[16:12] <Laney> we don't have to mess about with reverting if it's like quite soon
[16:12] <Laney> can just wait
[16:12] <Laney> it two weeks... well...
[16:12] <ogra> right
[16:12] <Laney> s/it/if/
[16:12] <sil2100> We want to land it today I guess
[16:13] <ogra> no issue then
[16:13] <ogra> tell me when it lands and i'll prepare a meta
[16:13] <Laney> For future you can hack update.cfg to build from a local seed branch, and use a PPA version
[16:13] <ogra> until someone accidentially cpoies it into the archive :P
[16:14] <Laney> mmm, you'd want support in the train to not do that
[16:14] <ogra> i'm not sure there is
[16:14] <Laney> probably not
[16:14] <ogra> which is why i uploaded an acceptable package back then
[16:15] <ogra> (and back then it was recent ... i didnt expect the silo to sit there for a week)
[16:15] <sil2100> ogra, didrocks, cyphermox, sergiusens: as always, I jump out now and do the rest of my shift after getting back
[16:15] <sil2100> sergiusens: let's finish up on the transition then
[16:15] <ogra> ++
[16:19] <sergiusens> I'll show up to your meeting now
[16:31] <didrocks> cjwatson: it will ignore the whole state until it's published in the release pocket in fact
[16:32] <didrocks> cjwatson: ah, it was
[16:32] <didrocks> so yeah, I have to reread my code apparently :)
[16:32] <dbarth> Laney: ping again? any chance my FFE can get attention today; otherwise I need to find a solution to unblock the rest of qt 5.2
[16:33] <dbarth> didrocks: regardless of the FFE, getting the silo in place would let us test things in a clean environment, can you assign us a silo for that or you're short on them?
[16:33] <Laney> dbarth: umm, how is it blocking that?
[16:33] <Laney> Can you ask in #ubuntu-release? Someone else might be able to help
[16:33] <dbarth> ok
[16:34] <cjwatson> seb128: could you publish 004 again?  one-line fix needed
[16:34] <cjwatson> -            registry = Click.User(db, name=options.user)
[16:34] <cjwatson> +            registry = Click.User.for_user(db, name=options.user)
[16:34] <Laney> The bug report didn't say that it was massively urgent
[16:34] <didrocks> dbarth: as told, I don't want to assign a silo to trash Mirv's work if you can't release in time or if the FFe is rejected
[16:34] <didrocks> dbarth: would have been better in first place to plan the FFe ahead
[16:34] <cjwatson> manual tests looking good otherwise, just need to run an AP or three
[16:34] <dbarth> then we won't be able to release today
[16:34] <dbarth> cause the ffe has not been reviewed yet
[16:35] <dbarth> then we will need the silo, testing, and all
[16:35] <seb128> cjwatson, do you need to bump the version?
[16:35] <seb128> cjwatson, I can't rebuild a 17.1 again
[16:35] <dbarth> so better stay aside, and land the rest instead
[16:35] <cjwatson> seb128: I did, it's 0.4.17.2 in lp:click
[16:35] <didrocks> dbarth: ok
[16:35] <seb128> cjwatson, oh, ok, I got confused while looking at the commit message on https://code.launchpad.net/~click-hackers/click/trunk/+merge/209698
[16:35] <cjwatson> just didn't want to paste that part into IRC :)
[16:36] <didrocks> dbarth: the reverts will be injected in your trunk with the Qt 5.2 landing as told previously
[16:36] <dbarth> sorry i hope it's not a catch 22 situation
[16:36] <seb128> cjwatson, you had a "releasing package click version 0.4.17.1" and not equivalent for .2
[16:36] <cjwatson> right, that's because I expect the CI lander to tag whichever one finally works
[16:36] <dbarth> ok, so we'll prep a new set of MPs once the qt-5.2 situation settles
[16:36] <cjwatson> but I wanted to tag the failed attempts along the way too
[16:36] <seb128> cjwatson, the changelog is UNRELEASE, is that ok?
[16:36] <cjwatson> yep, the lander will sort that out
[16:37] <seb128> cjwatson, ok, rebuild started
[16:37] <didrocks> hum, that will be an interesting situation (without changelog rewrite)
[16:37] <cjwatson> it was the same for 17 and 17.1
[16:37] <didrocks> let's see how it goes
[16:37] <seb128> hum
[16:37] <seb128> http://162.213.34.102/job/landing-004-1-build/49/console
[16:37] <seb128> it's not happy
[16:37] <seb128> oh, sorry
[16:37] <didrocks> seb128: right, you know that one :p
[16:37] <seb128> I've to check the ignore box
[16:37] <didrocks> yep
[16:38] <seb128> didrocks, I hadn't for the previous one, but that's because the 1st ftbesed
[16:38] <sergiusens> didrocks, joining the landing team meeting to discuss since irc threads are killing me today :-P
[16:38] <didrocks> seb128: yeah, I meant, you already know why I prevent doing that :)
[16:38] <seb128> didrocks, indeed
[16:38] <didrocks> sergiusens: you are more than welcome :)
[16:38] <didrocks> seb128: I should probably special case in case you click "build" and number of components == 1
[16:38] <seb128> cjwatson, ok, build started
[16:38] <ogra> plars, next image should be fine again on manta
[16:38] <cjwatson> seb128: thanks
[16:39] <ogra> (just uploaded a fix for adbd)
[16:39] <plars> ogra: great!
[16:39] <ogra> sorry for the breakage, manta uses a weird setup for the android gadget driver
[16:47] <davmor2> rsalveti: I'm having a quick play with the x86 emulator is there a way to update the image on it or should the image be current
[16:59] <rsalveti> davmor2: I'll create another image probably later today, but you can't update it still
[17:02] <didrocks> davmor2: coming?
[17:02] <didrocks> sergiusens: you wanted to join as well, right?
[17:03] <davmor2> didrocks: on my way
[17:03] <sergiusens> yup
[17:09] <cjwatson> category: questions whose answers I should know.  what's the current simplest way to run a click AP test suite on a device?
[17:14] <cyphermox> cjwatson: https://wiki.ubuntu.com/Touch/Testing#Running_Click_tests ?
[17:14] <cyphermox> not sure, it doesn't happen often for me ;)
[17:15] <cyphermox> I'm hoping that's still up to date
[17:15] <balloons> sergiusens, we should talk click-buddy at some point. I'm curious about dependency handling
[17:18] <cjwatson> cyphermox: worth a try, thanks
[17:19] <cjwatson> cyphermox: bit freaked out that it does apt-get source unity8, but I guess that's for its AP tests
[17:19] <cjwatson> pull-lp-source, rather
[17:19] <cyphermox> oy
[17:19] <cyphermox> yeah, seems wrong-ish
[17:19] <cyphermox> the ap tests should live in unity8-autopilot anyway
[17:20]  * cyphermox tries to hard-rewire his brain so that AP == autopilot, not access point
[17:20] <sergiusens> balloons, in theory; there shouldn't be dependencies if they are build dependencies
[17:26] <psivaa> elopio: mako-07 has been reinstalled. you could rerun the job
[17:27] <sergiusens> balloons, expanding on that; I talked to xnox and he consulted with cjwatson and said it would be ok to install extra build deps in the click chroot as long as the packages don't end up depending on anything strange (as in some lib we don't want to have to maintain compatibility with)
[17:27] <sergiusens> didrocks, silo done; so I'm going to start testing
[17:28] <didrocks> sergiusens: sweeet!
[17:28] <cjwatson> xnox has a branch awaiting my review to add session support to click chroot, so you'd be able to install them temporarily more easily
[17:29] <davmor2> didrocks: so balloons issue with the n7 camera flashing was resolved by realising flo has no flash :)
[17:29] <didrocks> ahah
[17:29] <davmor2> didrocks: this brings up the issue then on if the camera app should disable the feature and is flash listed in the hardware to know if there is one
[17:29] <balloons> ohh session support would be nice, I'm usually doing the manual task of installing the extra deps to build.. But I'm thinking more on the execution side. We use to push python-mock, the toolkit, unity, etc modules in phablet-test-setup
[17:30] <didrocks> davmor2: yeah, I think the whole "what does this hw support and what can I install" will need work
[17:31] <davmor2> didrocks: so safe to ignore for now but maybe update the bug that balloons has written right?
[17:31] <didrocks> yep
[17:31] <didrocks> please feel free :)
[17:32] <davmor2> balloons: ^ so just make your bug about better hardware detection and software limiting it's spec based on the hardware detection :)
[17:33] <balloons> sergiusens, ^^ see above. I was thinking about required test runtime modules
[17:34] <sergiusens> balloons, oh; wrt I asked you to review an MR two Fridays ago ;-)
[17:35] <balloons> sergiusens, hmm.. https://code.launchpad.net/~sergiusens/phablet-tools/emu_prov/+merge/207440
[17:35] <balloons> I was traveling too much, and failed.
[17:35] <sergiusens> balloons, yeah, that one ;-)
[17:36] <elopio> psivaa: thanks.
[17:36] <robru> bregma, ping about lp:unity status
[17:36] <bregma> robru, everything got resolved last night
[17:37] <robru> bregma, but it looks like lp:unity still contains bschaefer 's two accidental unreleased trunk commits?
[17:37] <elopio> doanac`: do you know why there is no rebuild link for me on this job? http://q-jenkins.ubuntu-ci:8080/job/autopilot-release-gatekeeper
[17:37] <elopio> not a big deal if you are busy, but it would make it a lot nicer.
[17:38] <balloons> sergiusens, ok last question.. Thoughts on this: http://paste.ubuntu.com/7045332/
[17:38] <bregma> robru, yes, it wasn't worth risking further corruption: they'll get released with the next landing anyway
[17:39] <doanac`> elopio: it could be the jenkins configuration. "rebuild" is a plugin. it might not be on q-jenkins
[17:39] <robru> bregma, hmmm, didrocks just asked me to --overwrite with lp:~ps-jenkins/unity/trusty-proposed
[17:39] <kgunn> tvoss: i'm still testing...i haven't forgotten...just need to check a few more things..
[17:39] <sergiusens> balloons, how old is your click chroot
[17:39] <sergiusens> ?
[17:40] <sergiusens> balloons, cmake should be in there
[17:40] <cjwatson> you could click chroot -a armhf -s trusty maint apt-get update; click chroot -a armhf -s trusty maint apt-get dist-upgrade
[17:40] <cjwatson> or just destroy and re-create
[17:43] <robru> bregma, sorry to step on your toes, but I just did the overwrite and everything looks fine now. lp:unity has nicer commit log as well, bonus ;-)
[17:43] <robru> bregma, so bschaefer can just MP his commits later when they're ready
[17:46] <bregma> thanks robru I'll have the upstream developers keep a log of the hours wasted while recovering from the diverged branches
[17:46] <robru> bregma, ok sorry, was requested straight from didrocks
[17:47] <didrocks> hum, I suggested that
[17:47] <didrocks> didn't force, but robru told me that trunk had commits that were not released
[17:47] <didrocks> and so it was all mixed up
[17:47] <robru> didrocks, well, it did have unreleased commits
[17:48] <didrocks> so yeah, maybe important, but always checking with upstream if they are ok with it to, or working with them to reconciliate the branches
[17:48] <didrocks> too*
[17:50] <didrocks> bregma: so, if you want to help on that you can repush your own branch (at the same revision)
[17:50] <didrocks> as you started from that one apparently
[17:51] <didrocks> and try to look at how getting trunk == version in distro
[17:51] <didrocks> like redoing a release, populating the changelog manually for the 2 commits, for instance
[17:51] <didrocks> so that you don't need to have a log of "hours"
[17:52] <bregma> didrocks, no, the changes should really go through the regular process, it's only developers who had checked out lp:unity since last night and made changes who are affected
[17:52] <bregma> no one has complained yet, so we're probably safe
[17:52] <didrocks> (wasted)
[17:52] <didrocks> but not to make our time wasted, answers would be appreciated
[17:52] <didrocks> bregma: and bschaefer pushed to trunk? he still have his branches?
[17:53] <didrocks> so be able to MP them back?
[17:53] <didrocks> to*
[17:53] <bschaefer> didrocks, it was an accident where i made a change to branch and did a bzr push :parent
[17:53] <bregma> didrocks, yes, and his tail is between his legs life a beaten dog
[17:53] <robru> didrocks, the bschaefer thing was an accident, he apologized already, no malice intended
[17:53] <bschaefer> didrocks, yeah, ill just have to re-propose them
[17:53]  * bschaefer is also wearing a cone of shame
[17:54] <robru> bschaefer, it's not *that* bad... just unfortunately compounded with lp connectivity issues making the resolution take longer than it should have
[17:54] <didrocks> bschaefer: I'm more afraid of you loosing your work than anything :)
[17:54] <didrocks> bschaefer: ahah ;)
[17:54] <bschaefer> robru, right, I should have been able to uncommit, push --overwrite and been done then it started hanging!
[17:55] <didrocks> bregma: well, accidents happen :)
[17:55] <bschaefer> didrocks, :)
[17:55] <didrocks> bregma: bschaefer: so, if you didn't get the launchpad hosting issue yesterday, normally, we would have the real branch
[17:55]  * bschaefer will not use :parent to push anymore
[17:55] <didrocks> and an additional merge
[17:55] <didrocks> "resync trunk"
[17:55] <didrocks> on top of it
[17:55] <robru> bschaefer, yeah, that's basically what I just did and it was fine... go figure
[17:55] <didrocks> which would have contained bschaefer's work
[17:56] <bschaefer> robru, dang! I tried around 5 times haha
[17:56] <didrocks> bschaefer: yeah :parent is dangerous :p
[17:56] <bregma> the lp:unity branch got corrupted, I had to run 'bzr check' before it would accept anything at all
[17:56] <bschaefer> didrocks, yeeah, sometimes i get lazy to get the real path of my branch (as i decided to make my lp name brandontschaefer)
[17:56] <didrocks> bregma: you were the only one to have that issue? was limited to lp:unity?
[17:57] <bregma> well, the merge&clean had the issue, bschaefer had an issue, I had an issue
[17:57] <robru> bschaefer, you can use ~ in place of your own name, like lp:~/unity/my-branch
[17:57] <bschaefer> robru, well that is very nice to know actually
[17:58] <didrocks> bregma: yeah, and I saw that it was able to push at other locations…
[17:58] <didrocks> really weird
[17:58] <robru> bschaefer, even with my short name i still always use ~. I can't imagine typing 'brandontschaefer' every time, wow ;-)
[17:58] <bschaefer> robru, yeeah i usually end up copying the branch name :), now that should speed up my pushes :)
[17:58] <cjwatson> "cjwatson" is so utterly wired into my fingers that I tend to type it out :)
[17:59] <cjwatson> ok, click 0.4.17.2 looks good (gallery, calendar, music, notes all passed; had to rerun a few tests but they got there in the end).  could somebody please land this for me from silo 004?  seb128 published it for me but I don't know if he's still around, as it's getting late there.
[17:59] <seb128> cjwatson, I can do taht
[17:59] <didrocks> cjwatson: I expect many failures from you the day we'll have again a release starting with a "c" :)
[17:59] <cjwatson> oh great
[17:59] <didrocks> cjwatson: you can do it as well btw
[17:59] <cjwatson> didrocks: oh yes, indeed we've never had a "c"
[17:59] <cjwatson> didrocks: I can?  I've never had ci train training
[18:00] <didrocks> cjwatson: yeah, in case you end up in a special case, you'll have to ask, but core-devs have access to publication
[18:00] <didrocks> cjwatson: default is always "click -> build, no option"
[18:00] <cjwatson> how do I get to that then?
[18:00] <seb128> cjwatson, http://162.213.34.102/job/landing-004-2-publish/build if you want to try to click it
[18:00] <didrocks> then, if we are in a special case, options to overrides/change behavior are there and it's better for you to ask in that case :)
[18:00] <seb128> cjwatson, https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFlCc1VzeVZzWmdBZS11WERjdVc3dmc#gid=22 has the links
[18:00] <cjwatson> ok, let's see
[18:02] <cjwatson> so I want to check ACK_PACKAGING but not the others, right?
[18:02] <seb128> correct
[18:02] <didrocks> (only needed if you have packaging changes, of course. debian/changelog doesn't count as a packaging change)
[18:03] <seb128> cjwatson, job SUCCESS ;-)
[18:03] <cjwatson> yeah, extensive packaging changes here :)
[18:03] <seb128> cjwatson, you can do the merge&clean later when the package is in the release pocket
[18:03] <cjwatson> yep
[18:04] <didrocks> cjwatson: you can track line 36 the migration as well (don't need to hit rmadison hard)
[18:04] <didrocks> even if I know it's not an issue for you on that one, just wanted to mention
[18:04] <cjwatson> yeah, personally I tail the publisher log ;-)
[18:04] <didrocks> how to tell I'm not surprised :p
[18:07] <cjwatson> the overrides will be wrong, I'll need to fix those, will take an extra publisher cycle
[18:07] <cjwatson> (for the new binaries)
[18:10] <cjwatson> argh, being called for dinner
[18:10] <didrocks> enjoy :)
[18:10] <seb128> didrocks, I just noticed on that case because cjwatson ended up bumping the version in-between fixes, but the .changes uploaded contains only the most recent entry and not all the ones which are part of the landing
[18:10] <didrocks> seb128: yeah, I'm a little bit puzzled on that because I handle that case
[18:10] <cjwatson> might be an lp bug
[18:10] <didrocks> seb128: mind opening a bug? I'll have a look
[18:10] <seb128> didrocks, can do
[18:10] <didrocks> ah
[18:11] <cjwatson> oh, there we go, I can fix the overrides if I remember -s trusty-proposed
[18:11] <didrocks> I can check quickly first
[18:11] <didrocks> the .changes
[18:11] <cjwatson> I think it'll close the bugs anyway, it works from what it has to what it's getting
[18:11] <cjwatson> might just be wrong on trusty-changes
[18:11] <seb128> k
[18:11] <didrocks> yeah
[18:11] <seb128> similar to syncs
[18:11] <didrocks> I do use -V
[18:12] <didrocks> and the .changes is fine
[18:12] <didrocks> (containing 0.4.17.1 and 0.4.17)
[18:12] <cjwatson> gone, I'll merge and clean later
[18:12] <didrocks> see you cjwatson
[18:12] <cjwatson> ta
[18:12] <didrocks> seb128: so, not for me :)
[18:12] <seb128> didrocks, good, less bug opening to do for me as well ;-)
[18:13] <didrocks> ahah :)
[18:18] <rsalveti> sergiusens: what packages are moving to click? I know gallery-app is one of them, what is the other one?
[18:28] <sergiusens> rsalveti, camera
[18:28] <rsalveti> sergiusens: cool
[18:30]  * didrocks wonders how rsalveti can hear the word "camera" without screaming yet
[18:30] <sergiusens> rsalveti, just running ap now; which is not as fast
[18:30] <rsalveti> didrocks: haha :-)
[18:31] <rsalveti> sergiusens: yeah
[18:39] <sergiusens> rsalveti, btw; the issue I see with flo is when the camera is on; I lock and then unlock; it seems a couple of buffers are dequeued and we get the same issue as mako; is that the mir issue you mentioned?
[18:40] <rsalveti> sergiusens: hm, with latest image?
[18:40] <sergiusens> rsalveti, nope; I was on holidays ;-)
[18:41] <rsalveti> sergiusens: oh, ok, should be better with latest
[18:41] <sergiusens> camera and gallery ran fine on flo; now triggering unity8
[18:41] <sergiusens> rsalveti, were the changes done in hybris?
[18:42] <rsalveti> sergiusens: yes
[19:05] <kgunn> robru: hey...i've found a bug that i don't want to release for unity-mir....all in all the packages looked really good but i found one strange specific use case around osk that seems broken....
[19:05] <kgunn> and tvoss needs a silo for platform-api
[19:05] <robru> kgunn, uhhh
[19:06] <robru> kgunn, are you asking me to abandon the silo and assign tvoss?
[19:06] <tvoss> kgunn, robru no need to
[19:06] <tvoss> I will look into landing tomorrow the earliest
[19:06] <robru> kgunn, well it sounds like you have all day to fix your bug then.
[19:07] <kgunn> hey thanks tvoss ...i'll try one more trick, yeah...i'll ask for a reconfig in a moment robru
[19:07] <robru> kgunn, ok, just ping me once the spreadsheet has the correct MPs
[19:16] <kgunn> robru: ok, got for it....reconfig
[19:16] <kgunn> hopefully reconfig works this time :) ....last night we had a reconfig that decided not to participate and kept including the deleted mp
[19:17] <robru> kgunn, hmm, yes, it seems the reconfigure job has changed...
[19:19] <robru> kgunn, ok, the new thing is broken, trying it the old way...
[19:19] <robru> kgunn, ok, looks good, please build
[19:20] <kgunn> robru: rock on...building...thanks
[19:20] <robru> kgunn, you're welcome
[19:23] <om26er> Saviq, is there another interface that I should rely on ? otherwise I can try with unity8' pid
[19:33] <Saviq> om26er, I thought unity8.autopilot.process_helpers.{restart_unity_with_testability,unlock_unity} would be used
[19:41] <om26er> Saviq, right, we can use that as well.
[19:41] <om26er> just need to make sure unity8-autopilot is installed on the device first
[19:54] <robru> sergiusens, so, I've been assigned to help you land the click conversion today. how's that going? are you ready for me to test the silo?
[19:54] <sergiusens> robru, oh, I'm testing the silo
[19:54] <sergiusens> that's my status
[19:54] <sergiusens> :-)
[19:55] <robru> sergiusens, great, no worries. is the seed rebuilt already?
[19:55] <sergiusens> robru, doesn't need to be rebuilt
[19:55] <robru> sergiusens, but it *is* built though?
[19:56] <robru> sergiusens, ah, i see ubuntu-touch-meta is in the silo, i guess that's fine then.
[19:57] <robru> sergiusens, ok, just ping me when you're satisfied and then i'll start poking at it
[20:01] <sergiusens> robru, ok
[20:01] <sergiusens> robru, keep in mind that for accurately testing this; there's a bunch of preconditons 'manual hand holding'
[20:03] <robru> sergiusens, oh yeah? like what?
[20:05] <sergiusens> robru, remove debs; build and install clicks
[20:05] <robru> sergiusens, well that makes sense.
[20:18] <sil2100> Back if anything
[20:18] <sil2100> robru, sergiusens: is the ubuntu-touch-meta in the silo up-to-date?
[20:20] <robru> sil2100, seems so? it's from feb 22nd, and it's changelog says it's dropping camera-app and gallery-app.
[20:22] <sil2100> hmmm
[20:22] <sil2100> Since there are some more changes pilled up in the bzr branch, not sure if Laney didn't want those released?
[20:23] <sil2100> It's a bit confusing to me
[20:23] <robru> sil2100, yeah i have no idea.
[20:23] <robru> sil2100, surely the one in the silo can be released for the purposes of that silo, and then other updates can get released later?
[20:23] <sergiusens> sil2100, it's needed
[20:23] <sil2100> sergiusens: I know it's needed, but I thought it might maybe need updating
[20:24] <sil2100> sergiusens: like, rebasing on what's in the bbzr branch
[20:24] <sil2100> Laney: are you still around?
[20:24] <sergiusens> sil2100, when you ask me if I updated it and with me living in the context of my silo; I can't really know how to answer you ;-)
[20:25] <sil2100> Well, never mind I guess ;)
[20:25] <sil2100> Just make sure it has all the changes that are in the archive I guess!
[20:25] <sil2100> sergiusens: is the testing process for it ongoing?
[20:25] <sergiusens> yes
[20:27] <sil2100> sergiusens: is it possible that we land this today?
[20:27] <sil2100> :)
[20:30] <sergiusens> as I mentioned in the landing team meeting; yes
[20:30]  * sil2100 missed out on that meeting
[20:31] <sil2100> sergiusens: once all is prepared, could you also give me a ping?
[20:31] <sergiusens> robru, if you want; it should be safe to run the autopilot tests for unity8 on your side
[20:48] <robru> sergiusens, are the click apps in the store yet? can't seem to find them
[20:50] <sergiusens> robru, no, needs to land in trunk first; that's why it's complicated
[20:50] <robru> sergiusens, oh, wow.
[20:51] <robru> sergiusens, I can't seem to actually launch any apps with the unity8 from your silo.
[20:51] <sergiusens> train design came after click design
[20:51] <sergiusens> robru, really? I bet you just can't launch gallery and camera from home lens
[20:52] <robru> sergiusens, surely you can build a click package and upload it to the store independently of the ci train landing? like just build from the branch
[20:52] <robru> sergiusens, well, webbrowser app won't launch.
[20:52] <robru> sergiusens, hmm, dialer launched but it was slow
[20:53] <asac> plese be extra careful about whatever you do here :)
[20:53] <sergiusens> robru, strange since the unity8 change is two text files; that's it
[20:53] <asac> we have no room for mistakes until qt5.2 lands
[20:53] <robru> sergiusens, yeah, i'll have to revert the silo and see if the image has this problem too. but i can't launch any webapps at all, they just come up as a blank window and then if i swip away from them, they don't appear in the running apps list.
[20:53] <sergiusens> robru, browser worked fine for me
[20:54] <sergiusens> robru, they all work for me; so you need to install the meta first; autoremove gallery and camera and then dist-upgrade
[20:54] <sergiusens> robru, and start fresh
[20:54] <sergiusens> (no prior dev mode)
[20:55] <robru> sergiusens, what do you mean 'no prior dev mode'? do you mean i have to bootstrap the phone? because i started this morning with a fresh flash, but it has my login and installed apps from previous usage
[20:56] <rsalveti> sergiusens: hey, ubuntu-device-flash is not removing /userdata/.writable-flash when you flash it from scratch (even when using -b)
[20:56] <rsalveti> just noticed my flo was always with writable-mode enabled
[20:56] <sergiusens> rsalveti, hmmm, 'format data' is busted then :-/
[20:57] <sergiusens> rsalveti, let me fix that in the upgrader script directly
[21:05] <robru> sergiusens, hummm, dist-upgrade didn't fix it. reflashing then....
[21:07] <sergiusens> robru, I'm good with the tests fwiw
[21:07] <sergiusens> robru, tested mako and flo
[21:08] <robru> sergiusens, ok, i'm just poking mako before I can approve this
[21:24] <kgunn> robru: can you reconfig me one more time in silo 3 ?...last attempt for me on this one
[21:24] <robru> kgunn, sure
[21:26] <robru> kgunn, and done! please build ;-)
[21:27] <robru> sergiusens, ok, webapps are looking fine now after a bootstrap, I guess I just had some cruft lying around. you ready for a publish?
[21:27] <bfiller> robru: can we get a silo for line 38 please?
[21:27] <robru> bfiller, sure
[21:28] <sergiusens> robru, yes; I am
[21:29] <sergiusens> robru, keep in mind that I still have work to do before an image can be published
[21:30] <sergiusens> robru, s/published/triggered/
[21:30] <robru> sergiusens, ok. cron kicks an image build in about 5 hours I think.
[21:30] <robru> sergiusens, ok, silo 7 published!
[21:30] <robru> bfiller, bah! it looks like address-book-service is blocked by the qt52 landing
[21:31] <bfiller> robru: ah ok
[21:31] <robru> bfiller, we're hoping to get that done by tomorrow.
[21:31] <bfiller> sergiusens: how we looking on our favorite click packages :)?
[21:32] <sergiusens> bfiller, being publish, as soon as it's merged it's going to the store; and then ci test runner update, then DONE
[21:33] <robru> sergiusens, excellent, should be mergable within an hour, barring any troubles in -proposed
[21:33] <bfiller> sergiusens: you're my hero
[21:33] <bfiller> :)
[21:33] <sergiusens> lol
[21:33] <bfiller> sergiusens: then we can do it again next week for the next batch :)
[21:33] <sergiusens> bfiller, are you just warming me up for the next ones? :-P
[21:34] <bfiller> exactly
[21:34]  * sergiusens wishes the hard codings are gone by then ;-)
[21:34] <bfiller> hopefully they are easier
[21:34] <robru> bfiller, it should be easier once qt52 is not locking 80% of the entire company ;-)
[21:37] <sil2100> \o/
[21:37] <cjwatson> give me a shout if there are troubles in -proposed, SMS or whatever - would rather be rousted to investigate that than have people blocked even more tomorrow
[21:38] <cjwatson> hopefully unnecessary though :)
[21:38] <robru> cjwatson, yep, i'm not aware of any reason there would be a problem, but sometimes there are surprises.
[21:42] <Laney> sil2100: Whatever, I'll upload that later
[21:42] <sil2100> balloons: hello!
[21:43] <balloons> sil2100, hpwdy
[21:43] <sil2100> Laney: k
[21:44] <sil2100> balloons: I wasn't on the meeting, but any progress related to weather-app?
[21:45] <balloons> sil2100, yes.. I feel like we'll have something that should solve it or come very close ;-)
[21:45] <rsalveti> sergiusens: why did we published the meta changes that adds gst0.10 to the seeds?
[21:45] <balloons> part is merged, I'm just digging through another mp to squeeze the last questionable things out
[21:47] <rsalveti> sergiusens: bfiller: can I remove the gst0.10 packages from the seeds?
[21:47] <bfiller> rsalveti: gallery hasn't landed yet with those changes, but it has an explicit dep so that should be ok
[21:48] <rsalveti> bfiller: hm, so I guess we first need to wait those changes to land (and be in a click package)
[21:49] <rsalveti> which is fine, just thought they would also be part of the click transition
[21:52] <sergiusens> rsalveti, it's not
[21:52] <sergiusens> rsalveti, that's what I mentioned in #ubuntu-touch
[21:52] <bfiller> rsalveti: and we found an issue with the MR
[21:53] <bfiller> rsalveti: so hopefully we can resolve that tomorrow
[21:53] <rsalveti> great, no worries
[21:53] <sergiusens> bfiller, btw, you can't really drop it from the seeds as there are no deps in click ;-)
[21:53] <bfiller> sergiusens: oh
[21:53] <sil2100> balloons: awesome!
[21:53] <bfiller> sergiusens: thought you had a way to deal with that?
[21:54] <sergiusens> bfiller, yeah, adding to the seeds
[21:54] <bfiller> hah
[21:54] <bfiller> not a good way (:
[21:55] <sergiusens> bfiller, it's the cleanest way; I don't like it; but that's a different story
[22:05] <sergiusens> bfiller, the other way is to embed the 3rd party sources into the source tree
[22:05] <bfiller> sergiusens: that's worse
[22:05] <sergiusens> bfiller, that's the click philosophy
[22:05] <bfiller> sergiusens: having a deps section like debs would be good
[22:06] <bfiller> sergiusens: reminds me of the ufa stuff we did
[22:06] <sil2100> balloons: you think it can land like till tomorrow?
[22:06] <sergiusens> bfiller, yeah, think of it as the android api level;
[22:06] <sergiusens> bfiller, the seed is sort of the api level
[22:07] <balloons> sil2100, yes I will push something to the store no matter what which should help
[22:10] <om26er> doanac`, https://code.launchpad.net/~om26er/ubuntu-test-cases/update_unlock_script/+merge/209800
[22:11] <doanac`> om26er: thanks! the code looks a lot nicer now also!
[22:11] <doanac`> plars: you want to merge this fix as you merge your MP?
[22:12] <om26er> doanac`, yeah and simpler
[22:12] <plars> doanac`: I can merge it, sure. I'm just waiting on sergiusens to give me the green light on camera/gallery :)
[22:13] <doanac`> plars: we have unity8-autopilot in the image when this will run right?
[22:13] <doanac`> ie - that's a click package?
[22:13] <om26er> its a deb
[22:13] <plars> doanac`: no, that one is fine
[22:13] <om26er> might make sense to actually get that thing on the image by default
[22:14] <plars> in actuality, I'm not sure if it matters whether we install the autopilot package other than the deps it may need to bring in
[22:14] <sil2100> balloons: :D
[22:15] <plars> that's the one for which phablet-click-test-setup makes sure the bzr branch checked out matches the rev of unity installed
[22:16] <sergiusens> doanac`, plars, still in progress
[22:16] <bfiller> robru: is qtorganizer5-eds blocked for qt5.2 as well? if not line 39 needs a silo. this is partial fix for the clock app blocker
[22:44] <pmcgowan> bfiller, that would cause a deadlock then ;)
[22:44] <pmcgowan> as we need clock fixed to promote to land qt 5.2
[22:45] <pmcgowan> looks like organizer is in the other silo
[22:45] <bfiller> pmcgowan: ok good
[22:45] <pmcgowan> bfiller, well not really
[22:45] <pmcgowan> bfiller, we want to land it for image promotion, then update timo's qt silo
[22:45] <bfiller> pmcgowan: wait, so can we land it now or not until 5.2?
[22:46] <pmcgowan> bfiller, we need to land it to fix clock
[22:46] <bfiller> right
[22:46] <pmcgowan> but will then need to fix the other silo somehow
[22:46] <pmcgowan> need a landing expert
[22:47] <pmcgowan> i hear crickets
[22:48] <pmcgowan> bfiller, I think the sequence is to remove it from the other silo (6) then make a new landing, then update the qt silo with the newer package
[22:48] <bfiller> pmcgowan: sounds reasonable
[22:48] <bfiller> pmcgowan: well the good news is the bug is basically fixed :)
[22:48] <pmcgowan> yar
[22:48] <sergiusens> pmcgowan, bfiller another option is to distro patch
[22:48] <pmcgowan> lots of bugs fixed today
[22:49] <sergiusens> supposed to be allowed
[22:49] <pmcgowan> means?
[22:49] <bfiller> why are we letting on clock bug grind the process to a halt? seems like we have a fix, just roll with it
[22:49] <sergiusens> pmcgowan, not do it through an MR but a patch
[22:49] <bfiller> no disrepect to clock, but it's just the clock
[22:49] <pmcgowan> right
[22:51] <sergiusens> bfiller, pmcgowan I'm always in favor of balanced decision in these cases, but I haven't been in the landing game for a while now :-)
[22:51] <pmcgowan> sergiusens, we have all the fixes we need, just need to orchestrate the landings
[22:51] <bfiller> sergiusens: lucky you :)
[22:52] <robru> bfiller, let me check
[22:52] <sergiusens> bfiller, I'm still unluckily involved
[22:52] <sergiusens> :-)
[22:53] <robru> bfiller, ahhh sorry, qtorganizer5-eds is also blocked
[22:53] <sergiusens> robru, seems we are good for merge and clean of silo 7?
[22:54] <robru> sergiusens, yes, please do!
[22:55] <bfiller> robru: right, see backlog what pmcgowan was suggesting
[22:56] <bfiller> not sure if possible
[22:57] <robru> bfiller, oh I see. didn't realize qt5.2 was blocked on this. ok let me see what i can do
[23:02] <pmcgowan> robru, bfiller if the logistics are too difficult, the alternative would be to just declare victory with the knowledge the fix is known
[23:02] <pmcgowan> but not ideal
[23:03] <bfiller> pmcgowan, robru : +1 from me
[23:03] <robru> pmcgowan, no worries, I am bumping qtorganizer5-eds from the qt52 silo as we speak. I should be able to assign a silo shortly.
[23:03] <pmcgowan> perfect
[23:03] <robru> (qt52 silo is so huge it takes a long time to reconfigure)
[23:04] <pmcgowan> the desired sequence is clock fixes, weather app fix -> promote image -> mir landing -> qt landing -> etc
[23:07] <bfiller> I need to go, will be back on later
[23:08] <robru> bfiller_afk, ok, I got you silo 2, and I started building for you too since you're afk. please start testing when you get back
[23:37] <kgunn> robru: please sir...just one more....silo3 reconfig
[23:37] <robru> kgunn, haha, no worries
[23:37] <kgunn> and when its done building &  i flash ...i'll give up the silo...i just need to take a video of it in that config
[23:38] <robru> kgunn, recon complete. please build!