[00:38] Hiho, I too suffer from the ppa/keyserver missing key problem. [00:38] https://answers.launchpad.net/launchpad/+question/670766 [00:38] It was just irksome warnings before and I could wait for a fix but now it's moved to fatal because I can't publish an update in bionic [00:38] because it dies wanting to diff the previous version of my package using the missing key. (xenial updates are ok). [00:38] https://launchpadlibrarian.net/378930581/buildlog_ubuntu-bionic-i386.qtpovray_3.80.1~bionic3_BUILDING.txt.gz [00:38] I can create a new ppa and publish ok [00:38] https://launchpad.net/~qtpovray/+archive/ubuntu/ppa2 [00:38] but that is not a valid solution. [00:38] (Having read a sortof related "try again" thread, I was hoping to maybe get a key with the second ppa). [00:38] Is there any kind of workaround? Can someone hand whack me a key? Am I just dead in the water here? [00:38] Thanks. === maclin1 is now known as maclin === maclin1 is now known as maclin === mjog_ is now known as mjog === bigfoot-- is now known as bigfoot- === maclin1 is now known as maclin [08:43] What's up with most of the s390x builds cleaning? [08:43] s/builds/builders/ [08:56] I just did a mass reset, so you probably just caught it in the middle of that [08:56] Not quite clear why things are unreliable at the moment though [09:14] Thanks. [12:29] Hm, I think this build is frozen: https://launchpad.net/~kubuntu-ninjas/+archive/ubuntu/ppa/+build/15142629 [12:29] akonadi doesn't take that long to build, and I see no build log output. [12:35] tsimonq2: The build farm is fairly busy atm so things are running a little more slowly than normal [12:36] OK [12:36] Though this is rather slower than I would have expected, hm [12:36] Ah, just finished now [12:37] Yup, I was expecting the FTBFS :) [12:38] Thanks wgrant === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === bdmurray_ is now known as bdmurray === chihchun is now known as chihchun_afk [16:48] Hey... re: the missing ppa keys issue; would it be too complex/hard to make a temporary stopgap for ppa owners to be able access their ppa key (requiring previous authentication of their personal key) so they can then manually propagate it to the keyserver? [16:49] Sorry if it's a dumb idea and I almost certainly don't fully grasp all the security implications of such a measure but the thought just hit me in the shower and I thought it might prove a reasonable temporary fix until whatever is the real issue can be hammered away. [16:50] Something like that is on my to-do list [16:51] And it will likely also involve arranging that the keyserver isn't on the critical path for builds either [16:51] (at least for new keys) [16:54] https://bugs.launchpad.net/launchpad/+bug/1667725 would be the first bit of it - as my comment notes, it's really only useful with some other steps, but given that we now have plans for some further steps (at least William and I talked about that last week), it's probably worth going ahead with that [16:54] Ubuntu bug 1667725 in Launchpad itself "[feature request] make full ppa signing public key available over https" [Undecided,New] [16:56] I see. [16:58] The next bit after that would be to start storing PPA keys directly in the LP database, and having some kind of best-effort arrangement to propagate them to the keyservers [16:58] That would be a lot more complex for user keys; but for PPA keys, all changes to them are under LP's control, so we don't need to worry about updates [16:59] We'd been hoping that the keyserver saga would be done by now, but ...