On Mon, 10 Jul 2023 at 12:14, Laurent Bigonville <bi...@debian.org> wrote: > > I'm wondering if that couldn't be done directly by the systemd package > instead of the libselinux1, that might avoid us the need to introduce a > new libselinux-common package or headache in the (unlikely?) case there > a soname change to the libselinux library. >
That seems sensible, since most of the tmpfiles.d snippets today are provided by pkg:systemd already. Are you referring with the soname change to co-installations issues (another example would be libselinux1:amd64 vs libselinux1:i386)? That would also be solved by shipping via pkg:systemd. The only already existing alternative that came to my mind is selinux-basics (which is however not installed by default and not a dependency of any package). > Note that we might need to remove the RuntimeDirectory=setrans option in > the mcstrans.service to avoid conflict (but that might be for the next > debian release) > I do not thinks RuntimeDirectory= conflicts with the tmpfiles.d entry, especially since mcstrans uses RuntimeDirectoryPreserve=true since 3.5[1]. But probably the systemd maintainers will know for sure. > If that's OK for you I'll coordinate with the debian systemd maintainer > ACK > Kind regards, > > Laurent > [1]: https://github.com/SELinuxProject/selinux/commit/4622ac0064f63fef0821fe0b0aaa52054e8c5ed3
