[00:08] <micahg> flexiondotorg: he's off today, but to answer your question, yes, the idea is that the upload will close the bug that's tracking the upload
[04:47] <tjaalton> infinity: ping lts-vivid
[08:00] <infinity> tjaalton: Working on it today.  First day back from VAC.
[08:01] <tjaalton> infinity: ah ok, nice
[14:28] <tedg> infinity, Did you figure out where that lib comes from? No one I pinged on the Mir side got back to me, but I can try some more.
[14:42] <RAOF> tedg, infinity: Those “libraries” are sourceless; they're empty.
[14:45] <RAOF> tedg, infinity: Their job is to be the minimum possible valid ELF libraries for various architectures, so we can test that our loader paths (a) report appropriate errors, and (b) will actually load a library.
[14:45] <tedg> RAOF, Then are they built by hand? How do you get that?
[14:53] <RAOF> tedg: Yeah, they were built by hand. The reason for this is that they're test data, and we *want* to try to load libarm64.so on i386.
[14:53] <RAOF> I... actually forget how we built them :)
[14:54] <RAOF> The shared library prober tests actually have a list of expected architectures.
[14:54] <tedg> RAOF, So infinity's issue is that he wants to build one for PPC
[14:54] <RAOF> Yeah.
[14:56] <RAOF> tedg: “touch foo.cpp; gcc -o foo.so -shared foo.cpp” is the way to generate them.
[14:57] <tedg> RAOF, Probably should be a shell script, eh?
[14:57] <RAOF> Possibly.
[14:57] <RAOF> It can't be run during Mir build, though, because we won't have all of {i386, x86_64, armhf, arm64, powerpc, ppc64, ppc64el} compilers :)
[14:58] <tedg> Sure, but if we add arm128 we'll need someone to remember how to do it :-)
[14:58] <tedg> At least a README
[14:59] <RAOF> Also, the shared library tests need to do something a bit more interesting, because we encode a list of architectures we expect in there.
[14:59] <RAOF> Please file a Mir bug about that :)
[15:00] <tedg> RAOF, So I think that infinity is probably working towards an MR with the PPC lib in it, what would be preferred as a MR reviewer?
[15:35] <arges> bdmurray: hi
[15:37] <bdmurray> arges: howdy
[15:38] <arges> bdmurray: hey jamespage was wondering about releasing bug 1443429, i can handle it, but i know today is your day
[15:39] <arges> looking at it, just looks like cinder needs releasing
[15:42] <bdmurray> arges: feel free to do it
[15:44] <arges> bdmurray: ok
[16:27] <RAOF> tedg: He'll need to also adjust the tests, but that'd be fine.
[16:37] <RAOF> infinity, tedg: https://code.launchpad.net/~raof/mir/document-our-random-test-binary-data/+merge/259798
[16:37] <RAOF> Documents how those binaries have arrived.
[16:38] <tedg> RAOF, Awesome, thanks!
[19:41] <infinity> RAOF: I already fixed everything around it, just needed to know how to generate the .so itself.  Thanks.
[20:20] <ChrisTownsend> bdmurray: Hi, are you on SRU duty today?
[20:21] <bdmurray> ChrisTownsend: yes, I am
[20:21] <ChrisTownsend> bdmurray: Great, would you have time to review the Unity SRU in unapproved?
[20:21] <bdmurray> ChrisTownsend: for which release?
[20:22] <ChrisTownsend> bdmurray: Trusty
[20:22] <ChrisTownsend> bdmurray: I added the debdiff to each bug targetted.
[20:23] <bdmurray> ChrisTownsend: I'll look at in a bit I have a call soon
[20:23] <ChrisTownsend> bdmurray: Thank you very much!
[20:23] <ChrisTownsend> bdmurray: debdiff is linked at the end of SRU header section in the description.