On Fri, 19 Jun 2015 09:01:43 +0200 Nicolas Thierry-Mieg <Nicolas.Thierry-Mieg at imag.fr> wrote: > You are correct, but what "more info" do you want? Well, a list of names of those conflicting packages would be nice to have. Or instructions how to ask yum to compile it. > You've spelled it > out quite well, you have the solution (set the lowest prio == highest > value for epel), end of story? Unfortunately, it isn't. I was running the machine for some time without having the yum-priorities plugin. I (naively) believed that EPEL is careful not to create conflicts against base (I have read on this very list that it's safe to use). Stuff got installed, updated several times over, etc. Now after I figured there are in fact conflicts, I need to figure out the consistency of the software installed on my machine. How many (and which) packages from base have been stepped over by epel on my system? How severe are the consequences? I need to know how affected my system is, which packages to reinstall (now that I've activated priorities), etc. It's a mess that needs to be cleaned up. > If you want it fixed you should report this to EPEL, not here. But > with a large repo like EPEL this is bound to happen again and again > as the distrib is a moving target. yum priorities mostly solves it. No, I don't really care to have it fixed, yum-priorities can take care of that in the future. But I want to fix my server, to make sure that all packages from base are still there. And I also want to make some noise about it on this list, so that other people don't end up with the same problem. It should be stated clearly that epel is *not* safe to use without the priorities plugin. Best, :-) Marko