serious scriptlet problems with today's updates

[Michael Schwendt]

On Fri, 17 Jan 2014 11:46:26 -0500, Mark Haney wrote:

> Hash: SHA1
> 
> On 1/17/2014 10:55 AM, Suvayu Ali wrote:
> > On Fri, Jan 17, 2014 at 4:49 PM, Mark Haney <mhaney at practichem.com>
> > wrote:
> >> 
> >> My question is, WTF happened?  My system is pretty clean. I
> >> never install packages by hand, only by either the standard
> >> Fedora repos or RPMFusion.  These were all Fedora repo updates,
> >> FWIW.  Did anyone else see this?
> > 
> > https://lists.fedoraproject.org/pipermail/users/2014-January/445554.html
> >
> > 
> https://lists.fedoraproject.org/pipermail/users/2014-January/445555.html
> > 
> 
> Geez.  NEITHER of the two replies I received were useful in any
> meaningful way.  That's just lazy, people.  If it hadn't been for
> Ian's just posted message, I'd still not know WTF was going on.  And
> I'm seriously concerned about how an SELinux policy was released
> stable with this big a problem attached to it.

Please don't be so negative. The linked messages explain the issue.
Nothing can be done about it anymore, since the previous selinux-policy
update ought to have been offered in the updates-testing repo for a longer
time.

The fix is on its way into the updates repo already. Try this as long as
you can still see 
  https://admin.fedoraproject.org/updates/FEDORA-2014-0870/selinux-policy-3.12.1-117.fc20
in updates-testing:

    su -
    setenforce 0
    yum clean expire-cache
    yum --enablerepo=updates-testing update selinux-policy\*
    setenforce 1