On Thu, Jul 15, 2021 at 08:08:13AM +0200, Helmut Grohne wrote: > I also proposed a solution here, which is avoiding > SystemCallArchitectures=native. Initially, that sounds like a > maintenance nightmare until you notice that it can be solved on a > technical level. We already have dh_installsystemd. How bad would it be > to have dh_installsystemd change .service files and automatically > replace =native with a concrete architecture (in arch:any packages > only)? systemd would no longer detect the architecture of services from > its own one but rather use the one documented by the package. The mixing > of architectures that our earlier solution broke would now partially > work. We'd fix one package and binNMU the pile.
I've discussed this with #systemd on libera.chat. That resulted in a new approach: Letting systemd detect the architecture of the binary being executed. We've reported that as a feature request at https://github.com/systemd/systemd/issues/20277. I therefore propose to temporarily ignore the SystemCallArchitectures issue on the Debian side and see what upstream thinks about it. The libsystemd-shared issue can be tackled independently. Helmut
