Hi, I just wanted to mention that arm32 support is possible, but optional in arm64. So far only a few chips had neglected arm32. So on most aarch64 systems you can "just run" armhf code and it would work.
Now the M1 chip AFAIK has no arm32 and that causes the issue you face, but at the same time explains to some extent why it wasn't much of a problem before. I thought I should mention that as it will affect the solution (do only some arm64 platforms want that, would others regress potentially going from HW to TCG emulation) and testing (as it will behave differently based on which HW you use for aarch64). And while the code to change to do what you ask for in debian/binfmt-install is simple. Past issues like [1] have hit just such issues as I'm afraid we might re-face here. Maybe this needs to become more advanced than just checking $DEB_HOST_ARCH, but that is up for discussion. [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604712
