[03:05] <ovnicraft> hello comment system in bugs support any wiki-like format ?
[03:05] <spiv> ovnicraft: no, unfortunately
[03:06] <ovnicraft> start to find many unfortunately things in LP
[05:57] <hyperair> sb levelclear -level clientcrap,crap,joins,parts,quits,nicks,clientnotice
[09:16] <oojah> Morning
[09:16] <Peng> Good morning
[09:17] <oojah> I'm trying to create a milestone 0.10, but getting the error that the milestone 0.1 already exists (which it does).
[09:17] <oojah> Is treating these as the same a design decision or should I report it as a bug?
[09:19] <wgrant> It's a bug, and it's already been reported... let's see if I can find it.
[09:19] <oojah> I did search... on "launchpad itself"
[09:20] <wgrant> Bug #581748
[09:20] <oojah> I never know where to search for lp bugs.
[09:20] <oojah> Ah right. That was in the list but didn't jump out as what I was looking for :)
[09:21] <oojah> Thanks.
[09:22] <oojah> With a workaround as well, ace.
[09:27] <mrevell> Morning!
[13:32] <geser> wgrant: did you had some time to check if the changes to the FTBFS script help?
[13:43] <mrevell> Anyone here able to give me some recipes guidance?
[13:55] <jelmer> hi mrevell
[13:58] <mrevell> Hello jelmer. I'm still struggling with this gtg daily builds things. I was wondering ... when I run pbuilder it seems to pull down a whole load of dependencies but then complains that gconf isn't around. I've asked around and it seems that I need to install python-gconf. Is there a way for me to find out which dependencies will get pulled down automatically and which I need to pull in manually?
[13:58] <jelmer> mrevell: pbuilder should pull in all of them for you
[13:59] <jelmer> mrevell: are you basing your recipe on an existing packaging branch, and do you know if that one is correct?
[13:59] <mrevell> jelmer, Okay, so when I get "ImportError: no module named gconf", does that mean it's not pulling in one of the dependencies?
[13:59] <jelmer> mrevell: it sounds like you need to add python-gconf to Build-Depends in debian/control
[14:00] <mrevell> jelmer, Ah, so that means it's a problem with the packaging?
[14:00] <jelmer> mrevell: it's a common module, so I wouldn't be surprised if it would already be available on most systems where people work on packaging.
[14:00] <mrevell> Ah, I see. Thanks jelmer.
[14:00] <jelmer> mrevell: Yeah, it looks that way.
[14:01] <mrevell> Righto, thanks :) I'll plod on.
[14:01] <jelmer> (pbuilder is great for catching these kinds of things because it gives you a clean build environment each time)
[14:04] <mrevell> jelmer, Forgive the newbie question but does that mean I can't just apt-get install python-gconf? Do I have to add it to debian/control?
[14:05] <jelmer> mrevell: yep, you have to add it to debian/control - (or install it in the pbuilder chroot, but that defeats one of the purposes of pbuilder)
[14:06] <jelmer> mrevell: the point is that this way you make sure all the necessary build dependencies are listed in debian/control
[14:06] <jelmer> as launchpad's build slaves will only have a minimal set of packages installed too, and won't have python-gconf
[14:07] <mrevell> jelmer, Aha. It sounds like I should report this as a bug against the package, too. What do you think?
[14:08] <jelmer> mrevell: yes, it sounds like this is a package bug.
[14:08] <jelmer> mrevell: is the packaging based on something that's already in ubuntu? In that case I wonder why it's not an issue there.
[14:10] <mrevell> jelmer, It is something that's in ubuntu but I'm pulling the debian directory from one of the project's (gtg) dev team's branches, which looks pretty old. Thanks, I'll look into this some more.
[14:11] <jelmer> mrevell: Ah, seems possible it's a missing dependency then, perhaps they only started using gconf recently or something like that.
[22:52] <bekks> hi
[22:53] <bekks> Having a launchpad account, as well as a custom built kernel for ubuntu 10.10 - what would I have to do to "publish" it to others?
[22:57] <thumper> bekks: you'd need a PPA, and upload the source package to the PPA to be built
[23:02] <bekks> thumper: So I have to create a PPA then.
[23:03] <thumper> bekks: that is how people normally make their debs available for others
[23:03] <thumper> bekks: it hooks into the software centre that way
[23:03] <bekks> thumper: I managed it to create my own kernel - how can I create a src package for it?
[23:03] <thumper> bekks: I have no idea
[23:03] <bekks> ok :D
[23:07] <lifeless> bekks: #ubuntu-packaging may be able to help with that
[23:07] <bekks> ah, thx