[12:37] <shadeslayer> stgraber: btw can you set multiple jobs for sbuild?
[12:38] <shadeslayer> ( and for the stuff you wrote )
[12:45] <cjwatson> It has a -j option if that's what you mean
[12:45] <cjwatson> Right there in its man page
[13:53] <shadeslayer> cjwatson: thx
[19:56] <Noskcaj> I the opinion of you guys, have i done enough (quality) work to apply for MOTU?
[19:58] <tumbleweed> Noskcaj: we generally want to see 6 months of sustained contribution
[19:58] <Noskcaj> ok, so not quite
[19:59] <tumbleweed> but almost - it does look like you've done quite a lot
[19:59] <tumbleweed> so start preparing an application, and ask your sponsors for endosement
[19:59] <Noskcaj> ok, thanks for the help
[20:00] <tumbleweed> Noskcaj: just looking at your uploads, what's up with qtiplot?
[20:00]  * Noskcaj checks
[20:01] <tumbleweed> it never built successfully
[20:04] <Logan_> It looks like infinity copied that over from Debian, no?
[20:05] <tumbleweed> Logan_: no, you did, sponsoring Noskcaj
[20:05] <Logan_> Oh my b.
[20:05] <Logan_> I knew it sounded familiar.
[20:05] <tumbleweed> :)
[20:07] <Logan_> http://bugs.debian.org/728642 <-- The FTBFS is reported in Debian. Hopefully they'll fix it soon.
[20:07] <tumbleweed> did neither of you test build it? :)
[20:08]  * tumbleweed sees a few other merges of Noskcaj's that failed to build (but were trivially fixed)
[20:08] <Noskcaj> For quite some time, i went off debian changelog only for syncs especially
[20:08] <Logan_> I trusted Noskcaj, although he said in the bug that he only tested it on a Debian chroot.
[20:08] <Logan_> I've been more careful with checking syncs locally. :P
[20:09] <tumbleweed> it's generally a good idea to test (if you have the bandwith)
[20:09] <Noskcaj> My internet is very, very bad. I've only just got the buildlog for qtiplot open
[20:09] <tumbleweed> esp because you won't get email notification for syncs that fail to build
[20:09] <Logan_> I honestly have no excuse with 80 down. So yeah, I take the blame.
[20:10] <Logan_> But it should be fixed soon in Debian, hopefully.
[20:10] <tumbleweed> yup. all's well that ends well
[20:10] <Logan_> Especially since the FTBFS is now affecting sid as well.
[20:31] <Logan_> Can anyone help me figure out why wmaker isn't going from proposed to release?
[20:31] <Logan_> I rebuilt wdm, but that doesn't appear to be enough...
[20:32] <Logan_> Oh nvm, I see.
[20:33] <tumbleweed> Logan_: fookb?
[20:33] <Logan_> Yep.
[20:33] <Logan_> Thanks. :P
[20:33] <Logan_> Weird how arm64 is the only one though.
[20:34] <tumbleweed> arm64 is new, so it has more recent builds of many packages than other archs
[20:34] <tumbleweed> which means they could have built against different libraries
[20:34] <Logan_> ...true. Gotcha.
[20:37] <tumbleweed> still, I don't know what the problem is, here
[20:38] <Logan_> Wassup?
[21:00] <ScottK> Also the current arm64 builders are unreliable.  Often just retrying a package solves a build failure.
[21:17] <Unit193> Just a note, pepperflashplugin-nonfree won't work as designed if you sync it, but a patch such as http://paste.openstack.org/show/aeiBkrJYNAvZws9mDL39/ may help.
[21:26] <tumbleweed> Logan_: I mean, I looked in an arm64 chroot, and it seemed perfectly installable
[21:27] <Logan_> Yes, but building on arm64 brought in the wutil dependency. As did rebuilding on all archs. Needed to rebuild to finish the transition.
[21:29] <tumbleweed> I don't see what the problem was, though