On 09/02/2014 05:37 PM, 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)? > yes it should be possible to automate this test, lets see if we can have a go. -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc