Thanks for the report. I was aware of the autopkgtest failures, but didn't realize that a failure there prevented migration. This failure seems a property of the autopkgtest environment, and has thus proved difficult to debug without a release. The upcoming 1.2.21 release has added diagnostics to help investigate this issue; I'll go ahead and cut that release.
I don't see any means by which a test can be marked ignore/flakey in the autopkgtest syntax, which seems unfortunate (right now, I'm trying to debug this failure in the specific autopkgtest environment; the test works fine on my setup and any other installed setup I can find). Do you have any suggestions? I could put a || true on Test-Command, but I'd rather use an idiom that we can search for etc.
