Les Mikesell wrote: > On Tue, Sep 2, 2014 at 11:24 AM, Michael Lampe <mlampe0 at googlemail.com> wrote: >>> >> What about some kind of preconfigured protection of base repositories? Epel >> doesn't live up to their own standards of not replacing system packages: >> >> # yum -d3 update | grep epel >> >> --> advancecomp-1.19-1.el7.x86_64 from epel excluded (priority) > (etc.) > > Isn't this something that should really be automated with some kind of > scanning at the repository level (for both package and file name > conflicts)? > What if some package from epel gets included by RH with an update? This happened several times in the past and epel always kept their package available, even if had a higher version number than the now official RH package. -Michael