[01:38] <crass> I'm getting a strange build error: https://launchpadlibrarian.net/153715559/buildlog_ubuntu-raring-i386.cdk_5.0.20130901_FAILEDTOBUILD.txt.gz
[01:39] <StevenK> checking if we have identified curses headers... none
[01:39] <StevenK> configure: error: No curses header-files found
[01:39] <crass> the reason is because ncurses-bin is not install, but it should be installed by a dependency of libncursesw5-dev
[01:40] <crass> ncurses-bin is a dependency of libncursesw5-dev, so why isn't it getting pulled in?
[01:54] <wgrant> crass: ncurses-bin is Priority: required; it's always installed
[01:54] <wgrant> that's why it doesn't show as being installed by the build
[01:55] <wgrant> I'd check your package's configure script to see what that check is actually checking
[03:54] <crass> wgrant: thanks, that helped
[03:59] <wgrant> crass: :)
[07:23] <caktux> How long does it take between a "dput ppa" and having something show up?
[07:25] <wgrant> caktux: A minute or two, if you've signed the package correctlyt.
[07:25] <wgrant> Well, you'll receive an accept/reject email within a minute or two, at least
[07:26] <caktux> Ok I guess I had not my key set before uploading...
[07:30] <caktux> it says it's has already been uploaded...
[07:30] <wgrant> caktux: That's a local check. Give dput the -f option to override that.
[07:33] <caktux> yay some feedback, thanks :)
[07:55] <caktux> It worked! I got a "packages cannot be authenticated" on apt-upgrade though..
[15:04] <shadeslayer> could someone look into this https://launchpadlibrarian.net/153827813/buildlog.txt.gz
[15:05] <shadeslayer> looks like a outdated-python-on-system issue to me
[15:05] <dobey> yes, the builders are still running on 8.04
[15:05] <wgrant> shadeslayer: Yeah, recipe version 0.4 isn't supported on the production builders yet.
[15:05] <wgrant> You need to use version 0.3
[15:05] <shadeslayer> are you sure 0.o
[15:05] <wgrant> s/version/format/
[15:05] <dobey> yes
[15:05] <shadeslayer> I used 0.4 somewhere
[15:05] <cjwatson> shadeslayer: https://bugs.launchpad.net/launchpad-buildd/+bug/915505
[15:06] <shadeslayer> https://code.launchpad.net/~blue-shell/+recipe/expanding-icons-taskmanager-daily
[15:06] <shadeslayer> 0.4 without issues
[15:06] <shadeslayer> so I think it's just a issue with debupstream
[15:07] <shadeslayer> ah well
[16:51] <jcastro> hi, how can I delete a blueprint?
[16:51] <jcastro> or mark it private?
[16:56] <wgrant> jcastro: A blueprint may be made private if the project has a commercial subscription, but they may not be deleted.
[21:32] <JonnyJD> I get "tar: recipe-{debversion}/.pc/manpage.patch/doc/conf.py: Cannot open: Permission denied" on a failed build log that does work locally
[21:33] <JonnyJD> https://launchpadlibrarian.net/153858307/buildlog.txt.gz
[21:33] <JonnyJD> I can't really find out what that is supposed to mean and if that is possibly a problem with the launchpad servers. The patches apply fine, local build is also fine.
[21:34] <JonnyJD> (the packaging originally comes from debian and builds fine there)
[21:50] <JonnyJD> the tar-ignore .pc option mentioned in https://bugs.launchpad.net/launchpad-buildd/+bug/760735 works. (sorry, I searched before, but didn't search with the right terms)
[21:59] <cjwatson> I see "new version of bzr-builder" mentioned, in which case it's probably blocked on the PPA builder upgrade to builderstack