[06:56] <CarlFK> https://launchpad.net/~carlfk  OpenPGP keys:     80E61AF4, 63D0E04D,17901261                         How did I end up with 3?
[06:56] <CarlFK> (I am guessing I made them, but have no idea why)
[07:06] <wgrant> Heh, well, if you don't know then we have no chance :)
[08:55] <CarlFK> wgrant:  where is the .conf file that  dput  or something that signs and uploads to my PPA?
[08:56] <wgrant> CarlFK: dput uploads, debsign signs. debsign respects the the DEBSIGN_KEYID setting in ~/.devscripts
[08:57] <CarlFK> hmm... ls: cannot access /home/carl/.devscripts: No such file or directory
[08:58] <CarlFK> how about dbuild ?
[09:00] <CarlFK> hmm.. how the heck does this work...  debuild -S -sa ; dput ppa:carlfk/ppa *.changes
[09:03] <wgrant> wgrant@lamuella:~$ man debuild | grep debsign created (assuming that lintian is installed), and finally signs the .changes and/or .dsc files as appropriate (using debsign(1) to do  this  instead
[09:03] <wgrant> CarlFK: debuild is a warpper around dpkg-buildpackage, debsign, and a few others bits and pieces.
[09:04] <wgrant> Put DEBSIGN_KEYID=deadbeef in your ~/.devscripts (file, not directory)
[09:04] <CarlFK> im trying to track down what key I use
[09:05] <CarlFK> theres a chance I haven't run this script on this box
[09:05] <CarlFK> so maybe I never brought over the .devscripts file
[16:29] <mark06> how can I set the version a bug affects?
[16:29] <mark06> isn't milestone for the version where it'll be fixed?
[16:49] <teward> mark06: version affected is usually reported in the bug itself if the bug was filed with `ubuntu-bug` or similar
[16:51] <mark06> ok I just left it implied in commit message referenced in the bug https://bugs.launchpad.net/pidgin++/+bug/1398036
[16:51] <ubot5`> Launchpad bug 1398036 in Pidgin++ "Google Talk not working in Windows" [Medium,Fix released]
[16:51] <mark06> 'residual change for rev 241'... so that's where the bug appeared
[16:52] <mark06> it was being a bit odd because the milestone is kind of "next" preview
[16:53] <mark06> I just replace binaries in same milestone......
[16:53] <mark06> but I think it's going to work, thanks!
[16:53] <teward> well for other launchapd projects it usually depends on how they handle their bugs.  milestone usually, I believe, is the target for when you want it fixed.
[17:08] <teward> wgrant or cjwatson: the PPA signing keys are issued per-user, not per-PPA, right?
[17:09] <bsc> Hi. Need a help. Will the key of a ppa change if I delete it and recreate one with same name?
[17:11] <teward> bsc: I don't believe it will, I've done the same thing before with PPAs and the signing key had remained the same, but of course, that's similar to the same question I asked - are PPA signing keys issued per-user or per-PPA
[17:11] <teward> guess we'll just need to wait for a response :)
[17:15] <bsc> teward, ok..
[19:23] <Rhonda> Hi there.  Where would be the right place to raise concerns with a launchpad user?
[20:37] <wgrant> Rhonda: https://answers.launchpad.net/launchpad/+addquestion for issues that can be public, otherwise feedback@launchpad.net or PM to me.
[23:22] <cjwatson> teward: When you create a second or subsequent PPA for a given user, it inherits the signing key from the user's first PPA.  So they're effectively per-user.
[23:24] <wgrant> Ah yeah, we ended up discussing that in #ubuntu-packaging.
[23:34] <teward> cjwatson: (late reply) wgrant addressed that in the #ubuntu-packaging channel :)
[23:34] <teward> my next question was one wgrant already answered - what's the bitstrength on them.  mine's sufficiently old enough that it's 1024 >.>