On Wed, 10 Apr 2024 at 11:54:02 +0200, Christian Kastner wrote:
> I've already filed an MR at vmdb2 upstream that fixes the logic, but I
> thought it might be best to track the issue here as well. Please feel
> free to close this bug if you think it is superfluous.
If there's no actionable bug in autopkgtest, and a fix in vmdb2 will
automatically fix autopkgtest without any autopkgtest code changes being
required or desirable, then the usual way to represent that would be to
give the vmdb2 bug report an "affects" on autopkgtest.
smcv
