[CentOS] Yum issue on CentOS 5, x86_64

Mon Apr 16 22:16:36 UTC 2007
Styma, Robert E (Robert) <stymar at alcatel-lucent.com>

I just loaded CentOS 5 on a new x86_64 machine
I built for my wife.  I am converting her from
the dark $ide. :-)

I started getting the following messages from yum:

]: yum update
Loading "installonlyn" plugin
Setting up Update Process
Setting up repositories
Reading repository metadata in from local files
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package subversion.x86_64 0:1.4.3-0.1.el5.rf set to be updated
--> Running transaction check

Dependencies Resolved

========================================================================
=====
 Package                 Arch       Version          Repository
Size 
========================================================================
=====
Updating:
 subversion              x86_64     1.4.3-0.1.el5.rf  rpmforge
4.4 M

Transaction Summary
========================================================================
=====
Install      0 Package(s)         
Update       1 Package(s)         
Remove       0 Package(s)         

Total download size: 4.4 M
Is this ok [y/N]: y
Downloading Packages:
Running Transaction Test
Finished Transaction Test


Transaction Check Error:
  file /usr/share/emacs/site-lisp/psvn.el from install of
subversion-1.4.3-0.1.el5.rf conflicts with file from package
subversion-1.4.2-2.el5
  file /usr/share/xemacs/site-packages/lisp/psvn.el from install of
subversion-1.4.3-0.1.el5.rf conflicts with file from package
subversion-1.4.2-2.el5

Error Summary
-------------

[styma14]: rpm -e subversion-1.4.2-2.el5
error: "subversion-1.4.2-2.el5" specifies multiple packages
[styma14]: rpm -qa | grep subversion
subversion-1.4.2-2.el5
subversion-1.4.2-2.el5

######################################
It appears I have a package installed twice.  I tried the
normal "rpm is damaged" sequence of:


rm -f /var/lib/rpm/__db*
db_verify /var/lib/rpm/Packages
rpm --rebuilddb

But that did not help the situation.  Are there any suggestions on how
to get
rid of this one piece and get past this error?  I tried a -f on the rpm
-e and it
failed the same way.

Bob Styma