[01:22] <rvr> ToyKeeper: dobey: Ok, I just saw something very strange trying to verify the fix. I cancelled, but... the app was installed!
[06:06] <Mirv> renatu: the silo 024 qtpim avatar import fix has a comment from QA in trello
[06:11] <Mirv> 014 OTA-8 bugfix made 026 dirty, forcing ubuntu-push rebuild - the commits itself in 026 stay the same obviously
[06:40] <Mirv> another to get the updated trunk for real
[09:14] <abeato> Mirv, hey, robru uploaded yesterday the  qtmultimedia-opensource-src package to silo 9, but I think we also need to upload the derived package qtmultimedia-opensource-src-gles
[09:25] <Mirv> abeato: ok, I can handle it. I also remind you that I really hope no API migration mess will come out of this, ie those changes have not been submitted to upstream or accepted by them. but Jim has told me he does not expect trouble this time.
[09:26] <abeato> Mirv, noted, thanks
[09:57] <rvr> Mirv: ping
[10:08] <Mirv> rvr: pong
[10:08] <rvr> Mirv: Hey
[10:09] <rvr> Mirv: I left a comment on the card for silo 24
[10:09] <rvr> Mirv: The photo is correctly imported from Google, but not correctly exported (or at least, Google doesn't read the photo).
[10:11] <Mirv> rvr: right, I pinged renatu already about that, but he's in another timezone. I'm just providing the packaging, renatu is the lander here so I can't comment on the export case.
[10:12] <rvr> Ahh, I see
[10:46] <cjwatson> snakefruit (various archive cron jobs, http://people.canonical.com/~ubuntu-archive/, etc.) going down soon for a RAM upgrade
[11:08] <Mirv> hmm, are xenial images unbootable on mako currently?
[11:09] <Mirv> mine is just stuck in Google screen, even after doing a bootstrap flash
[11:24] <Mirv> ok wipe + bootstrap did the trick
[11:30] <cjwatson> snakefruit back
[11:38] <Mirv> ah, nope, that was vivid accidentally, xenial still shows just Google screen so I guess it's dead at the moment
[11:38] <renatu> rvr, hey what is the problem with the avatar export?
[11:39] <rvr> renatu: I exported the vcard and imported it back to Google, and the contact didn't show the photo
[11:40] <renatu> rvr, did you try import it on android?
[11:40] <rvr> renatu: So I don't know whether it is a problem of Google or what
[11:40] <rvr> renatu: I don't have any android around, just using the web
[11:40] <renatu> rvr, works nice on android
[11:40] <renatu> I never tried import on gmail
[11:41] <renatu> rvr, we have this bug for iphone: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1510259
[11:41] <renatu> rvr, the fix is on silo 2
[11:41] <rvr> renatu: I see
[11:41] <rvr> The contact is shared
[11:42] <rvr> It's just that Google doesn't like the photo field
[11:44] <renatu> rvr, the field looks correct to me, and works nice on android and iphone. Maybe we need something special for google
[11:45] <rvr> renatu: Ok
[11:45] <rvr> renatu: Mirv: I am approving the silo, just wanted to have some feedback about this
[11:47] <renatu> rvr, I will report a new bug about that
[11:47] <renatu> rvr, but this is not related with the silo changes
[11:51] <Mirv> rvr: renatu: thanks!
[11:51]  * Mirv publishing
[14:09] <renatu> alesage_, crash fixed on silo 2. You can continue the tests.
[14:19] <dobey> popey: hi. can you approve the com.canonical.payui 15.01.135 sitting in the store review queue please?
[14:24] <popey> dobey, will do
[14:25] <dobey> popey: thanks
[14:26] <popey> dobey, done
[14:26] <popey> np
[14:27] <mardy_> Mirv: good session! And now it's time to feed the cat! :-)
[14:29] <Mirv> mardy: thanks! and yeah :)
[14:39] <dobey> rvr: hi
[14:39] <rvr> dobey: Hi
[14:41] <dobey> rvr: so, the issue you found seems to not be new. i am able to recreate your issue with the old pay-service too. can you file a bug about it, so we can figure out how best to deal with this case, and we can move forward with the current landing?
[14:44] <rvr> dobey: Sure
[14:45] <dobey> rvr: thanks
[14:47] <rvr> dobey: Assign it to the correct project, if wrong https://bugs.launchpad.net/canonical-devices-system-image/+bug/1513093
[14:48] <dobey> pay-ui is probably where we'll need to fix it
[15:01] <dobey> rvr: do we need to wait for ToyKeeper? looks like she went through the test plan just fine from the comments
[15:05] <rvr> dobey: Let's wait for her approval, as she's the one that did most of the testing.
[15:08] <dobey> ok
[15:40] <Mirv> sil2100: hey Texas! any idea what's up with xenial images? I can't get past Google logo (have tried --bootstrap --wipe), but the phone is not bricked since I can (continue) to use vivid
[15:40] <pmcgowan> Mirv, xenial images totally busted, foundations looking at it
[15:42] <sil2100> Mirv: hey! Yeah, as pmcgowan mentioned, they be b0rken
[15:42] <sil2100> It's a known feature of our xenial images
[15:44] <Mirv> pmcgowan: sil2100: thanks! I'd have demoed xenial phone Qt 5.5.1 in my session but had to do with demoing xenial KDE on Qt 5.5.1 :)
[15:46] <robru> cihelp: s-jenkins builders are really broken. I had to disable a few of them
[15:49] <fginther> robru, thanks. Looking into the problem now
[15:49] <psivaa> robru: i assume you're talking about prodstack-worker-5 and the rest?
[15:49] <robru> psivaa: yeah
[15:49] <robru> fginther: thanks
[15:49] <robru> psivaa: I've had problems with 2, 5, 6, and 7.
[15:50] <dobey> i wonder when toykeeper will be around today
[15:50] <robru> fginther: psivaa: "problems" as in random java tracebacks unrelated to my actual branches
[15:50] <psivaa> robru: ack, thanks.
[16:13] <robru> psivaa: fginther oh god there's only 2 nodes available and the queue is out of control
[16:14] <fginther> robru, yes :-) it's not good
[16:34] <fginther> robru, more nodes are coming back now. Not sure what happened, but they are much happier after a reboot
[16:34] <robru> fginther: yaaay
[16:34] <robru> thanks
[16:51] <rvr> oSoMoN: Approving silo 39
[16:51] <oSoMoN> rvr, thanks!
[18:00] <dobey> so many queuebot notices
[18:07] <dobey> robru: btw, force merge didn't work. it fails without an MP or sync source
[18:07] <robru> k
[18:10] <dobey> ToyKeeper: please ping me when you're around.
[21:13] <ToyKeeper> dobey: Hi, didn't see your message until now.
[21:14] <ToyKeeper> dobey: I have early onset cold symptoms and crashed last night before finishing.  Looks like the silo is unblocked now, at least.
[21:16] <dobey> ToyKeeper: yeah, rvr wanted to wait for your approval before moving the landing ahead any further though. hope you're feeling better after resting
[21:16] <ToyKeeper> So far, yes.  :)
[21:17] <ToyKeeper> I doubt there will be any more issues with the landing.  It was just rvr's bug holding things back, and non-overlapping time zones.
[21:18] <dobey> yeah. there was a rebuild of ubuntu-push required though. i guess that needs retested?
[22:49] <alecu> hi trainguards: I see that silo 046 shows as "QA Granted". Do we need to do anything else to land it?
[22:49]  * alecu has not completed any landings with the new dashboard yet...
[22:49] <sil2100> alecu: hey! No, we need a core-dev to take care of those
[22:49] <alecu> great
[22:50] <sil2100> cyphermox: would you have a moment to look through the publishable box on the train? https://requests.ci-train.ubuntu.com/#/publishable
[22:53] <robru> alecu: generally speaking the answer is yes, once you see 'QA Granted' it is your responsibility to click the publish button. if your silo doesn't contain any packaging changes then you will be able to publish it yourself
[22:53] <cyphermox> sil2100: compiz, nux, unity for the silo 11 are missing diffs... I'm not comfortable publishing things that mention unity with no diff.
[22:54] <robru> balls
[22:54] <robru> cyphermox: I'll try to regenerate diffs and see what happens...
[22:59] <cyphermox> silo 16 introduces a "sync with main" changelog entry, UNRELEASED, in between other entries for stuff already released, this looks very very wrong -- that was ubuntu-ui-toolkit-gles
[22:59] <robru> cyphermox: sil2100: the build job in silo 11 suggests that those diffs are empty because the version in the silo is the same as the version in distro
[22:59] <cyphermox> so, why?
[23:01] <robru> cyphermox: it appears as though silo 11 was published already, just 4 hours ago, but only bamf was rebuilt since then
[23:01] <cyphermox> well, i'm not going to sign off on that
[23:01] <robru> cyphermox: so the ones that have empty diffs are really empty diffs, can be safely ignored (publish job won't republish redundant versions)
[23:01] <robru> cyphermox: bamf has a diff tho
[23:02] <robru> cyphermox: sorry, bamf and indicator-appmenu
[23:02] <robru> Trevinho: perhaps you could explain the situation in silo 11. it was published, then you rebuilt bamf and indicator-appmenu, now you want to publish again?
[23:03] <robru> cyphermox: this was published by Laney
[23:03] <Trevinho> robru: indicator-appmenu was not correclty rebuilt against new bamf, and so it was missing the wrong dependency
[23:03] <Trevinho> robru: so Laney told me to do this....
[23:04] <Trevinho> robru: indicator-appmenu and bamf published have to be updated with these new ones
[23:04] <robru> Trevinho: ok well it looks ok to me train-wise. I was worried the empty diffs were some kind of bug but it all looks legit. I'm not sure why cyphermox won't sign off
[23:05] <cyphermox> silo 46 adds tests and does cleanup that doesn't appear in the changelog?!
[23:07] <cyphermox> -Vcs-Bzr: https://code.launchpad.net/~unity-team/unity-lens-music/trunk
[23:07] <cyphermox> +Vcs-Bzr: https://code.launchpad.net/~unity-team/unity-lens-music/saucy
[23:07] <cyphermox> ^ wat?
[23:08] <cyphermox> oh, this one is amazing, it lists a ton of changes in changelog but I can't match them to stuff in the changes: https://ci-train.ubuntu.com/job/ubuntu-landing-042-1-build/lastSuccessfulBuild/artifact/unity-lens-music_content.diff
[23:09] <cyphermox> maybe all the changes in the other silos and uploads got merged there? :D
[23:14] <cyphermox> I think that's all of the "publishable" things, right?
[23:14] <sil2100> Crazy stuff
[23:14] <cyphermox> yup.
[23:14] <cyphermox> it was entertaining
[23:15] <cyphermox> I'm starting to think we'd benefit from core-dev review for some of these by people who have a better idea what the code does at all too thought