Bug 141195 - Missing update announcement
Missing update announcement
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Depends On:
Blocks: 141256
  Show dependency treegraph
Reported: 2004-11-29 15:34 EST by Bernd Bartmann
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-04-11 17:50:51 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bernd Bartmann 2004-11-29 15:34:02 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041111 Firefox/1.0

Description of problem:
The update announcement is missing on fedora-announce list.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. look for an update announcement

Additional info:
Comment 1 Daniel Walsh 2004-12-02 15:00:19 EST
Ok, I blew it on this one, but just sent out an announcement on

Comment 2 Bernd Bartmann 2004-12-03 03:28:30 EST
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.
Comment 3 Daniel Walsh 2004-12-03 10:03:15 EST
Not sure what you mean by still has this problem.

Comment 4 Bernd Bartmann 2004-12-03 10:13:42 EST
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

So it requires manual action for the user to get the policy activated. 
Comment 5 Daniel Walsh 2004-12-03 11:02:08 EST
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.

Comment 6 Bernd Bartmann 2004-12-10 12:18:55 EST
Dan, today I did fresh full install of FC3 and applied all currently
available updates including:


Again I got *.rpmnew from the strict and targeted update.
Comment 7 Daniel Walsh 2004-12-10 12:46:16 EST
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.

Note You need to log in before you can comment on or make changes to this bug.