Hide Forgot
Description of problem: bash-3.1# rpm -q bind bind-9.3.2-12.FC5 bash-3.1# rpm -i caching-nameserver-7.3-5.FC5.noarch.rpm file /etc/named.conf from install of caching-nameserver-7.3-5.FC5 conflicts with file from package bind-9.3.2-12.FC5 Version-Release number of selected component (if applicable): bind-9.3.2-12.FC5 caching-nameserver-7.3-5.FC5.noarch.rpm rpm-4.4.2-15.2 How reproducible: Always Steps to Reproduce: 1. install bind 2. try to install caching-nameserver Actual results: Inability to install caching-nameserver due to a file conflict Expected results: caching-nameserver succesfully installed Additional info: bind is from fc5 updates
The caching-nameserver RPM is now obsoleted by the bind-config package, which 'Provides: caching-nameserver'. If you obtained bind-9.3.2-12.FC5 via a 'yum update' command, then caching-nameserver would be correctly 'obsoleted' by bind-config. You do not need to install caching-nameserver if you have bind-config installed.
*** Bug 187729 has been marked as a duplicate of this bug. ***
I'm still seeing this problem. Essentally the update path from a vanilla FC-5 to the current FC-5 updates in Core, Updates and Extras. On a vanilla system: # rpm -q bind bind-9.3.2-4.1 # rpm -q caching-nameserver caching-nameserver-7.3-5.FC5 # rpm -qf /etc/named.conf caching-nameserver-7.3-5.FC5 Trying to update: # yum -y update [...] bind x86_64 30:9.3.2-33.fc5 updates 941 k [...] Transaction Check Error: file /etc/named.conf from install of bind-9.3.2-33.fc5 conflicts with file from package caching-nameserver-7.3-5.FC5 The problem is that bind-config is not part of the vanilla install, and therefore doesn't get a chance to Obsolete caching-nameserver. I'm guessing the answer is having bind Requires: bind-config ?
*** This bug has been marked as a duplicate of 207322 ***