https://bugs.kde.org/show_bug.cgi?id=451257
--- Comment #10 from Albert Astals Cid <aa...@kde.org> --- I don't think skipping the test is good, the situation you're in is bad, you have a plugin that when reading the file and saving it again makes changes to the file itself, and that's "bad", so having the test just be skipped or passed is suboptimal, having it fail is a way of saying "you should contact to whoever gave you your libavif and ask them to 'fix it' " Daniel: If we can detect somehow that people are using a "wrongly configured" libavif and give that as error instead of the current failure, sure that's much better -- You are receiving this mail because: You are watching all bug changes.
