=== JanC is now known as Guest1583 === JanC_ is now known as JanC [04:53] @rbasak yup we are aware of it; it's one of the things in a grab-bag of maintenance we need to find time for === JanC_ is now known as JanC [10:28] OK. Thanks! === JanC_ is now known as JanC [19:20] dput black hole? I'm working on (new) packages for Apache Arrow and Apache ORC which are dependencies for the next release of Ceph. I have a set of .../debian/* files that work on my jammy box (debuild + pbuilder) but when I dput them to launchpad they aren't getting built. dput says it successfully uploaded them. https://launchpad.net/~ceph-apache-arrow/+archive/ubuntu/orc. [19:20] Is there somewhere I can look to see where they went? [19:23] Is there somewhere else I should seek assistance, here seems kinda dead [19:30] trying to build for mantic and noble. [19:39] kkeithley: usually, launchpad will email you error messages if your upload had problems [19:40] kkeithley: if you didn't get an email, the usual cause is that the upload wasn't properly signed -- launchpad won't email people on invalid signatures, to avoid hassling people who might not have actually made the upload in question [19:57] it's was signed, with the same sig as the other packages I build on launchpad. I have gotten emails when those fail to build, and those showed up on the site first. [19:59] kkeithley: If nobody with access to check logs is answering here, then you can file a ticket on https://answers.launchpad.net/launchpad/+addquestion and that goes into a queue that does get checked (most likely European working hours) [20:02] yep, just posted my question there [20:04] The reason will show up in the process-upload logs, they just aren't public [21:05] I actually quoted some of cjwatson's (internal) responses in my response to kkeithley :) [21:07] clinton-fung: do check process-upload.log though, since you can and I can't :) [21:07] In process-upload.log for ppa-uploader, I wasn't able to find any references to something in the ticket kkeithley logged. [21:07] That's odd in itself - I'd expect to see _something_, positive or negative [21:08] Yeah I did that; just my grep fu failed me [21:08] It might not quote the PPA name, if it failed before the point where it decided where to put the package [21:08] This is the URL quoted in the question: https://launchpad.net/~ceph-apache-arrow/+archive/ubuntu/orc [21:08] Getting the uploaded package name might help - that's a little more likely to show up in grep [21:08] I've tried all sorts of case-insensitive greps on permutations of things from that URL [21:09] (It may or may not be the case that the package name is particularly related to that URL) [21:09] I found an answer from wgrant from years gone by highlighting that in a particular other user's case, they didn't declare any binary packages [21:10] If that were the case there'd be a rejection in process-upload.log [21:10] Usually best to locate that first, somehow. One other thing that might be worth checking is when the dput attempt was [21:10] Depending on when this happened, we had a major outage 1.5 days ago, for an extended period of time [21:51] @kkeithley I have asked for the above information on the ticket, too. If you aren't able to remember when the original dput was executed (because I understand people don't generally make a note of the time for everything they do in life), perhaps it makes sense for you to attempt it again using the -f option (to avoid getting the error about the package having already been uploaded), so that you [21:51] can note the time and share it with me. [23:32] @kkeithley thanks for your response on the question. It helped me find the relevant logs, and indeed it seems like you used a key that is not registered in Launchpad. In that scenario, we won't email you about the failure. [23:39] I see. Okay, thanks