[00:16] <dima5> Hi. The package "mrcal" is in "jammy-proposed", and somebody here told me it's not migrating because it is failing to build. I just made a jammy chroot to try to see the issue, and it builds just fine for me. Can somebody tell me where to see the package build issue, and how to reproduce? Thanks
[00:23] <dima5> I'm a DD, but not very familiar with Ubuntu processes, so I don't know where everything is here.
[00:31] <JanC> build log for amd64: https://launchpadlibrarian.net/585662084/buildlog_ubuntu-jammy-amd64.mrcal_2.1-2_BUILDING.txt.gz
[00:37] <JanC> dima5: there seem to be errors when creating the .pod files?
[00:40] <dima5> JanC: Thanks. How can I reproduce? I mk-sbuild to make a new jammy chroot and then I sbuild. This completes with no errors
[00:40] <dima5> (running off now, but I'll look at the replies when I come back)
[00:41] <JanC> not sure, one of the Ubuntu developers might know more when they are around (it's weekend though)
[00:44] <JanC> I wonder if it depends on a newer version of another package that wasn't in the archive yet when the failed builds happened?
[05:50] <dima5> I'm seeing a build failure on ubuntu buildds that I can't reproduce in a jammy chroot: https://launchpadlibrarian.net/585662084/buildlog_ubuntu-jammy-amd64.mrcal_2.1-2_BUILDING.txt.gz
[05:52] <dima5> I'm about to upload a package update to Debian/sid that includes more diagnostics so that I can make intelligent guesses about what is failing. Is there any way to speed up the feedback loop? Currently I upload to Debian/sid, then I wait for ubuntu to slurp the update, then I wait for the ubuntu buildd to build it so that I can look at the log to figure out what happened. Then I add more diagnostics and go again. Any way to shorten 
[06:43] <ginggs> dima5: you could upload to a PPA https://help.launchpad.net/Packaging/PPA
[06:45] <dima5> ginggs: OK... That would skip the import step? I'd still need to wait for the buildd to pick it up? Any idea how long that would take? What if I keep uploading to sid?
[06:47] <ginggs> queues are empty now https://launchpad.net/builders so it should be instant
[06:51] <dima5> OK. Let me try that. Thanks
[07:05] <dima5> OK. I uploaded to the PPA. Launchpad doesn't see the upload 10min later. Any idea what the latency is supposed to be?
[07:42] <ginggs> dima5: i'd say normally less than 10 min.  has launchpad still not picked it up?
[07:50] <dima5> ginggs: Nope, not yet: https://launchpad.net/~9-ubuntu-4/+archive/ubuntu/mrcal-test
[07:52] <dima5> Sorry to keep bugging the channel. There's just zero feedback here. I think I figured out when the importer runs: every 6 hours: https://people.canonical.com/~ubuntu-archive/auto-sync/2022-02-10/
[07:52] <dima5> So presumably the Debian/sid upload will show up in 3 hours. Or maybe not!
[07:53] <ginggs> dima5: i'll upload something to my PPA in a few minutes
[07:54] <dima5> ginggs: Cool. Then we'll see how long it takes
[07:54] <dima5> ginggs: I'm using my Debian key to sign the PPA uploads. Ubuntu probably doesn't have that keyring. Should I not be signing it at all?
[07:54] <dima5> I can imagine it's throwing out the upload without telling me for whatever reason
[07:57] <ginggs> i sign my debian and ubuntu uploads with the same key
[07:58] <ginggs> have you imported your key into launchpad?
[07:59] <jbicha> dima5: https://help.launchpad.net/Packaging/UploadErrors
[08:01] <dima5> Yeah, OK. It's some key thing. Reading the docs. Thanks.
[08:02] <ginggs> https://help.launchpad.net/YourAccount/ImportingYourPGPKey#Importing_your_key_into_Launchpad
[08:15] <ginggs> dima5: i've just uploaded a package to my PPA, received the Accepted email in 1 minute, and it is building already
[08:17] <dima5> ginggs: Thanks. Keys were the problem. I now see emails in response to my uploads. The emails are rejections, but at least I now know what to debug. Hopefully I have enough to figure it out now. Thanks for your help!
[08:18] <ginggs> dima5: yw!
[08:21] <dima5> The PPA upload built just fine! I guess I wait for the non-PPA upload to try to build. No idea what's happening here
[08:24] <ginggs> dima5: check your PPA dependencies
[08:24] <ginggs> you want to build with Proposed
[08:25] <ginggs> because that's how the archive is built (similar to how Debian builds everything in unstable)
[08:26] <dima5> ginggs: OK, that makes sense. Doing that now...
[08:33] <dima5> ginggs: That did it. I see the failure, and the extra diagnostics I added tell me clearly what needs fixing. Thanks a ton. You said me probably days of time
[08:33] <dima5> saved
[08:40] <ginggs> \o/
[13:56] <ahasenack> morning