On Sun, November 2, 2014 21:40, Peter wrote:

On 11/03/2014 02:35 PM, reynierpm@gmail.com wrote:

...

Transaction Check Error: file /usr/lib64/libevent-2.0.so.5 from install of libevent-2.0.19-1.rhel6.x86_64 conflicts with file from package libevent-last-2.0.21-4.el6.remi.x86_64 file /usr/lib64/libevent_core-2.0.so.5 from install of libevent-2.0.19-1.rhel6.x86_64 conflicts with file from package libevent-last-2.0.21-4.el6.remi.x86_64 file /usr/lib64/libevent_extra-2.0.so.5 from install of libevent-2.0.19-1.rhel6.x86_64 conflicts with file from package libevent-last-2.0.21-4.el6.remi.x86_64

remi is known to mess things up like that if you don't install it properly. First thing I would do is "yum remove remi-release" unless you have something you specifically need the remi repo for, then I would try this:

I would start by setting enable=0 for all of the repos inside remi.repo and then only using remi with the --enablerepo=remi --enablerepo=remi-whatever. I do not think it wise to have remi enabled by default. But, neither do I think it necessary to remove the repo altogether. Turning it off by default should suffice.

Then remove whatever packages are causing causing the conflict as is suggested. The remi.repo need not be enabled to effect removals. Then try your update with remi out of the picture.