[00:38] <dickbalaska> Hiho, I too suffer from the ppa/keyserver missing key problem.
[00:38] <dickbalaska> https://answers.launchpad.net/launchpad/+question/670766
[00:38] <dickbalaska> 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] <dickbalaska> because it dies wanting to diff the previous version of my package using the missing key.  (xenial updates are ok).
[00:38] <dickbalaska> https://launchpadlibrarian.net/378930581/buildlog_ubuntu-bionic-i386.qtpovray_3.80.1~bionic3_BUILDING.txt.gz
[00:38] <dickbalaska> I can create a new ppa and publish ok
[00:38] <dickbalaska> https://launchpad.net/~qtpovray/+archive/ubuntu/ppa2
[00:38] <dickbalaska> but that is not a valid solution.
[00:38] <dickbalaska> (Having read a sortof related "try again" thread, I was hoping to maybe get a key with the second ppa).
[00:38] <dickbalaska> Is there any kind of workaround? Can someone hand whack me a key? Am I just dead in the water here?
[00:38] <dickbalaska> Thanks.
[08:43] <tsimonq2> What's up with most of the s390x builds cleaning?
[08:43] <tsimonq2> s/builds/builders/
[08:56] <cjwatson> I just did a mass reset, so you probably just caught it in the middle of that
[08:56] <cjwatson> Not quite clear why things are unreliable at the moment though
[09:14] <tsimonq2> Thanks.
[12:29] <tsimonq2> Hm, I think this build is frozen: https://launchpad.net/~kubuntu-ninjas/+archive/ubuntu/ppa/+build/15142629
[12:29] <tsimonq2> akonadi doesn't take that long to build, and I see no build log output.
[12:35] <wgrant> tsimonq2: The build farm is fairly busy atm so things are running a little more slowly than normal
[12:36] <tsimonq2> OK
[12:36] <wgrant> Though this is rather slower than I would have expected, hm
[12:36] <wgrant> Ah, just finished now
[12:37] <tsimonq2> Yup, I was expecting the FTBFS :)
[12:38] <tsimonq2> Thanks wgrant
[16:48] <Lord-Kamina> 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] <Lord-Kamina> 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] <cjwatson> Something like that is on my to-do list
[16:51] <cjwatson> And it will likely also involve arranging that the keyserver isn't on the critical path for builds either
[16:51] <cjwatson> (at least for new keys)
[16:54] <cjwatson> 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:56] <Lord-Kamina> I see.
[16:58] <cjwatson> 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] <cjwatson> 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] <cjwatson> We'd been hoping that the keyserver saga would be done by now, but ...