[08:20] <alkisg> Hi, https://code.launchpad.net/~ltsp/+recipe/ltsp-proposed shows "No suitable builders" for half an hour now, while in the past I had to wait for the package build, but not for the recipe build. Is this normal? 
[09:57] <alkisg> I cancelled and re-sent it and now it appears fine, thanks :)
[10:48] <cjwatson> alkisg: Cancelling and recreating rarely makes a difference and usually just makes things worse, FWIW.  In this case I think builders were temporarily on manual due to an outage (but it was before I started work).
[10:49] <alkisg> cjwatson: thank you cjwatson; I'll keep it in mind although in this case I also pushed some commits so I had an extra reason to cancel them :)
=== cpaelzer_ is now known as cpaelzer
[14:25] <rbasak> I think https://git.launchpad.net/~git-ubuntu-import/ubuntu/+source/ruby-rails-assets-markdown-it--markdown-it-for-inline is broken somehow at the LP end
[14:26] <rbasak> Is the git repository there corrupt somehow?
[14:26] <rbasak> I'm getting git-ubuntu importing errors I don't fully understand, but then I looked to see what was there and got "CGI Script Error" from LP
[14:37] <cjwatson> 2021-11-03 14:36:48+0000 [-] CGI b'/~git-ubuntu-import/ubuntu/+source/ruby-rails-assets-markdown-it--markdown-it-for-inline' exited with exit code 128
[14:37] <cjwatson> 2021-11-03 14:36:48+0000 [-] Errors from CGI b'/~git-ubuntu-import/ubuntu/+source/ruby-rails-assets-markdown-it--markdown-it-for-inline': b'fatal: Failed to read notes tree referenced by refs/notes/
[14:37] <cjwatson> commits (7b3b42a426aa49f04f21e940ee49ab7980fa0a03)\n'
[14:37] <cjwatson> Does that make sense to you?
[14:38] <cjwatson> It seems to be quite incompletely pushed as well
[14:38] <cjwatson> Lots of errors when I try to clone it
[14:41] <rbasak> cjwatson: that's related to the import error I'm seeing. git-ubuntu adds a note to refs/notes/commits for every import it synthesizes. My errors are related to something broken about that ref.
[14:42] <rbasak> Seems like some kind of referential integrity problem maybe? I expect git to maintain that for me.
[14:43] <rbasak> Bug 1871838 is related, but I don't think it's relevant here except that from the LP end it's refs/notes/commits
[14:45] <rbasak> BTW, this isn't urgent - I'm just trying to clear out the very few remaining errored imports
[14:46] <rbasak> It might be easier just do delete the repository and let git-ubuntu recreate it. It seems unlikely this would impact anyone.
[14:47] <rbasak> But it might be useful to find a bug that'll bite us later
[14:52] <cjwatson> I think just deleting and recreating is best.  If there's an underlying bug then it's probably in the oldish version of git we're running at the server end and I doubt that the effort of investigating this would pay off.
[14:52] <rbasak> git-ubuntu uses "git push --atomic" at the end of an import run, but I don't know if that was the case when this repo was first pushed.
[14:52] <rbasak> OK I'll do that. Thanks!
[14:52] <cjwatson> But if it keeps happening then we should absolutely dig further.
[14:54] <rbasak> Repository deleted, and the importer is rerunning now.
[15:41] <rbasak> The import completed successfully. Thank you for looking!
[15:43] <cjwatson> OK, good