[00:16] <wgrant> tomreyn: Fixed
[00:16] <wgrant> Thanks for the report.
[00:30] <tomreyn> wgrant: thank you.
[11:19] <Laney> are stack traces from LP OOPSes OK to paste into public bugs?
[11:19] <Laney> Nothing secret in there I don't think
[11:33] <cjwatson> Depends on the details, but they're usually OK
[11:33] <cjwatson> Do check first :)
[11:56] <Laney> Ta
[12:49] <cjwatson> Laney: thanks for the older bug reference - it is indeed similar enough to that to be useful
[12:50] <Laney> cjwatson: You're welcome - actually it was the "um, is this your bug?" thing when I filed it that found that one (although I would have searched, I might not have searched with Fix Released) :-)
[18:10] <kyrofa> ppc64 snap builds look a little sad, anyone know what's happening here? https://launchpadlibrarian.net/383859979/buildlog_snap_ubuntu_xenial_ppc64el_nextcloud-daily-13_BUILDING.txt.gz
[18:27] <cjwatson> That repository was last pushed about three hours ago, rather more recently than that build happened.  Are you certain that that branch actually existed at that point?  (Try the build again.)
[18:29] <cjwatson> I'd certainly go for "contents of repository weren't quite what you think they were" over "builder was subtly broken in some way that managed to convince git that a branch didn't exist but not show any other obvious signs of corruption", by Occam's razor. :)
[19:26] <QwertyChouskie> Can someone take a look at why https://code.launchpad.net/~stk/stk/trunk is failing to import?  It worked once... then failed all subsequent times
[19:26] <QwertyChouskie> BTW thanks for the quick fix for the other issue
[19:57] <QwertyChouskie> Log: https://launchpadlibrarian.net/383938195/stk-stk-trunk.log
[19:57] <QwertyChouskie> AssertionError: Invalid sha for <Commit 31ca89256948183ce59ef6fd96c29900eeca3570>: 83ff426c5385f865818d594bc3d9ce6a7afec3ed