[07:06] <dholbach> good morning
[08:23] <Laney> hey
[08:23] <Laney> tumbleweed: seeded-in-ubuntu seems sad: IOError: [Errno socket error] [Errno 111] Connection refused
[08:39] <wgrant> Laney: Apologies, some maintenance on that host took a bit longer than expected.
[08:39] <wgrant> It's been back for a while now
[08:39] <Laney> Works now
[08:40] <Laney> thanks for the boot
[14:00] <bregma> hey folks, I have a package I want to NEW into universe but I'm confused about the next step to take: I filed an RFP, I have a branch ready and built in a PPA, so what's next?
[14:13] <mfisch> bregma: you need a sponsor, let me get back to you about next steps in 15 mins if thats ok
[14:14] <bregma> I'm nothing if not patient
[14:14] <Laney> I assume it can't go to Debian?
[14:16] <bregma> someone else has got a Debian ITP, but he's not likely to find a sponsor there, he hasn't been in contact with upstream, he hasn;t responded to my queries, and I'm aiming to get this particular package in early in the Trusty cycle with an eye to getting it in main
[14:17] <bregma> if and when it gets into Debian, we can start synching then
[14:20] <dholbach> jtaylor, not sure if you tweet, but I noticed that you replied on a couple of keepass2 bugs - do you know what to reply to https://twitter.com/DigitalGrinch/status/391572684372328448?
[14:20] <mfisch> debian is the best route to take if possible bregma
[14:21] <mfisch> does anyone know if the "Packaging branch status" field when branching is supposed to be accurate?
[14:21] <mfisch> Wesnoth says CURRENT but it's got a lucid version in bzr
[15:10] <shadeslayer> stgraber: thanks for sbuild-launchpad-chroot :)
[15:11] <stgraber> hehe, np, I figured it'd be useful to quite a few other developers ;)
[15:11] <shadeslayer> yeah, I recently found out that pbuilder allows shipping files in /usr/local while sbuilder craps out and for the longest time I didn't understand why
[15:12] <shadeslayer> subtle differences in pbuilder and sbuilder apparently
[15:12] <shadeslayer> so its nice to have something is even closer to launchpad in terms of building stuff :D
[15:45] <cjwatson> shadeslayer: No, it has nothing to do with sbuild (which is not spelled sbuilder).  It's more likely that you have pkgbinarymangler installed in your sbuild chroot.
[15:45] <cjwatson> shadeslayer: Since the pkgsanitychecks script in pkgbinarymangler enforces this check.
[15:45] <shadeslayer> oh
[15:45] <shadeslayer> dh_builddeb.pkgbinarymangler: dpkg-deb --build debian/mintsources .. returned exit code 1
[15:46] <shadeslayer> indeedly
[16:47] <mfisch> and to answer my own question, wesnoth is current because it was renamed to wesnoth-1.10 after lucid, both trees are current.