Re: Bug#1103931: gnupg2: Please don't build-depend on swtpm on unsupported architectures
Gregor Riepl <[email protected]>
| Newsgroups | gmane.linux.debian.ports.sparc |
|---|---|
| Message-ID | <[email protected]> |
> 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? I'm very surprised swtpm doesn't work on any architecture. It's a software-based TPM emulator[1] and should therefore be available even on platforms that don't have (and will likely never have) a TPM. Looking at the buildd reports[2], it's missing on some arch because of either a lack of seccomp or python3-cryptography->cargo[3]. 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 will make swtpm much less secure, of course, but until someone steps up and backports seccomp to alpha and sparc64... As for cargo: I don't understand what the problem is. cargo and rustc are built from the same source package, but rustc complains that cargo is unavailable?[4] The control file looks a bit odd to me, but I don't see any immediate indication why it wouldn't work on the unsupported archs. I may look into this a bit more later. [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://buildd.debian.org/status/package.php?p=rustc&suite=sid [5] https://salsa.debian.org/rust-team/rust/-/blob/debian/sid/debian/control?ref_type=heads