Red Hat Bugzilla – Bug 186332
Last modified: 2007-11-30 17:11:27 EST
Description of problem:
Transaction Check Error: file /etc/named.conf from install of
bind-9.3.2-12.FC5 conflicts with file from package caching-nameserver-7.3-5.FC5
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. yum update
This is very strange - this problem does not occur for me.
I just double checked this on a clean installed FC-5 system by doing
# yum update
The bind-*9.3.2-4.1 packages were correctly updated to bind-*9.3.2-12.FC5,
and the caching-nameserver package was correctly obsoleted by bind-config.
bind-config now 'Obsoletes: caching-nameserver', and takes over ownership of
the $ROOTDIR/etc/named.conf file. The bind package only owns named.conf as
a %ghost file, as does bind-config, to prevent named.conf being removed by
previous versions of the package which Provide: named.conf.
What was the command you used to update bind ?
If it was yum, do you have 'obsoletes=1' in /etc/yum.conf or an active
/etc/yum.repos.d/*.repo file ?
The default yum configuration specifies 'obsoletes=1' and would avoid this
You will not get this problem if you included bind-config in the list of
packages to be updated, or if you use a current version of yum with the
'obsoletes=1' processing enabled.
This problem has been cleared up. I now am able to 'yum update'. I have been
updating all other packages other then bind and related updates. Today it works.
obsoletes=1 is set in /etc/yum.conf
[user@host ~]$ rpm -qa|grep bind
Good - glad to see the problem has been resolved.