[09:31] <duflu_> Hang on a sec, be in hangout in a minute
[10:46] <duflu_> Saviq: That heap corruption bug I don't think I'll try to push for 0.8.1. It's unclear if it's really resolved or if we're getting false duplicates from another bug with the same Stacktrace signature confusing errors.ubuntu.com
[10:46] <Saviq> duflu, ack
[10:46] <duflu> Once we've proven the problem is gone in devices running 0.10 it will be clear
[10:48] <duflu> Saviq: Hmm, although if we pushed the fix for the first one to 0.8.1 that might be enough. Cos the second similar crash only got introduced in 0.9
[10:48]  * duflu proposes for someone else to decide
[10:48] <Saviq> duflu, 0.8.1 is already up for QA validation
[10:49] <duflu> Saviq: Easy decision then. Which rev?
[10:50] <Saviq> ok this is going to be mayhem
[10:50] <Saviq> I knew we should not have released lp:mir/0.8 into rtm :|
[10:50] <Saviq> duflu, 1965 + lp:~mir-team/mir/backport-1355173.trust-prompt-suspend
[10:51] <duflu> Saviq: Kay. That's landed at r1966 BTW
[10:51] <Saviq> yeah, that's why I don't know what will happen
[10:51] <Saviq> because the train merged it as a different rev
[10:51] <Saviq> most probably conflicts will happen
[10:51] <duflu> Saviq: I doubt it's a problem. Nothing else has landed on that branch in months
[10:52] <Saviq> duflu, probably not a *problem*, but the train will complain anyway, as it will try to push 1965 + backport that it merged itself to lp:mir/0.8
[10:52] <Saviq> and I expect it will fail to do so due to the new commit on top
[10:52] <Saviq> although maybe it will reconcile first, we'll see
[10:53] <Saviq> but that's exactly why I wanted to have a separate branch for releases, one that no one pushes to manually
[10:54] <duflu> Saviq: RTM packaging is a different branch: lp:~mir-team/mir/14.09
[10:55] <duflu> Although I fully expect the train madness to ignore that fact :)
[10:55] <duflu> Merging will happen cleanly either way. Bzr knows when the same source branch already landed.
[10:56] <Saviq> duflu, well, camako seems to not have known about the 14.09 branch, so the MP that is in the train is the above backport
[10:56] <duflu> Saviq: Never mind. They both end up in sync later. We can clarify configs another day
[10:56] <Saviq> duflu, it's not what the train ignores, really, it's rather that the MP was against lp:mir/0.8 and not the rtm branch
[10:56] <Saviq> duflu, yup
[10:57]  * duflu wishes more people remembered the difference between upstream and distro branches
[10:57] <duflu> More robots I mean?
[14:18] <alan_g> alf: have you asked CI eng to look at the repeated failures on https://jenkins.qa.ubuntu.com/job/mir-vivid-amd64-autolanding/?
[14:19] <alf> alan_g: no
[14:20] <alan_g> I've just asked
[14:20] <alf> alan_g: thanks, just joined channel
[14:42]  * kdub wishes android had thought out their multimonitor stuff better
[14:53]  * alan_g wishes Mir had thought out their multimonitor stuff better
[14:56]  * davmor2 wishes anyone had thought about multimonitor stuff full stop
[14:57] <kdub> :)
[14:58]  * anpok_ wishes we infinite display space and no need for multiple monitors
[15:00] <davmor2> anpok_: that's easy buy one of these http://www.samsung.com/uk/consumer/tv-audio-video/televisions/curved-tvs/UE78HU8500TXXU and use it as a monitor