[01:45] <duflu> Hmm, that new libinput released 45min ago in xenial looks interesting. I wonder what it fixed
[06:36] <camako> RAOF
[06:36] <RAOF> Yo!
[06:36] <camako> around?
[06:36] <camako> oh cool.. Hey I'm trying to publish mir 0.19
[06:36] <camako> it needs a core dev ack for packaging changes
[06:37] <RAOF> Throw me the link!
[06:37] <camako> RAOF, could you lend me a hand?
[06:37] <camako> RAOF, this is the silo : https://requests.ci-train.ubuntu.com/#/ticket/901
[06:37] <camako> not sure where the link is
[06:39] <RAOF> Bah.
[06:40] <RAOF> Hm. I think you actually need an archive admin, because we've introduced new packages (and they'll need to be promoted to main)
[06:42] <camako> RAOF, umm this link has "ack packagin changes" option... https://ci-train.ubuntu.com/job/ubuntu-landing-010-2-publish/build
[06:42] <RAOF> Oh, wow! Where did you find that!
[06:42] <camako> :-)
[06:42] <RAOF> We shouldn't be retrospectively changing changelog entries, but the changes are purely formatting, so aren't terrible.
[06:43] <camako> I don't know if whoever is clicking needs to have admin/core-dev priviliges though
[06:44] <RAOF> Well, I've got those privileges.
[06:44] <RAOF> (But shouldn't use the AA privileges ☺)
[06:44] <RAOF> Well, I've acked the packaging changes.
[06:45] <camako> RAOF, where did you do that?
[06:45] <RAOF> I pressed that button :)
[06:45] <camako> lol makes sense
[06:46] <camako> RAOF, did you press 'build' too? Make sure you're logged in first.
[06:46] <RAOF> I did press build.
[06:47] <RAOF> And then I pressed build again, and it did something else.
[06:47] <RAOF> BONZA!
[06:47] <camako> ah ok I see it
[06:47] <camako> yeap uploading
[06:49] <camako> ... aaand success! thanks RAOF
[06:49] <RAOF> Win!
[08:34] <zzarr> hello duflu :-D
[08:35] <core_t> !seen 0.19
[08:35] <core_t> :'(
[08:36] <zzarr> core_t, what should that command have done?
[08:36] <core_t> zzarr, release mir 0.19
[08:36] <core_t> :D
[08:39] <core_t> hm... Version 0.19.0+16.04.20160128-0ubuntu1 uploaded 20 hours ago
[08:39] <zzarr> core_t, I wounder what version of mir I use
[08:39] <zzarr> (on my MX4)
[08:39] <core_t> 0.18.1
[08:39] <core_t> probably
[08:39] <core_t> if you are on stable
[08:41] <duflu> zzarr: Release in progress, not an official update yet. But it has reached proposed: https://launchpad.net/ubuntu/+source/mir
[08:41] <duflu> core_t ^
[08:42] <core_t> thanks duflu :D
[08:42] <duflu> Oh dear. That changelog for 0.19.0 is messy and incomplete. Sorry.
[08:42] <zzarr> core_t, I am on stable
[08:45] <zzarr> duflu, do you have time to take a peak at this link? http://malideveloper.arm.com/resources/drivers/arm-mali-midgard-gpu-user-space-drivers/
[08:46] <duflu> zzarr: Interesting but I'll have to skip it till next week
[08:47] <zzarr> duflu, I'm still thinking about if it is/how it could be possible to get Mir on my Chromebook
[08:48] <zzarr> duflu, okey, no problem, I'm very grateful that you have taken the time you have and that you help me :-D
[08:49] <zzarr> duflu, I think I forgot to tell yesterday, but I do like Mir :-D
[08:49] <duflu> zzarr: Good. We aim to make it likeable.
[08:49] <duflu> Although have some steps to go still.
[08:50] <zzarr> duflu, yes :-)
[08:50] <zzarr> duflu, it's a bit sad that my MX4 can't handle MHL.... but there's nothing to do about it I guess
[10:47] <Saviq> guys, qtmir and qtmir-gles doesn't seem to build in proposed http://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#mir
[11:10] <zzarr> is there a guesstimation when Aethercast will be installable/useful?
[11:14] <anpok_> hm soon-ish
[11:24] <zzarr> like OTA-10?
[11:25] <zzarr> or will it be an app I install?
[11:35] <anpok_> i assume it will be part of the image.. but not sure which OTA.. the frequency of the OTA seemed to have increased these weeks,,
[11:37] <zzarr> anpok_, yes you're right
[11:37] <anpok_> zzarr: you can watch the launchpad bzr repository and look for aethercast test silos .. not sure if there is one currently set up
[11:38] <zzarr> okey, anpok_, thanks
[11:42] <greyback_> hey, I just apt-get updated to mir0.19, and see that I still have old version of mir-client-platform-mesa and  mir-platform-input-evdev
[11:42] <anpok_> hm how did you update
[11:43] <greyback_> apt-get update
[11:43] <greyback_> distupgrade
[11:45] <anpok_> so you did not install the kms7 evdev4 driver packages?
[11:45] <anpok_> do you have mir-graphics-drivers-desktop/android installed?
[11:47] <greyback_> I'm missing mir-graphics-drivers-desktop
[11:47] <anpok_> ok,
[11:47] <anpok_> then it has no package to upgrade that depends on the new packages..
[11:47] <greyback_> yeah, that pulls the newer drivers in
[11:48] <greyback_> I wasn't aware of that package existing
[11:48] <greyback_> cool, thanks
[11:48] <anpok_> maybe we should have a recommends for those?
[12:01] <alan_g> anpok_: AIUI that would end up pulling the mesa stack onto the phone in some scenarios
[12:02] <anpok_> hm.. then this will our "did you try turning it off and on again"
[12:02] <anpok_> +be
[12:03] <alan_g> We ought to be able to do better, but debian packaging incantations are not my thing#
[12:26] <greyback_> most likely, best solution when the time comes is for ubuntu-desktop to depend on mir-graphics-drivers-desktop
[12:27] <greyback_> assuming we will distinguish touch and destop in future...
[12:29]  * alan_g thinks "desktop" is a bad name - it really means mesa-kms && mesa-X11, if we ever have another "desktop" stack, or a non-desktop "mesa" (dragonboard anyone?) it gets confusing
[12:32] <anpok_> yes.. as soon as we get proper egl backend loading in mesa pulling both drivers might not be such a big issue
[12:38] <alan_g> I'm sure we discussed that around March '15 - it is almost a year later
[12:38] <anpok_> yip
[12:47] <zzarr> I long for Aethercast :-)
[14:07] <alf> Saviq: Hi! Is ccache working for you in unity8 jenkins?
[14:08] <alf> Saviq: In Mir (using your scripts) it gets called when building, but it seems to have no positive effect. Could it be that it doesn't recognize the files because of different file paths?
[15:05] <camako> Saviq, @qtmir build failure, we build this so many times before publishing. Why is it failing now? was there another landing?
[15:05]  * camako checks
[15:06] <Saviq> camako, britney behaviour change, qtmir's autopkgtest is wrong in that scenario as it's trying to build old qtmir against new mir :/
[15:07] <camako> Saviq, ok so I talk to ci guys?
[15:08] <Saviq> camako, #ubuntu-devel rather, infinity's been helping, but it looks like we might need to force it through unless they've a way to re-run with qtmir source from proposed
[15:08] <Saviq> /source/d
[15:10] <camako> Saviq, ok thanks for chasing
[15:16] <Saviq> camako, I'm going into flight mode, so you might want to follow up on #ubuntu-devel
[15:17] <camako> Saviq, thanks
[15:51] <kdub> i've somewhat convinced myself that
[15:51] <kdub> we need a MirBufferContext for the new semantics
[15:51] <kdub> instead of mincing the MirBufferStream to do the new and old jobs
[15:52] <kdub> internally, its a mess to mince it thusly :)
[15:52] <kdub> a manually controlled api isnt really a stream
[17:31] <MoPac> Hello -- On login to a Unity8-desktop-session-mir session (liveUSB of latest/updated 16.04), I'm getting a segfault in libmirclient.so.9 (system crash, session never loads, have to restart lightdm). I wanted to raise it here before I reported it as a bug in case it's not really meant to work on a liveUSB like that...
[17:32] <MoPac> The dmesg line is "system-crash-no[17587]: segfault at 0 ip 00007f7ed7cc500f sp 00007ffc17d965b0 error 4 in libmirclient.so.9[7f7ed7c72000+8c000]"
[17:34] <alan_g> MoPac: does this help? https://bugs.launchpad.net/mir/+bug/1526658/comments/17
[17:38] <MoPac> alan_g: "unable to locate" either of those packages
[17:39] <MoPac> But I did have a mesa3 and mesa4 -- removing those and retrying
[17:40] <alan_g> MoPac: Try removing all but the latest. You'll need the latest of them
[17:40] <MoPac> I'm trying with just -dev ... I'll then try with just 4