Bug 141195
Summary: | Missing update announcement | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bernd Bartmann <bernd.bartmann> |
Component: | selinux-policy-targeted | Assignee: | Daniel Walsh <dwalsh> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-04-11 21:50:51 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 141256 |
Description
Bernd Bartmann
2004-11-29 20:34:02 UTC
Ok, I blew it on this one, but just sent out an announcement on selinux-policy-targeted-1.17.30-2.39. Dan Thanks Daniel. This also updated cleanly for me. No new *.rpmnew files. But the new selinux-policy-strict 1.19.10-2 still has this problem. Not sure what you mean by still has this problem. Dan Yeah, I should have opened a new bug on this. What I mean is that the new selinux-policy-strict-1.19.10-2 rpm has the same problem that you seem to have fixed in the selinux-policy-targeted-1.17.30-2.39 update. selinux-policy-strict-1.19.10-2 creates two *.rpmnew files during the update: file_contexts policy.18 So it requires manual action for the user to get the policy activated. The funny thing is the 10-2 has the fix and the 2.39 does not. I think you are seeing the problem, because of a previous install. The fix will only work on a fresh install or an install where the RPMNEW files were moved over the the policy.18/file_context files. Once the files differ from the installed version, you will always get an RPMNEW file. The sources update should reload the policy though. Dan Dan, today I did fresh full install of FC3 and applied all currently available updates including: selinux-policy-strict-1.19.10-2.noarch.rpm selinux-policy-strict-sources-1.19.10-2.noarch.rpm selinux-policy-targeted-1.17.30-2.39.noarch.rpm selinux-policy-targeted-sources-1.17.30-2.39.noarch.rpm Again I got *.rpmnew from the strict and targeted update. Yes this is because the full install on FC3 installs an older version of selinux-policy-targeted-sources which will modify the policy.18 and file_context file. So any package you install afterwards will see that they are modified. If you move back the original policy.18.rpmnew and file_context.new files and install. Then everything will work fine. So until FC4, this will be a problem. |