On Fri, Apr 3, 2009 at 12:47 PM, MHR <mhullrich at gmail.com> wrote: > 2009/4/2 Ron Blizzard <rb4centos at gmail.com>: >> >> >> 2009/4/2 Ralph Angenendt <ra+centos at br-online.de> >>> >>> Why should we list rpmforge packages in the Release Notes? exclude >>> subversion from base if you want to use the one from rpmforge because it >>> is newer - and remove gstreamer-plugins-bad, because it shares some >>> files with gstreamer-plugins-good from from the base repository. >> >> That was my only issue with on my laptop upgrade. All I did was... >> >> # yum remove gstreamer-plugins-bad >> >> ...and then re-ran the upgrade. >> > > I'm going to blame my failing eyesight for this one. I removed both > the bad and the ugly, and everything worked fine. > > Now I need to remember to put them back.... > > GREAT JOB AND THANKS FOR ALL THE HARD WORK! > > I can't tell you how pleased I am with all of CentOS, bug and my own > stupidity notwithstanding. Now I'm ready to update my laptop. I have a problem with gstreamer-plugins-good update on three x86_64 boxes and none of them ever had any third party rpm packages except my home built openssh-5.2. I finally solved it by doing rpm -Uvh in the following files in order: gstreamer-tools-0.10.20-3.el5.x86_64.rpm gstreamer-0.10.20-3.el5.i386.rpm gstreamer-0.10.20-3.el5.x86_64.rpm gstreamer-plugins-base-0.10.20-3.el5.i386.rpm gstreamer-plugins-base-0.10.20-3.el5.x86_64.rpm >From there the update went smoothly on the test box. Whatever caused this only seems to affect x86_64 machines. -- Stephen Carville