=== chihchun_afk is now known as chihchun === alf is now known as alf_ [09:31] Hang on a sec, be in hangout in a minute [10:46] 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 === duflu_ is now known as duflu [10:46] duflu, ack [10:46] Once we've proven the problem is gone in devices running 0.10 it will be clear [10:48] 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] duflu, 0.8.1 is already up for QA validation [10:49] Saviq: Easy decision then. Which rev? [10:50] ok this is going to be mayhem [10:50] I knew we should not have released lp:mir/0.8 into rtm :| [10:50] duflu, 1965 + lp:~mir-team/mir/backport-1355173.trust-prompt-suspend [10:51] Saviq: Kay. That's landed at r1966 BTW [10:51] yeah, that's why I don't know what will happen [10:51] because the train merged it as a different rev [10:51] most probably conflicts will happen [10:51] Saviq: I doubt it's a problem. Nothing else has landed on that branch in months [10:52] 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] and I expect it will fail to do so due to the new commit on top [10:52] although maybe it will reconcile first, we'll see [10:53] but that's exactly why I wanted to have a separate branch for releases, one that no one pushes to manually [10:54] Saviq: RTM packaging is a different branch: lp:~mir-team/mir/14.09 [10:55] Although I fully expect the train madness to ignore that fact :) [10:55] Merging will happen cleanly either way. Bzr knows when the same source branch already landed. [10:56] 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] Saviq: Never mind. They both end up in sync later. We can clarify configs another day [10:56] 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] duflu, yup [10:57] * duflu wishes more people remembered the difference between upstream and distro branches [10:57] More robots I mean? === dandrader is now known as dandrader|bbl === alan_g is now known as alan_g|lunch === alan_g|lunch is now known as alan_g === dandrader|bbl is now known as dandrader [14:18] 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] alan_g: no [14:20] I've just asked [14:20] 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] :) [14:58] * anpok_ wishes we infinite display space and no need for multiple monitors [15:00] 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 === dandrader is now known as dandrader|afk === dandrader|afk is now known as dandrader === alan_g is now known as alan_g|EOD === popey_ is now known as popey