So you mean this is a known issue? Does that imply that the best course of action from a Debian perspective is simply to disable the test?
So you mean this is a known issue? Does that imply that the best course of action from a Debian perspective is simply to disable the test?