On 06/05/2014 02:56 PM, Stefan Lasiewski wrote: > I just noticed that some of my Scientific Linux servers appear to have > duplicate Yum .repo under /etc/yum.repos.d/ : > > ``` > [root@ hostb yum.repos.d]# pwd > /etc/yum.repos.d > [root@ hostb yum.repos.d]# ls -ld sl*repo > -rw-r--r--. 1 root root 1837 Feb 20 2012 sl6x.repo > -rw-r--r--. 1 root root 1209 Feb 6 16:11 sl-other.repo > -rw-r--r--. 1 root root 1014 Feb 6 16:11 sl.repo > [root@ hostb yum.repos.d]# > ``` > > Should my systems have both `sl.repo` and `sl6x.repo`, or will these > conflict with each other? > > I don't understand why the file sl6x.repo was installed at all, but it > appears that both sl-release & yum-conf-sl6x were installed at install > time, possibly as part of the @Base or the @Core group. > > [root@staffdb02 yum.repos.d]# rpm -q --file /etc/yum.repos.d/sl6x.repo > yum-conf-sl6x-1-2.noarch > [root@staffdb02 yum.repos.d]# rpm -q --file /etc/yum.repos.d/sl.repo > sl-release-6.5-1.x86_64 > [root@staffdb02 yum.repos.d]# > > > Thank you, > > -= Stefan >
Scientific Linux traditionally kept you on the point release you initially installed (e.g. 6.x). This is different from RHEL, which by default points to a repository containing the latest packages for the latest point release, keeping you up to date without needed to manually adjust the repository info. The yum-conf-sl6x package provides RHEL like behaviour for updates. Brandon Vincent
