[00:24] <robert_ancell> RAOF, back?
[05:51]  * conyoo good morning o_O
[12:04] <seb128> seems like the new mir landing in wily is busted, it triggered  bootest regression errors and I installed it on a device and unity8-dash abrt on start
[12:04] <seb128> just letting the channel know
[12:04] <seb128> unsure who is looking after that landing/update
[12:04] <seb128> kgunn, ^
[12:05] <anpok> i am looking at that right now
[12:05] <anpok> I tried mako this morning.. worked as expected
[12:05] <seb128> can you reproduce or do you need info?
[12:05] <anpok> now trying on krillin
[12:05] <seb128> k
[12:09] <seb128> seems also whoever did that landing forgot to rebuild some libmirclient8->libmirclient9 rdepends
[12:09] <seb128> ciborium ubuntu-push-client url-dispatcher
[12:24] <greyback> kdub: hey, so I cross-built your branch locally, copied the mirserver lib to the device, rebooted. All looks ok. But when I plugged in a monitor, hang. Here's a backtrace: http://pastebin.ubuntu.com/11892528/
[12:24] <greyback> kdub: would you prefer I do a proper build & install? Just in case?
[12:24] <anpok> seb128: how did you discover that ciborium depends on libmirclient8?
[12:25] <kdub> greyback, the fix is contained in the graphics-android.so.2
[12:25] <greyback> kdub: gah, ok
[12:26] <seb128> anpok, that's the ones that fail to update with wily-proposed enabled
[12:27] <seb128> anpok, but seems like it's a depends chain and that url-dispatcher is the one that need a rebuild
[12:30] <anpok> seb128: yeah I had an mp for url-dispatcher prepared, just forgot to add it.
[12:37] <greyback> kdub: god news, that seems to have fixed it
[12:37] <greyback> good even
[12:37] <kdub> yay
[12:37] <greyback> nice one
[13:01] <kgunn> seb128: anpok just trying to understand, how did seb128 see bootest regression and we didn't ? i'm kinda hinting, what could we do to avoid in future
[13:18] <seb128> kgunn, I didn't do that in front, I'm just looking at why mir is blocked in proposed (http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt)
[13:18] <seb128> sorry, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[13:34] <kgunn> seb128: ah...i mean not good, but good it got caught in proposed
[13:34] <kgunn> so machinery worked ;)
[13:37] <anpok> hm it would have turned up when somebody tries to remove the old client libraries
[13:53] <dandrader> what's the name of the env var I should use to tell the filepath of the socket file my mir server should use?
[13:55] <dandrader> ok, it's MIR_SERVER_FILE
[16:09] <tedg> Seems like Mir isn't linking to protobuf? https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1475619
[16:09] <tedg> (in wily)
[17:08] <tedg> Added a Mir task