=== chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === hikiko is now known as hikiko|off [06:43] RAOF: When would you estimate the majority of transitions to yakkety would finish? [06:43] What do you mean? [06:44] RAOF: I mean when do you reckon the floor and mountains would stop moving [06:44] Oh, roughly now. [06:44] Hmm, OK. Might switch soon [06:45] Oh, I don't think gcc-6 is default yet. That's the last piece of outstanding foundation change I know of. [06:45] Sounds like a big one [06:45] Usually is [06:46] Well, mir already builds with it :) [06:46] Cool, but we also depend on a whole archive that needs to work too [06:47] Well, my laptop is fine with it (at the moment). [06:47] The everything-stages-in-proposed switch has shaved *a lot* of the sharp edges off the development release. [06:48] Yeah I can put it on a laptop any time. But if my main work dev machine stops working, that's a problem [06:49] RAOF: What's that? We just use proposed more now? [06:49] Or use it properly [06:50] Every upload gets diverted to proposed, and only migrates when (a) the migration does not break installability, and (b) all autopkgtests pass. [06:50] Awesome [06:51] This is why having a autopkgtests for Mir would be valuable; every mesa upload would sit in proposed until the Mir autopkgtests completed successfully. [06:51] Except I'm sitting on an installability regression that's a major pain [06:51] Which we don't test for [06:52] By “installability” I mean “every package in the archive can be installed”, not “can be installed on a PC with a new nvidia card ☺”. [06:52] Ooh [06:52] RAOF: I meant https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1546641 [06:52] Ubuntu bug 1546641 in unity-settings-daemon (Ubuntu Yakkety) "unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()" [Critical,Triaged] [06:53] Which admittedly is not installability as much as acceptability [06:54] Indeed. [06:55] Also, isn't a bug in the development branch, but in the release :). [06:55] It was in development, before it got released :) [06:55] Two months before [06:55] Right, but this is less a question about yakkety. [06:56] * duflu continues searching for unofficial EGL extensions === w00t_ is now known as w00t === davmor2_ is now known as davmor2 === alan_g is now known as alan_g|afk === marcusto_ is now known as marcustomlinson === chihchun is now known as chihchun_afk [11:27] alf__, are you back today? [11:28] kdub: yes [11:28] alf__, welcome back [11:28] kdub: thanks! [11:29] alf__, just wanted to point out https://bugs.launchpad.net/mir/+bug/1577357, wondering if you remember anything about that bug/workaround where we try to force mir_demo_server to link to pthread [11:29] Ubuntu bug 1577357 in Mir 0.23 "package-built mir_demo_server does not start on device" [High,New] [11:30] * kdub will keep chipping at it after i've got 1578159 squared away [11:31] probably would be nice to have in 0.23 if its simple (my experiments with it monday werent sucessful though) [11:32] so if its not, we'll just tag to 0.24 === alan_g|afk is now known as alan_g [11:43] kdub: The original issue was seen only when cross-compiling with clang+ld.gold (IIRC). The packaged binaries are built with gcc+ld.bfd, right? [11:44] yes, they should be [11:45] kdub: In any case, it's very strange that the executable doesn't link with pthread even though we have the work around (i.e. explicitly use pthread symbols) [11:45] right, and I've traced through enough to see that -pthread is there in the options === chihchun_afk is now known as chihchun === dandrader is now known as dandrader|lunch === dandrader|lunch is now known as dandrader === charles_ is now known as charles === alan_g is now known as alan_g|EOD === chihchun_afk is now known as chihchun