[Bug 2346531] Review Request: selinux-policy-epel - SELinux policy for EPEL packages

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.redhat.com/show_bug.cgi?id=2346531



--- Comment #17 from Petr Lautrbach <plautrba@xxxxxxxxxx> ---
(In reply to Carl George 🤠 from comment #16)
> > This is supposed to be EPEL only package. I have not found any other way how to get it in.
> 
> EPEL-only packages are fairly rare and should not be needed in most cases. 
> The primary case is for unshipped subpackages, as the docs I linked
> describes.  Why does this need to be EPEL only?  Are these policies in the
> Fedora selinux-policy package?  If so, why are they not present in the RHEL
> package?  Can these be included in the RHEL package?

Fedora is one big repo which contains all packages and Fedora selinux-policy
therefore contains modules for all packages and it does not make sense to split
it.

OTOH since selinux-policy-targeted-40.13.26-1.el10 the policy packages ship
only modules related to packages in CentOS Stream resp RHEL. It makes the
policy smaller, operation with policy faster and so on.

Packages that are in EPEL are supposed to be confined by this
selinux-policy-epel package. Therefore this split. Also
selinux-policy-epel-{targeted, mls} uses for modules priority 200 instead of
100 as it used in https://fedoraproject.org/wiki/SELinux/IndependentPolicy
It makes it clear which module comes from CentOS Stream selinux-policy and
which comes from EPEL.

> > This is actually a bug and I  will address it.
> 
> Once this is fixed, many paths will conflict with the RHEL
> selinux-policy-devel package, which is not allowed by EPEL policy.  We have
> an exception to allow this only in the narrow use case of providing an
> alternate version of software for compatibility purposes.  This is not the
> same situation.
> 
> https://docs.fedoraproject.org/en-US/epel/epel-policy/
> #policy_for_conflicting_packages

The fix will be more in sense do not ship interface files from base policy in
epel policy and vice versa. Similar to policy subpackage where there's no
conflict as demonstrated in #c15. Or maybe i'll drop selinux-policy-epel-devel
completely as it would be covered by selinux-policy-devel. Not sure, need to do
some investigation.


-- 
You are receiving this mail because:
You are always notified about changes to this product and component
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2346531

Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202346531%23c17

-- 
_______________________________________________
package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite Conditions]     [KDE Users]

  Powered by Linux