[00:50] <tedg> Looking for a MOTU or core-dev to help publish a silo, anyone around?
[00:51] <tedg> Specifically: https://requests.ci-train.ubuntu.com/#/ticket/1292
[05:04] <Mirv> tedg: publishing
[08:28] <sil2100> oSoMoN, dbarth_: hey guys! How's work on https://requests.ci-train.ubuntu.com/#/ticket/1286 going?
[08:29] <oSoMoN> sil2100, I’m validating it again as I write, hopefully that build is the last one
[08:44] <dbarth_>  sil2100: same for webapps
[08:51] <sil2100> Excellent, thanks!
[09:09] <sil2100> jibel: I suppose it would be really cool if we could do a OTA-10.1 re-spin for the emulator with the oxide fix in it
[09:09] <sil2100> oSoMoN, dbarth_: are there any other changes in the new oxide besides the fix for the emulator?
[09:10] <dbarth_> sil2100: a fix for the regression
[09:10] <oSoMoN> sil2100, yes, it’s a new version of oxide (1.13 -> 1.14)
[09:11] <dbarth_> sil2100: here: https://bugs.launchpad.net/oxide/1.14/+bugs
[09:11] <dbarth_> the critical one
[09:11] <sil2100> Ouch, that might be a bit complicating stuff
[09:11] <oSoMoN> sil2100, see https://bazaar.launchpad.net/~oxide-developers/oxide/packaging.xenial/view/head:/debian/changelog
[09:12] <jibel> sil2100, sure we could release the emulator only
[09:21] <om26er> sil2100, Hi! can you tell when does a .click package gets into the image ?
[09:21] <om26er> there was a release of dekko last week and its still not in the image, or am I missing something ?
[09:22] <sil2100> om26er: hey!
[09:22] <sil2100> om26er: so it's a bit complicated as most of our clicks are shipped with our images through custom tarballs
[09:22] <sil2100> So as long as no new device tarball was published, the new versions won't be pre-installed
[09:23] <sil2100> *device=custom
[09:23] <om26er> sil2100, how can I request a new tarball ?
[09:24] <sil2100> om26er: you need to reach out to penk, he's the one currently taking care of those... sadly currently the custom tarball release part is a bit detached from ours
[09:24] <sil2100> I could also prepare one, but I have no idea if they don't have any other changes staged
[09:24] <sil2100> You can find penk on our internal channels, he's on a Chinese timezone
[09:26] <sil2100> (or by e-mail)
[09:26] <om26er> sil2100, hmm, sounds complicated. Will talk to penk
[10:34] <dbarth_> sil2100: i just marked silo 38 approved again, ie the newest oxide build
[10:41] <sil2100> \o/
[11:00] <pstolowski> jibel, qa hello, fyi, since silo 71 is not yet under testing, i'm currently adding a few more MPs to it & rebuilding, so this silo will be ready later today
[11:02] <jibel> pstolowski, no problem. I removed the card another one will be created when it is ready for testing again
[14:32] <rvr> ChrisTownsend: Silo 80 approved
[14:40] <nik90> rvr, Hi, once again, I'm here if you have any questions about uNav :)
[14:59] <rvr> nik90: Ack :)
[17:22] <robru> sil2100: hey what's the plan for dual silos? I'm around to flip the switch to yakkity if you need
[17:32] <robru> sil2100: https://code.launchpad.net/~robru/bileto/yakkity/+merge/292991
[17:48] <robru> sil2100: what's the plan for duals? steve says it's not as simple as just s/xenial+/yakkety+/
[17:48] <robru> sil2100: I've undone the change where the primary series of a dual silo is targetted at overlay ppa at least.
[17:49] <dobey> triples!
[18:02] <robru> dobey: for real? seems nobody is around
[18:03] <dobey> robru: yes. i don't see why it shouldn't be possible to do a triple landing
[18:04] <robru> dobey: obviously it's possible to do a triple landing it's just an insane burden to expect people to validate three different sets of packages on three different releases. (or 6 different sets of packages in the case of GLES stuff)
[18:06] <dobey> robru: what do you mean by validate? it's not like previously we had qa running tests for xenial builds; otherwise i guess the xenial phone images would work
[18:06] <dobey> robru: maybe it's not a good thing for GLES (i don't know for sure), but it's certainly valid for some packages
[18:07] <robru> dobey: I mean the developers are required to ensure that their builds work in both xenial & vivid before sending to qa.
[18:07] <dobey> as long as we have to support vivid-overlay anyway
[18:07] <dobey> robru: well, "work"
[18:07] <dobey> robru: there's no way to ensure stuff works when the phone won't boot
[18:08] <robru> dobey: I don't understand why we bother to have duals at all if people are just dumping untested garbage all over xenial.
[18:08] <dobey> robru: well it's not entirely untested, and certainly not garbage
[18:10] <dobey> we're probably doing more testing than is done for a lot of the stuff that's just copied over from debian unstable
[18:10] <dobey> if only via unit/integration/autopilot tests
[19:22] <bregma> that doesn't look right
[19:34] <dobey> fun
[19:35] <bregma> I'm just guessing, but the fringe-area localizer has stopped meshing with the grapple grommet somewhere?
[19:36] <bregma> perhaps the Filbert flange is out of quarter?
[19:37] <bregma> try reversing the polarity of the neutron flow across the flux capacitor
[19:39] <kenvandine> oh joy... train wreck
[19:39] <bregma> maybe just try turning it off and back on again?
[19:39] <kenvandine> :)
[19:39] <kenvandine> bregma, but i'm not from IT
[19:39] <kenvandine> lol
[20:37] <robru> Oh jeez
[20:37] <robru> I'm here
[20:40] <robru> ok I have a fix on trunk, should hit prod within an hour
[20:40] <robru> dobey: bregma: kenvandine: ^
[20:42] <robru> my bad guys, sorry
[20:53] <bregma> :)
[21:21] <kenvandine> robru, thx
[21:21] <robru> kenvandine: yw
[21:21] <kenvandine> yay... it's working :)
[22:13] <bfiller> robru: could you rebuild indicator-datetime for i386 on silo 9 please?
[22:20] <robru> bfiller: done
[22:20] <bfiller> robru: thank you
[22:21] <robru> bfiller: you're welcome