Bug 1567980
Summary: | container.if duplicate definition errors when building policy module | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Pierre Ossman <ossman> |
Component: | selinux-policy | Assignee: | Lukas Vrabec <lvrabec> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 31 | CC: | amurdaca, dareynol, dwalsh, jchaloup, lsm5, lvrabec, mgrepl, plautrba, pmoore, rh.container.bot, samuel, zpytela |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | selinux-policy-3.14.4-44.fc31 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-01-21 01:38:38 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Pierre Ossman
2018-04-16 14:04:26 UTC
THis is not a bug. What is happening here is the selinux-policy is shipping its own container.if so that third parties can use it to compile against. When you build container-selinux from scratch you also get a version of contianer.if and their compiler is just pointing out this fact. The compiler will use the local container.if, rather then the selinux-policy-targeted version. This only happens if container-selinux and selinux-policy-devel are installed at the same time. They're shipping identical container.if in two different locations. I'd argue this is a bug in container-selinux package. There should be only one container.if. $ rpm -qf /usr/share/selinux/devel/include/services/container.if container-selinux-2.123.0-2.fc31.noarch $ rpm -qf /usr/share/selinux/devel/include/contrib/container.if selinux-policy-devel-3.14.4-43.fc31.noarch $ sha512sum /usr/share/selinux/devel/include/services/container.if /usr/share/selinux/devel/include/contrib/container.if f6987ed181c24b7de0aacf4c3dd9e5b07d906df7ed87157290656e0f4c6a6663ff87b7ccb8a38ccd90c4778950fed4e50204d5458b57534aaba2c5a5b708cd3b /usr/share/selinux/devel/include/services/container.if f6987ed181c24b7de0aacf4c3dd9e5b07d906df7ed87157290656e0f4c6a6663ff87b7ccb8a38ccd90c4778950fed4e50204d5458b57534aaba2c5a5b708cd3b /usr/share/selinux/devel/include/contrib/container.if The container.if that is in selinux-policy is the downstream of container-selinux. Now whether or not it should be carried, is up to the selinux-policy maintainers. I do not know how often it is copied from the upstream. It is needed so that if policy packages in the selinux-policy package use container interfaces, it will compile. We're taking the latest version of container.if file from container-selinux with every build of selinux-policy. It should be fixed with the next build of selinux-policy. selinux-policy-3.14.4-44.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-397eea28b7 selinux-policy-3.14.4-44.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report. The problem persists in Fedora 33. $ rpm -qa selinux-policy selinux-policy-3.14.6-36.fc33.noarch $ rpm -qa selinux-policy-devel selinux-policy-devel-3.14.6-36.fc33.noarch $ rpm -qa container-selinux container-selinux-2.158.0-1.fc33.noarch |