Hi, guys.
Thanks for your advices.
I updated selinux-related policies to 117.
Hope others could fix theirs, too...
2014/1/19 Stephen Glenn <stepglenn(a)gmail.com>
I'm running a pretty standard Fedora-20 release.
What I did to work through the fixes on this:
## Clean up yum to start with.
yum --enablerepo='*' clean all
yum-complete-transaction --cleanup-only
## Set SE to permissive
setenforce 0
## Find out what needs help
yum check
## Manually update, remove, fix, etc... PAIN.
## Then to correct any duplicates
package-cleanup --dupes
package-cleanup -y --cleandupes
## Get the system updates
yum -y --skip-broken distro-sync
## Set SE back to enforcing
setenforce 1
yum check
getenforce
... I hope this help others...
On Sat, Jan 18, 2014 at 11:56 AM, Dominick Grift <dominick.grift(a)gmail.com
> wrote:
> On Sat, 2014-01-18 at 16:13 +0900, Shintaro Fujiwara wrote:
> > HI, during the process of #rpm -ivh my_program, I had an error saying
> > as follows.
> >
>
> Yes this was a major mess-up that affected many many fedora users. Some
> of which got their system broken beyond repair (maybe because they lack
> knowledge to repair it , i dont know)
>
> I do not understand how this could have happened. Does this go to
> Fedora-testing repository first? Does it not need karma first?
>
> How could a change with such great impact make it into Fedora 20 in the
> first place. This is not rawhide.
>
> Anyways yes bad publicity for SELinux but then again, this is Fedora and
> we (should) know that this can happen...
>
>
>
> --
> selinux mailing list
> selinux(a)lists.fedoraproject.org
>
https://admin.fedoraproject.org/mailman/listinfo/selinux