[08:34] <DNS> hi guys :)
[08:35] <czajkowski> DNS: ello
[08:36] <DNS> 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] <czajkowski> open a new one please
[08:38] <DNS> 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] <czajkowski> hmm not sure
[08:39] <czajkowski> StevenK: can you help me out here please?
[08:41] <DNS> for example https://launchpad.net/~dns/+archive/gnu/+packages?field.name_filter=ballandpaddle&field.status_filter=published&field.series_filter=
[08:41] <DNS> precise binaries are gone
[08:41] <DNS> but maverick still there even if they are from same date??
[08:42] <DNS> oh even 5 days later uploaded
[08:46] <DNS> same i recognized with emacs23 packages but the source packages i have deleted now, emacs24 is there:)
[08:52] <DNS> so it looks for me like a database problem, but not sure
[08:57] <wgrant> 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] <DNS> 0_o how can i delete the binaries without source being deleted?
[08:58] <DNS> not sure how i am able to do so
[08:58] <wgrant> You can do it through the API
[08:58] <DNS> but i didnt afaik
[08:58] <wgrant> Hm
[08:59] <DNS> can u see ip of that dl request
[08:59] <DNS> and is that german ip?
[08:59] <DNS> *del
[08:59] <wgrant> In terms of sources, you deleted -2~precise1, uploaded -3~precise1, then deleted -3~precise1 and copied -2~precise1 back in
[08:59] <DNS> oh
[08:59] <wgrant> That's not exactly conventional and might have confused something
[09:00] <DNS> hmm
[09:00] <DNS> but thats kinda bug or?
[09:00] <DNS> or a feature? :p
[09:03] <wgrant> 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] <wgrant> It's a bit hard to see exactly what happened
[09:05] <DNS> 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] <DNS> *so the build has failed...
[09:06] <wgrant> Right, and then in June it looks like you rerequested the deletion of the already deleted initial -2~precise1 package, I think...
[09:08] <wgrant> So there was possibly a race because you deleted and recopied the first one back in so quickly
[09:08] <wgrant> Before the deletion had been processed
[09:08] <wgrant> I think
[09:11] <DNS> 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] <DNS> its 2 times shown, 1 time failed, 1 time build ok
[09:13] <wgrant> Hmm
[09:13] <wgrant> That's not necessarily wrong
[09:13] <wgrant> Since one of the builds is from another PPA
[09:14] <wgrant> It is a tad confusing, though.
[11:12] <DNS> Is the button/link "This answer solved my problem" removed at all or just temp?
[11:13] <DNS> i mean under answers
[11:14] <czajkowski> it's there
[12:39] <DNS> czajkowski: i didnt see the link hm... anyways thanx again for your answer ;-D
[12:39] <czajkowski> np
[14:30] <tumbleweed> I'm not getting any e-mail response from (signed) PPA upload attemps. Any known issue?
[14:31] <tumbleweed> (it is PPA for a team I just joined, so I could have a config screwup, but I can't find it)
[14:32] <czajkowski> tumbleweed: what key are you using as there was an issue yesterday with the wrong keys being used
[14:33] <tumbleweed> czajkowski: teh only key I ever use
[14:33] <tumbleweed> (which is a subkey of my registered key)
[14:33] <czajkowski> https://bugs.launchpad.net/bugs/1053568
[14:33] <czajkowski> subkey is the issue
[14:33] <tumbleweed> aha, ta
[14:34] <czajkowski> np
[14:34] <czajkowski> turns out reading ones bug mail is useful
[14:43] <wgrant> tumbleweed: Is that still happening?
[14:43] <tumbleweed> wgrant: as of an hour or two ago, yes
[14:43] <wgrant> Hm
[14:46] <tumbleweed> 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] <tumbleweed> err 1.1.3
[14:47] <wgrant> tumbleweed: Yeah, there's a ticket about that
[14:48] <tumbleweed> also, these days, it's recommended to put sks behind a frontend proxy, as it's single-threaded
[14:49] <tumbleweed> oh, that's already the case, nm
[14:49] <wgrant> It is, yeah :)
[14:56] <wgrant> tumbleweed: OK, downgraded more packages. Can you try again?
[14:57] <tumbleweed> wgrant: uploaded
[15:01] <tumbleweed> wgrant: accepted, ta
[15:01] <wgrant> tumbleweed: Thanks for confirming.
[17:34] <kamal> 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] <dobey> sure :)