(sorry, this should have included a Cc... I added some additional analysis below)
Also I am not to hot about hardcoding the list of archs where swtpm is available in debian/control but do not see a better alternatives. - Any ideas?
swtpm is a software TPM implementation[1] and shouldn't demand anything platform specific. Looking at the buildd report[2], the problems seems to be missing dependencies: seccomp and python3-cryptography->cargo[3]. The report doesn't mention it, but libtpms is also missing on some archs[7]. As a first step, I'd make sure seccomp is indeed required and try to build without it on those archs where it isn't implemented. This would apply to alpha and sparc64. As for cargo: The extremely convoluted bootstrapping process (see [4]) ultimately requires an existing rust compiler to compile a new version of rustc and cargo. This can be kicked off with the instructions in [5], but it will require LLVM 19, which is currently missing on a few architectures due to lack of upstream support: [6] So... my conclusion from all of this is: sparc64 could be made to work if swtpm is built without seccomp (for this architecture only). I did a quick test and can confirm that this is possible by passing --without-seccomp and removing SWTPM_TEST_SECCOMP_OPT from the autopkgtest. I don't think the reduced security would be a huge issue on sparc64 anyway... alpha, hppa and sh4 won't work unless LLVM 19 includes support for these architectures, or there is some other way to build the rust packages. [1] https://github.com/stefanberger/swtpm [2] https://buildd.debian.org/status/package.php?p=swtpm&suite=sid [3] https://buildd.debian.org/status/package.php?p=python-cryptography&suite=sid [4] https://salsa.debian.org/rust-team/rust/-/blob/debian/sid/debian/README.Debian [5] https://salsa.debian.org/rust-team/rust/-/blob/debian/sid/debian/README.source [6] https://buildd.debian.org/status/package.php?p=llvm-toolchain-19 [7] https://buildd.debian.org/status/package.php?p=libtpms
