Comment 6 for bug 1483836

Discussing this in an upstream issue, some of this appears to be due to the debian automatic test-run being too stringent, while upstream diverges. For instance upstream now raises failures when called with unknown arguments, causing unexpected warnings.

Not yet clear how best to fix this. Upstream recommended simply not running the aapits tests, I'm working through the subsequent failures.