[00:15] <KNRO> Hi, on pbuilder-dist update, I get this error W: GPG error: http://ppa.launchpad.net natty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 487CEC2B3F33A288
[00:15] <KNRO> any idea why?
[00:16] <lifeless> you probably haven't apt-key added the ppa; apt-add-repository should do that automatically for you
[00:20] <KNRO> no that's not it.. that key is not my ppa key
[00:21] <KNRO> the only I'm tryng pbuilder-dist to update from
[00:22] <lifeless> that key is for 'Launchpad INDI'
[00:22] <KNRO> yes...
[00:23] <KNRO> pbuilder-dist natty update --othermirror "deb http://ppa.launchpad.net/mutlaqja/ppa/ubuntu natty main"
[00:23] <KNRO> and that's the command...
[00:23] <lifeless> and like I said, you probably apt-key added it
[00:45] <KNRO> no hope! I tried doing sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 487CEC2B3F33A288
[00:45] <KNRO> still same result
[07:12] <KNRO> I already have a gpg key imported for my launchpad ppa, however, pbuild-dist update still displays the same error : GPG error: http://ppa.launchpad.net natty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 487CEC2B3F33A288
[07:12] <KNRO> I tried apt-key add, add-apt-repository but nothing works
[07:13] <KNRO> sudo apt-get update runs fine with no errors, just pbuilder-dist update gives that error
[07:14] <jmarsden> KNRO: Maybe you need to apt-key ... that key inside the chroot??
[07:14] <KNRO> how do I know if it's inside chroot?
[07:14] <geser> KNRO: did you add that PPA key inside your normal system or inside the pbuilder environment?
[07:15] <KNRO> I just did sudo apt-get add normally...
[07:15] <KNRO> how can I add to it pbuilder environment?
[07:15] <geser> then you only added it to your normal system and not the pbuilder
[07:16] <KNRO> ok, how to add to pbuilder then?
[07:16] <geser> "pbuilder-dist natty login --save-after-login" gives you a shell inside your pbuilder (the --save-after-login is important else your changes get thrown away at the end)
[07:16] <jmarsden> KNRO: Something like   pbuilder login --save-after-login  ... then apt-key around in there and exit when done.
[07:17] <geser> then add the key the same you did it before and you can use "apt-get update" to check if it runs now without any error message
[07:18] <geser> if everything works as wanted "exit" the pbuilder and your changes get saved
[07:19] <KNRO> ok let me try that
[11:01] <OwaisL> What is the state of python-skype (Skype4Py) in Oneiric? I can't find the package anymore
[11:04] <geser> OwaisL: it got removed in Debian and Ubuntu: (From Debian) RoQA; orphaned, low popcon; Debian bug #622667
[13:53] <Laney> bdrung: can we upload u-d-t?
[16:37] <tumbleweed> Laney: do we not want some bug closing in syncpackage?
[16:38] <Laney> unless someone is actively working on it right now, I wouldn't delay putting the initial support out there
[16:40] <Laney> (the announcement can mention the caveats)
[16:40] <tumbleweed> yeah, nobody's working on it
[17:27] <tumbleweed> Laney, cjwatson: I'm guessing we should make it check the sync blacklist too? It doesn't look like +localepackagediffs knows about it
[17:46] <cjwatson> tumbleweed: meh, probably, yes
[19:13] <jtaylor> is it normal that branches to be sponsored should have distro set to UNRELEASED?
[19:13] <jtaylor> just got a few complaints in some of my as-needed branches, but its the first time I get that complaint
[19:16] <jbicha> I always used oneiric but I was corrected today too
[19:29] <tumbleweed> jtaylor: we do that in DPMT, as it makes good sense for trunk in team-maintained packages. I don't see a good reason to do it for proposed merges in Ubuntu
[19:54] <tumbleweed> jtaylor: endorsed your MOTU application
[19:55] <jtaylor> :O it isn't finished yet :/
[19:55]  * tumbleweed doesn't care
[19:55] <jtaylor> but thanks