[00:17] <plars> Saviq: yeah, the only thing I can think is that something is messed up in your schroot. some bad update (likely?) somehow got your  source.list on the system messed up, so maybe the schroot needs to be recreated again after I addressed that? Or maybe something in the archive it is complaining about is still in a bad state
[00:18] <plars> Saviq: I don't think anything is wrong with the system itself though - it seems to be complaining about the archive, but I'm not familiar with that error
[00:19] <plars> Saviq: if it's not urgent, then we should probably see if it resolves itself over the weekend, and check with someone on #ubuntu-devel to see if they have ideas
[03:50] <bzoltan> rvr: thank you!
[03:52] <bzoltan> Now I need somebody who can publish this silo -> https://requests.ci-train.ubuntu.com/#/ticket/1266
[03:53] <bzoltan> any trainguard here who could help ^ I could win 2 days of testing
[03:53] <bzoltan> Mirv: ^ if you happen to be around for a click :)
[10:46] <Mirv> seeing if the train manages do to proper diffs
[10:46] <bzoltan> Mirv: Thanks a bunch!
[10:47] <Mirv> I'll debdiff if not
[10:49] <Mirv> yeah train indeed fixed itself with diff_only
[10:56] <bzoltan> \o/
[11:05] <Mirv> robru: thanks, indeed they are correct. I guess I was just confused at seeing many silos having a weird/unexplainabale diff and needing the manual diff_only run.