=== michaelh|away is now known as michaelh === Logan__ is now known as Logan_ === bigjools-afk is now known as bigjools === michaelh is now known as michaelh|away === apachelogger is now known as trainlogger === bigjools-afk is now known as bigjools [08:34] hi guys :) [08:35] DNS: ello === czajkowski changed the topic of #launchpad to: Reduced Builder capacity at present | Help contact: czajkowski | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad [08:36] i have 2 questions: 1. If i requested a year ago to increase my PPA capacity and now its full again and i could need more space again, does it make sense to reopen the request from a year ago or should i open a new one? [08:36] open a new one please [08:38] 2. i recognize that some binaries in my ppa are gone somehow even if they are just a half year old, what is the reason for binaries being deleted from a ppa [08:38] hmm not sure [08:39] StevenK: can you help me out here please? [08:41] for example https://launchpad.net/~dns/+archive/gnu/+packages?field.name_filter=ballandpaddle&field.status_filter=published&field.series_filter= [08:41] precise binaries are gone [08:41] but maverick still there even if they are from same date?? [08:42] oh even 5 days later uploaded [08:46] same i recognized with emacs23 packages but the source packages i have deleted now, emacs24 is there:) [08:52] so it looks for me like a database problem, but not sure [08:57] DNS: https://launchpad.net/api/devel/~dns/+archive/gnu/?ws.op=getPublishedBinaries&binary_name=ballandpaddle&distro_arch_series=/ubuntu/precise/i386&version=0.8.1-bzr118-2~precise1 says that you deleted the binaries at 2012-06-11T23:16:27.366326+00:00 [08:57] 0_o how can i delete the binaries without source being deleted? [08:58] not sure how i am able to do so [08:58] You can do it through the API [08:58] but i didnt afaik [08:58] Hm [08:59] can u see ip of that dl request [08:59] and is that german ip? [08:59] *del [08:59] In terms of sources, you deleted -2~precise1, uploaded -3~precise1, then deleted -3~precise1 and copied -2~precise1 back in [08:59] oh [08:59] That's not exactly conventional and might have confused something [09:00] hmm [09:00] but thats kinda bug or? [09:00] or a feature? :p [09:03] There's probably a bug in there somewhere, but you've done some pretty strange things to that package in April and June [09:03] It's a bit hard to see exactly what happened [09:05] well i can describe, i tried to build latest revision but that contained code depended on a special package which was/is not released anywhere, as i figured out later... so build the as failed and i copied the previous packages back in there [09:06] *so the build has failed... [09:06] Right, and then in June it looks like you rerequested the deletion of the already deleted initial -2~precise1 package, I think... [09:08] So there was possibly a race because you deleted and recopied the first one back in so quickly [09:08] Before the deletion had been processed [09:08] I think [09:11] wgrant: here i did similar i think and that confused launchpad too https://launchpad.net/~dns/+archive/gnu/+sourcepub/2559218/+listing-archive-extra [09:12] its 2 times shown, 1 time failed, 1 time build ok [09:13] Hmm [09:13] That's not necessarily wrong [09:13] Since one of the builds is from another PPA [09:14] It is a tad confusing, though. [11:12] Is the button/link "This answer solved my problem" removed at all or just temp? [11:13] i mean under answers [11:14] it's there === sagaci__ is now known as sagaci [12:39] czajkowski: i didnt see the link hm... anyways thanx again for your answer ;-D [12:39] np [14:30] I'm not getting any e-mail response from (signed) PPA upload attemps. Any known issue? [14:31] (it is PPA for a team I just joined, so I could have a config screwup, but I can't find it) [14:32] tumbleweed: what key are you using as there was an issue yesterday with the wrong keys being used [14:33] czajkowski: teh only key I ever use [14:33] (which is a subkey of my registered key) [14:33] https://bugs.launchpad.net/bugs/1053568 [14:33] Ubuntu bug 1053568 in Launchpad itself "PPA uploads signed with subkeys silently fail" [Critical,Fix released] [14:33] subkey is the issue [14:33] aha, ta [14:34] np [14:34] turns out reading ones bug mail is useful [14:43] tumbleweed: Is that still happening? [14:43] wgrant: as of an hour or two ago, yes [14:43] Hm [14:46] wgrant: and yes, you shoudl get your keyservers upgraded. I did a backport of sks 1.3.1 to precise, that's probably the best thing to run [14:46] err 1.1.3 [14:47] tumbleweed: Yeah, there's a ticket about that [14:48] also, these days, it's recommended to put sks behind a frontend proxy, as it's single-threaded [14:49] oh, that's already the case, nm [14:49] It is, yeah :) [14:56] tumbleweed: OK, downgraded more packages. Can you try again? [14:57] wgrant: uploaded [15:01] wgrant: accepted, ta [15:01] tumbleweed: Thanks for confirming. === matsubara__ is now known as matsubara === yofel_ is now known as yofel === czajkowski changed the topic of #launchpad to: Reduced Builder capacity at present | Help contact:- | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad [17:34] thanks folks, for all the help diagnosing and fixing the gpg subkeys problem... sinzui, patdk-wk, dobey, thedac, wgrant, and anyone else who I missed there [17:44] sure :) === bulldog98_ is now known as bulldog98 === trainlogger is now known as apachelogger === davi_ is now known as davi