[00:50] Looking for a MOTU or core-dev to help publish a silo, anyone around? [00:51] Specifically: https://requests.ci-train.ubuntu.com/#/ticket/1292 === salem_ is now known as _salem [05:04] tedg: publishing === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun [08:28] oSoMoN, dbarth_: hey guys! How's work on https://requests.ci-train.ubuntu.com/#/ticket/1286 going? [08:29] sil2100, I’m validating it again as I write, hopefully that build is the last one [08:44] sil2100: same for webapps [08:51] Excellent, thanks! === chihchun is now known as chihchun_afk [09:09] 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] oSoMoN, dbarth_: are there any other changes in the new oxide besides the fix for the emulator? [09:10] sil2100: a fix for the regression [09:10] sil2100, yes, it’s a new version of oxide (1.13 -> 1.14) [09:11] sil2100: here: https://bugs.launchpad.net/oxide/1.14/+bugs [09:11] Ubuntu bug 1 in Ubuntu Malaysia LoCo Team "Microsoft has a majority market share" [Critical,In progress] [09:11] the critical one [09:11] Ouch, that might be a bit complicating stuff [09:11] sil2100, see https://bazaar.launchpad.net/~oxide-developers/oxide/packaging.xenial/view/head:/debian/changelog [09:12] sil2100, sure we could release the emulator only === chihchun_afk is now known as chihchun [09:21] sil2100, Hi! can you tell when does a .click package gets into the image ? [09:21] there was a release of dekko last week and its still not in the image, or am I missing something ? [09:22] om26er: hey! [09:22] om26er: so it's a bit complicated as most of our clicks are shipped with our images through custom tarballs [09:22] So as long as no new device tarball was published, the new versions won't be pre-installed [09:23] *device=custom [09:23] sil2100, how can I request a new tarball ? [09:24] 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] I could also prepare one, but I have no idea if they don't have any other changes staged [09:24] You can find penk on our internal channels, he's on a Chinese timezone [09:26] (or by e-mail) [09:26] sil2100, hmm, sounds complicated. Will talk to penk === seb128_ is now known as seb128 === chihchun is now known as chihchun_afk [10:34] sil2100: i just marked silo 38 approved again, ie the newest oxide build [10:41] \o/ === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [11:00] 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] pstolowski, no problem. I removed the card another one will be created when it is ready for testing again === _salem is now known as salem_ [14:32] ChrisTownsend: Silo 80 approved [14:40] rvr, Hi, once again, I'm here if you have any questions about uNav :) [14:59] nik90: Ack :) === chihchun_afk is now known as chihchun [17:22] sil2100: hey what's the plan for dual silos? I'm around to flip the switch to yakkity if you need [17:32] sil2100: https://code.launchpad.net/~robru/bileto/yakkity/+merge/292991 [17:48] sil2100: what's the plan for duals? steve says it's not as simple as just s/xenial+/yakkety+/ [17:48] sil2100: I've undone the change where the primary series of a dual silo is targetted at overlay ppa at least. [17:49] triples! === alesage_ is now known as alesage [18:02] dobey: for real? seems nobody is around [18:03] robru: yes. i don't see why it shouldn't be possible to do a triple landing [18:04] 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] 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] 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] dobey: I mean the developers are required to ensure that their builds work in both xenial & vivid before sending to qa. [18:07] as long as we have to support vivid-overlay anyway [18:07] robru: well, "work" [18:07] robru: there's no way to ensure stuff works when the phone won't boot [18:08] 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] robru: well it's not entirely untested, and certainly not garbage [18:10] 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] if only via unit/integration/autopilot tests [19:22] that doesn't look right [19:34] fun [19:35] I'm just guessing, but the fringe-area localizer has stopped meshing with the grapple grommet somewhere? [19:36] perhaps the Filbert flange is out of quarter? [19:37] try reversing the polarity of the neutron flow across the flux capacitor [19:39] oh joy... train wreck [19:39] maybe just try turning it off and back on again? [19:39] :) [19:39] bregma, but i'm not from IT [19:39] lol [20:37] Oh jeez [20:37] I'm here [20:40] ok I have a fix on trunk, should hit prod within an hour [20:40] dobey: bregma: kenvandine: ^ [20:42] my bad guys, sorry [20:53] :) === salem_ is now known as _salem [21:21] robru, thx [21:21] kenvandine: yw [21:21] yay... it's working :) === chihchun is now known as chihchun_afk [22:13] robru: could you rebuild indicator-datetime for i386 on silo 9 please? [22:20] bfiller: done [22:20] robru: thank you [22:21] bfiller: you're welcome === blr_ is now known as blr