[00:44] <cjwatson> Saviq: I think it will be more an issue of availability of sufficient powerpc build capacity, since we don't quite have scalingstack on powerpc yet (though it's planned).  It's likely a good idea to restructure around PPAs since it makes better use of the company's build capacity for exotic architectures in general, but I don't know to what extent it would be an immediate answer for you.
[00:45] <cjwatson> Saviq: Creating devirt PPAs requires the LP user that's doing the creation to be specially privileged, so we would want to be careful about extending that to, say, lots of Jenkaas users.  (Having scalingstack on the architectures in question will make devirting unnecessary.)
[01:58] <robru> oh good
[01:59] <robru> cjwatson: any ideas here ^ ? should I retry those?
[02:35] <robru> good god
[02:35] <robru> 8-hour oxide build.
[06:51] <robru> Failed to upload? wat
[09:17] <cjwatson> robru: sounds like https://bugs.launchpad.net/bugs/1535949.  I think everything has been retried, but I'll go through and double-check in a bit
[09:18] <Laney> I guess not things in silos?
[09:18] <robru> cjwatson: looks like just the one: https://requests.ci-train.ubuntu.com/#/tickets?status=Failed%20to%20upload
[09:19] <cjwatson> Laney: right, possibly not, depends how Martin did the retries
[09:19] <robru> cjwatson: but a few ones mysteriously cancelled: https://requests.ci-train.ubuntu.com/#/tickets?status=Cancelled
[09:19] <cjwatson> robru: but also cancelled builds
[09:19] <cjwatson> robru: the bug caused builds to loop indefinitely so they had to be cancelled
[09:19] <cjwatson> that's a manual action by somebody, but in this case it makes sense as a consequence of that
[09:19] <robru> cjwatson: yeah I saw the logs looping, was definitely stuck
[09:20] <Laney> train question
[09:20] <Laney> I accidentally built a silo for x + v instead of just x
[09:20] <Laney> can I just change that field and ignore the borked builds?
[09:20] <robru> Laney: you can change that field and then manually delete the vivid builds from the silo
[09:21] <Laney> K, thanks robru
[09:21] <robru> Laney: you're welcome
[09:21] <robru> alright, early meeting tomorrow, goodnight!
[10:03] <sil2100> jibel: rootfs for the rc re-spin has built, importing it now
[10:03] <sil2100> Confirmed the manifest is sane
[10:03] <jibel> sil2100, good thanks
[10:04] <sil2100> Although... I noticed that it pulled in a newer liblibertine1, I had no idea we shipped this library in our touch images
[10:04] <sil2100> ubuntu-pd probably has all the libertine packages while touch only this one, but still - anyway, this is a no-problem for touch POV
[10:08] <jibel> sil2100, content-hub depends on it
[10:10] <sil2100> Oh, and if you don't mind, the new image won't be tagged - I would have to tag all the images manually after importing, wasting time, while we'll have a re-spin with language-packs anyway
[10:10] <jibel> it's fine
[10:57] <cjwatson> robru: all cleaned up now
[11:08] <rvr> jhodapp: ping
[11:08] <jhodapp> rvr, pong
[11:08] <rvr> jhodapp: Hi
[11:08] <jhodapp> rvr, hey there
[11:08] <rvr> jhodapp: I'm failing silo 5
[11:08] <rvr> jhodapp: Test 18: FAIL (music stops).
[11:09] <rvr> It does not happen without silo packages
[11:10] <jhodapp> rvr, that's odd, but it has nothing to do with playback...the changes only affect being able to start to play a media file
[11:10] <jhodapp> rvr, but will double check
[11:11] <jhodapp> rvr, oh, that's a new test...you don't have the fix for test #18 yet
[11:11] <jhodapp> that's the issue
[11:11] <jhodapp> rvr, the fix comes with the new music-app
[11:12] <rvr> jhodapp: Ah
[11:13] <jhodapp> rvr, that was this bug that I proved was music-app's fault last Friday: https://bugs.launchpad.net/ubuntu-rtm/+source/media-hub/+bug/1534172
[11:13] <sil2100> jibel: all imported it seems!
[11:15] <rvr> jhodapp: I see. Ok, then I will do some more tests before approving the silo.
[11:17] <sil2100> morphis: hey!
[11:18] <sil2100> morphis: I've been looking at LP: #1534193 a bit last week and I noticed xenial has horribly outdated android packages
[11:19] <jhodapp> rvr, thanks!
[11:20] <sil2100> morphis: maybe not horribly... I'm not really 100% familiar with how the android versioning works, but it's clear that the xenial version is based off some much earlier time (20150818)
[11:22] <sil2100> morphis: anyway, the truth is that the last real android upload to xenial was last year - are there any reasons the touch changes from overlay can't be pushed to xenial?
[11:38] <sil2100> cyphermox: hey!
[11:39] <sil2100> cyphermox: I was looking at the overlay -> xenial delta (LP: #1534193) and noticed that mtp is outdated in xenial - would it be possible to  get that synced up there?
[12:02] <Mirv> sil2100: when will OTA-10 gates open?
[12:04] <sil2100> Mirv: they're open since a while!
[12:05] <sil2100> Mirv: they're basically open since Monday lateish
[12:05] <sil2100> rc-proposed landings are normal
[12:05] <Mirv> sil2100: yeah I thought that might be the answer but since I saw other assumptions I decided to ask neutrally! :) thanks!
[12:16] <sil2100> Mirv: yw! We have a snapshot for OTA-9 made so all is good
[12:43] <rvr> jhodapp: Plug in a pair of headphones, then unplug - video playback should pause -> Video does not pause
[13:18] <jhodapp> rvr, are you sure it's this silo's fault? should have nothing to do with that
[13:59] <morphis> sil2100: oh yeah, we need to bring those in line
[14:18] <rvr> jhodapp: Weird, I reflashed and  reinstalled the silo and cannot reproduce the problem, anymore.
[14:18] <jhodapp> rvr, that's what I would expect, that sounded fishy
[14:19] <rvr> jhodapp: Approving the silo
[14:20] <jhodapp> rvr, thank you sir
[14:49] <bschaefer> trainguards, i need to be added the group to request a silo on bileto to do a mir release
[14:49] <sil2100> bschaefer: hey! Let me do that
[14:49] <bschaefer> thanks!
[14:51] <sil2100> bschaefer: done! You should be good, re-log in bileto and be sure to tick the ci-train-users team
[14:51] <bschaefer> sil2100, cool let me check
[14:51] <bschaefer> works, yay, thanks!
[14:55] <sil2100> yw!
[15:48] <xavigarcia> Mirv: ping
[15:52] <xavigarcia> Mirv: Just wanted to ask you about bug 1485522... Is the QML component fix ready in vivid overlay? If not... could we create a silo including the fix so I can test if it makes the sound indicator work OK?
[16:01] <Mirv> xavigarcia: I'm not aware of a QML component fix that could be shipped. the one mentioned in #5 is in the 5.4.1 we're using, and there is no mention of other possible fixes.
[16:01] <Mirv> I also didn't get a reply to my Dec 16th upstream contact
[16:05] <xavigarcia> Mirv: Okay.. so it means we have to wait for a response, right?
[16:05] <Mirv> xavigarcia: yes or if David or someone else on our side can come up with a solution
[16:05] <xavigarcia> Mirv: or do you think there is something else we can look at?
[16:05] <xavigarcia> Mirv: I see
[16:06] <xavigarcia> Mirv: Thanks!
[16:06] <Mirv> xavigarcia: ie diwic or jhodapp, diwic seems the most "inside" the problem.
[16:06] <Mirv> no problem
[19:26] <sil2100> jibel: hey, do you know if the required trust-store translations are in?
[19:27] <sil2100> jibel: we had the auto-uploads of langpacks today, I'm wondering if we should kick another one or are those enough to copy to rc
[19:27] <jibel> sil2100, let me check
[19:28] <sil2100> jibel: es looks fine from LP POV
[19:28] <sil2100> Since the translations were added on the 18th
[19:30] <jibel> sil2100, I checked language-pack-touch-fr and the right strings are in the langpack with the correct translation
[19:31] <jibel> in the .deb
[19:32] <jibel> spanish is fine too
[19:33] <sil2100> I suppose we might do the copy then
[19:33] <jibel> and chinese
[19:33] <jibel> sil2100, yeah go ahead
[19:33] <pmcgowan> jibel, whats the latest
[19:34] <sil2100> I wouldn't want to do those like *right now* since I don't like fixing things late at night, but tomorrow morning I'll copy and rebuild
[19:36] <pmcgowan> oh mn music-app never landed
[19:37] <jibel> pmcgowan, the regression with the content hub is concerning, it may hide more than just a problme with the camera, kenvandine and Kaleo are on it. otherwise nothing we don't already know
[19:37] <jibel> yeah and music app and IAP didn't land
[19:37] <pmcgowan> I wonder if the music app export issue is content hub also?
[19:37] <ahayzen> music-app is waiting for OTA9 to be released ? it is otherwise ready (ignoring a flaky jenkins issue)
[19:38] <kenvandine> pmcgowan, shouldn't be
[19:38] <ahayzen> pmcgowan, that was fixed, it was something missed when updating to the new listitems
[19:38] <pmcgowan> ahayzen, ok, and alesage is aware?
[19:38] <kenvandine> the content-hub issue isn't a regression in content-hub, we're thinking maybe qtmir
[19:38] <jibel> ahayzen, it can be published to the store, there is a bump of the version of the framework and users of pre-OTA9 won't see the update
[19:38] <ahayzen> pmcgowan, i told him we had fixed all the issues he had found
[19:38] <pmcgowan> great news
[19:38] <ahayzen> jibel, the branch isn't top approved yet, and if we pushed then it would disappear from the store for stable users
[19:39] <ahayzen> so i'd rather wait until post ota9
[19:39] <sil2100> ahayzen: I suppose we can publish, we checked yesterday that new users won't be able to install it on their stable phones
[19:39] <sil2100> Oh
[19:39] <jibel> alesage, ^ music app is good to land from your perspective?
[19:39] <sil2100> It would?
[19:39] <sil2100> Ah
[19:39] <ahayzen> jibel, it would probably need to go through QA again right?
[19:39] <alesage> jibel, we should give it a glance, yes?
[19:39] <alesage> ahayzen, is there a new build?
[19:40] <ahayzen> sil2100, other people were reporting that when they were putting apps with the new framework into the store, it disappears from the store for say OTA8.5 users?
[19:40] <jibel> pff
[19:40] <jibel> really that's bad
[19:40] <sil2100> Yeah, I guess we had this thing once
[19:41] <sil2100> Forgot about it, the store is really really broken
[19:41] <pmcgowan> well thats a feature :)
[19:41] <ahayzen> alesage, there isn't a new build, as we were trying to fix a jenkins issue, but i've found that that affects weather aswell, so looks like it is a flaky sdk helper in autopilot. We should get the branch landed and then check with popey then hand over a new click to test :-)
[19:41] <pmcgowan> probably lots of apps wanting to use 1.3 components
[19:41] <jibel> bad features exist too ;)
[19:42]  * ahayzen waits for the day of the beta-store
[19:42] <pmcgowan> I blame beuno but hes not here
[19:42] <alesage> ahayzen, ack, I'll assume we'll use the normal process unless jibel says otherwise, feel free to badger me then
[19:43] <jibel> alesage, that's fine we'll retest it since it cannot be published before the release anyway
[19:43] <alesage> jibel, ack very well
[20:34] <mterry> robru, did you lose github.com/robru?
[20:34] <robru> mterry: yeah I deleted it a while ago. why, did somebody take it?
[20:34] <mterry> robru, looks like it
[20:34] <mterry> robru, did you move somewhere else or just not need those branches anymore?
[20:35] <robru> lol
[20:35] <robru> mterry: I moved everything into launchpad.
[20:35] <robru> mterry: my only notable thing was gottengeography anyway
[20:35] <robru> mterry: you spying on me?! ;-)
[20:36] <robru> mterry: https://code.launchpad.net/~robru/+git
[20:37] <mterry> robru, no I just had a bookmark to your dotfiles branch and I noticed it recently and thought "I wonder what's in there now?"
[20:37] <robru> hah, wow. i honestly thought nobody ever looked at those
[20:38] <mterry> robru, first time in a long time  :)  But nice to know that I have a bunch of aliases to steal if I get bored of mine  :)
[20:39] <robru> mterry: one thing you might find interesting is https://git.launchpad.net/~robru/+git/pad which is a wrapper around bzr to automate some lp interactions (basically it makes some assumptions about your filesystem in order to save you typing, so 'bzr branch' becomes shorthand for 'bzr branch $(basename $PWD)' and a few other goodies.