I've prepared an NMU for rust-kvm-bindings (versioned as 0.5.0-1.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should cancel it.
It's not my place to tell you to cancel it, but I can tell you that it it will not clear the path for testing migration.
The new version of rust-kvm-bindings adds a dependency on rust-vmm-sys-util. rust-vmm-sys-util has a few issues * It is not in testing and has missed the freeze deadline. * It FTBFS on armel and mipsel due to the unavailbility of atomicu64 * It fails it's autopkgtests on 32-bit architectures, this looks like broken tests to me. * It fails it's autopkgtests on s390x, some rngs produce different results, presumablly due to endian issues. I don't know what the contracts for said rngs are and hence whether this is a bug in the rngs or in the tests. Since no applications in Debian depend on this package, I do not intend to dig deeper into these issues myself. It would be possible to patch rust-kvm-bindings to disable the dependency on rust-vmm-sys-util and the optional feture that depends on it. If there were applications in Debian that used rust-kvm-bindings and did not use the feature in question I would do so, but as there are no such applications I don't intend to bother.
