Comment 11 for bug 1977873

Good catch, Julie!

So, 2 things:

- why is it working (better) when we remove that inclusion? is it something that is present by default in the build namespace, or injected by the tooling used to build the policy ?

- do you want to make a follow-up patch re-adding the setpgid as a class process, just to be consistent and clear ?

I think SELinux maintainers indeed added some better error catching in the 3.4 release[1] - but at the same time, I'm sing some reverts happening, leading to a 3.4-2 (at least downstream). Guess it's not stable yet, and we may face some other issues in the near future :/.

[1] https://github.com/SELinuxProject/selinux/releases/tag/3.4