Control: fixed -1 1:6.0+dfsg-1~exp0 Control: tag -1 patch Control: tag -1 upstream Control: tag -1 bullseye
I've now done several runs spread over several days and they all succeeded, so that alone would indicate that the issue is resolved with the 6.0 version. On top of that, Bernhard Übelacker has identified the exact commit which fixed the issue and when that commit got backported to 5.2, the issue was resolved there too. Normally I'd close the bug by sending a msg to 988174-done@b.d.o, but I'm explicitly not doing that here as I think this bug should be fixed for Bullseye as well. AFAIK that usually requires a RC bug and I don't think this bug qualifies as such. But I (/we?) do think that a/the maintainer should evaluate this issue, also because the fix is tiny and targeted, and take the appropriate action. As the maintainers email address/ML doesn't (seem to) exist, I've explicitly CC-ed the uploader of 1:6.0+dfsg-1~exp0 in this response. Cheers, Diederik
signature.asc
Description: This is a digitally signed message part.
