[02:22] I am trying to upload a package to my PPA, but I get "Unable to identify 'Michael Marley': in launchpad" in the rejection message. [02:22] Googling yields no results. [02:25] mamarley: Your email address in debian/control or debian/changelog is invalid. [02:26] It's set to michael@mamarley-laptop [02:26] Oh, that would do it. [02:26] Stupid me. Thanks! === OutOfControl is now known as benonsoftware === JoseeAntonioR is now known as jose === FourDollars_ is now known as FourDollars [16:16] hey guys, I looked for it but havent found it - is somewhere a list of currently accepted ppa distributions? since Ive tried to upload a ppa package for precise and it seems not to get built or even get a message about it? [16:43] FloSoft: https://launchpad.net/ubuntu/+ppas (right hand side of the page) [16:43] basically, it's any currently supported distribution of Ubuntu [16:51] FloSoft: if you don't get an e-mail whether the package was accepted or not, then most likely you signed it with the wrong gpg key or similar. === BradCrittenden is now known as bac [21:07] dobey: hmm the key is registered and correct, thats what I think is a bit strange? no message, no email, "upload okay" [21:08] FloSoft: if you tell us the package name then somebody can look it up in the logs for you [21:08] (not necessarily me, I have to go shortly) [21:09] cjwatson: okay its s25rttr in https://launchpad.net/~flosoft/+archive/s25rttr/+packages [21:09] 2014-03-20 21:08:12 INFO Failed to parse changes file '/srv/launchpad.net/ppa-queue/incoming/upload-sftp-20140320-210802-011565/~flosoft/s25rttr/ubuntu/precise/s25rttr_20140320-9255.315_source.changes': GPG verification of /srv/launchpad.net/ppa-queue/incoming/up [21:09] load-sftp-20140320-210802-011565/~flosoft/s25rttr/ubuntu/precise/s25rttr_20140320-9255.315_source.changes failed: Verification failed 3 times: ["(7, 153, u'Key expired')", "(7, 153, u'Key expired')", "(7, 153, u'Key expired')"] [21:10] hmm interesting - since my key is not expired O.o [21:10] apparently it is [21:10] at least, the data on the key server says it is [21:10] hmm okay [21:11] Are you accidentally using an old key, maybe? [21:11] which keyserver does it use? [21:11] keyserver.ubuntu.com [21:11] yes, both your keys there are expired [21:11] pub 1024D/FDA80487 2007-07-07 [expired: 2013-01-06] [21:11] pub 1024D/6D09334C 2007-07-13 [expired: 2013-01-06] [21:11] the keyserver probably won't accept an update at this point removing the expiry as that would make expiries kind of pointless, although you can certainly try sending it an update in case I'm wrong [21:11] do you know how to upload the (local) keys to keyserver from scratch? I cant remember ;) [21:12] gpg --keyserver keyserver.ubuntu.com --send-keys KEY-ID [21:12] if it won't accept an update to an expired key then you probably have no alternative but to create a new one [21:12] you could take the opportunity to make it stronger, e.g. 4096-bit RSA [21:13] * cjwatson goes [21:13] ah no it seems to allow the update [21:14] or i dont know, on the website of the keyserver it doesnt show the expirydate [21:21] hmm okay I'll look at it tomorrow, seems like I really have to generate a new key :/