Re: [SLUG] messed up yum update

2013-12-14 Thread Ben Donohue
I always first run... yum update yum Just in case there are fixes to yum that are needed. Otherwise I would completely uninstall and possibly reboot. (years of windows training... ;-) Ben On 15/12/13 09:49, li...@sbt.net.au wrote: Content preview: I have a centos system, getting

Re: [SLUG] messed up yum update

2013-12-14 Thread Gavin Carr
You generally shouldn't have both epel and rpmforge enabled, as they'll frequently conflict. Try disabling one or other (set enabled=0 in the relevant repo file in /etc/yum.repos.d) and try it again. You can also test by doing 'yum update --disablerepo=rpmforge' or 'yum update

Re: [SLUG] messed up yum update

2013-12-14 Thread lists
On Sun, December 15, 2013 11:39 am, Gavin Carr wrote: Gavin, Ben, thanks You generally shouldn't have both epel and rpmforge enabled, as they'll frequently conflict. Try disabling one or other (set enabled=0 in the relevant repo file in /etc/yum.repos.d) and try it again. You can also test

Re: [SLUG] messed up yum update

2013-12-14 Thread lists
Complete! except for getting a 'damaged xml' message, I might check on iredmail for solution, thanks again for the pointers : # yum clean all Loaded plugins: fastestmirror, priorities Cleaning repos: base epel extras iRedMail updates Cleaning up Everything Cleaning up list of fastest mirrors