[05:41] <stevenm_> jbicha, crap basically
[11:44] <seb128> ginggs, why did you do those dvisvgm migration-reference/0 triggers? :-(
[12:02] <LocutusOfBorg> cpaelzer, I did update debian bug: #997178 with some content :) I hope you agree on the patch name  (and did sync in kinetic)
[12:10] <cpaelzer> hehe, yeah LocutusOfBorg that is fine
[12:10] <cpaelzer> although I do not see 3.22-4.1 in kinetic, did that just happen and needs to trickle down into visibility?
[12:22] <ginggs> seb128: dvisvgm was failing OOM, added to big_packages now
[12:24] <seb128> ginggs, what was the value of the retries though? it did send back ghostscript which is annoying :/
[12:24] <seb128> ginggs, or would have been nice to retry also other triggers that failed, making it go green in the reference made it consider recent pas failures as regressions which they are not
[12:30] <ginggs> seb128: ok, retried on amd64, arm64 and ppc64el
[12:30] <seb128> ginggs, thanks
[12:31] <seb128> ginggs, still for next time, please avoid retrying on the reference in those cases, it just make other tries results invalid in regard of the reference and means we need to wait longer for those to be tried again
[12:47] <cpaelzer> LocutusOfBorg: oh FYI - the file name is this way due to being auto-created from the upstream commit title
[13:36] <ginggs> seb128: looks like ghostscript still waiting on liblatex-driver-perl/1.2.0-1: amd64: Test in progress, but at least no longer by dvisvgm
[13:37] <seb128> ginggs, great, thanks!
[13:40] <LocutusOfBorg> lol cpaelzer :)
[13:41] <LocutusOfBorg> I like git format-patch -1 :)