[07:06] good morning === Noskcaj10 is now known as Noskcaj [08:23] hey [08:23] tumbleweed: seeded-in-ubuntu seems sad: IOError: [Errno socket error] [Errno 111] Connection refused [08:39] Laney: Apologies, some maintenance on that host took a bit longer than expected. [08:39] It's been back for a while now [08:39] Works now [08:40] thanks for the boot === Jen is now known as Guest69976 === shadeslayer_ is now known as shadeslayer === freeflying_away is now known as freeflying [14:00] 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] bregma: you need a sponsor, let me get back to you about next steps in 15 mins if thats ok [14:14] I'm nothing if not patient [14:14] I assume it can't go to Debian? [14:16] 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] if and when it gets into Debian, we can start synching then [14:20] 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] debian is the best route to take if possible bregma [14:21] does anyone know if the "Packaging branch status" field when branching is supposed to be accurate? [14:21] Wesnoth says CURRENT but it's got a lucid version in bzr === freeflying is now known as freeflying_away [15:10] stgraber: thanks for sbuild-launchpad-chroot :) [15:11] hehe, np, I figured it'd be useful to quite a few other developers ;) [15:11] 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] subtle differences in pbuilder and sbuilder apparently [15:12] so its nice to have something is even closer to launchpad in terms of building stuff :D [15:45] 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] shadeslayer: Since the pkgsanitychecks script in pkgbinarymangler enforces this check. [15:45] oh [15:45] dh_builddeb.pkgbinarymangler: dpkg-deb --build debian/mintsources .. returned exit code 1 [15:46] indeedly === chuck_ is now known as zul_ === mdeslaur is now known as chuck_ === chuck_ is now known as mdeslaur [16:47] and to answer my own question, wesnoth is current because it was renamed to wesnoth-1.10 after lucid, both trees are current. === chuck_ is now known as zul === ara is now known as Guest23418 === jalcine_ is now known as jalcine