Bug 206097

You need to install caching-nameserver package....

Having caching-namserver doesn't seem to make a difference:

[root@localhost Mike]# rpm -q caching-nameserver
caching-nameserver-9.3.2-33.fc5
[root@localhost Mike]# yum update
Loading "installonlyn" plugin
Setting up Update Process
Setting up repositories
livna                                                                [1/4]
core                                                                 [2/4]
updates                                                              [3/4]
extras                                                               [4/4]
Reading repository metadata in from local files
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package bind-config.i386 30:9.3.2-20.FC5 set to be updated
--> Running transaction check
--> Processing Dependency: bind = 30:9.3.2-20.FC5 for package: bind-config
--> Finished Dependency Resolution
Error: Missing Dependency: bind = 30:9.3.2-20.FC5 is needed by package bind-config

I already *had* caching-nameserver installed, and it was updated along with bind.

$ rpm -q caching-nameserver
caching-nameserver-9.3.2-33.fc5

What does caching-nameserver have to do with bind-config?

Well, same problem here. Steps to reproduce :
- Install a new FC5 system
- Run "yum update".... *boom*

The problem here is that the initial system has caching-nameserver, which
bind-config-9.3.2-20.FC5.i386.rpm obsoletes :

$ rpm -qp --obsoletes bind-config-9.3.2-20.FC5.i386.rpm 
caching-nameserver  

But this bind-config package requires an exact version of bind which is
available, but since there is also a newer one, yum doesn't list it :

$ rpm -qp --requires bind-config-9.3.2-20.FC5.i386.rpm 
bind = 30:9.3.2-20.FC5
[...]

Installed Packages
bind.i386                                30:9.3.2-4.1           installed
bind-libs.i386                           30:9.3.2-4.1           installed
bind-utils.i386                          30:9.3.2-4.1           installed
Available Packages
bind.i386                                30:9.3.2-33.fc5        updates
bind-chroot.i386                         30:9.3.2-33.fc5        updates
bind-config.i386                         30:9.3.2-20.FC5        updates <- old
bind-devel.i386                          30:9.3.2-33.fc5        updates
bind-libbind-devel.i386                  30:9.3.2-33.fc5        updates
bind-libs.i386                           30:9.3.2-33.fc5        updates
bind-sdb.i386                            30:9.3.2-33.fc5        updates
bind-utils.i386                          30:9.3.2-33.fc5        updates

So... why is bind-config still at 30:9.3.2-20.FC5 instead of 30:9.3.2-33.fc5?

Jess, 

can we remove the bind-config 30:9.3.2-20.FC5 package from updates?

Oh no! caching-nameserver 30:9.3.2-33.fc5 requires "bind = 30:9.3.2-33.fc5"...
but the old bind-config obsoletes it!

Please have the older bind-config removed from the FC5 updates directory, it
should "fix" the problem.

*BUT*

The real issue here is that this bind-config has obsoleted "caching-nameserver"
without any version. If it was made to obsolete only caching-nameserver up to a
certain version, lower than the new re-introduced caching-nameserver, then this
problem wouldn't have existed.

Please try to ALWAYS use a version for the obsoletes tag. Doing otherwise nearly
always asking for trouble.

Please remove bind-config-9.3.2-22.fc5 from updates-testing repository.

bind-config was removed from the updates directory, I missed the
updates-testing, will remove it there too.

And removed from updates-testing.

(In reply to comment #9)
> And removed from updates-testing.

Thanks!

I still have the bind depedency problem. 
What should I do?

Still seeing the problem here too.   I've got a clean FC5 system which has been
running "yum update" every few days and it's been working fine.  Today I started
seeing this "bind-config" error.   It's not clear to me what the problem is or
how to work around it.

You can have two kinds of problems:

1) Your yum randomly hits mirror sites which still have
bind-config-9.3.2-20.FC5.i386.rpm. In this case, sooner or later the problem
will solve itself. Ypu may help it changing the metadata_expire value to for
example 5 (seconds) and try "yum update" for example five times (then restore
the original value, if you want).

2) If that does not help, you may have the rpm database slightly screwed up. I
believe I had this on one of my servers. The following procedure apparently has
solved it. Do a "rpm --rebuilddb". Have patience to let it run (or try "rpm -vv
--rebuilddb" if you like lotsa messages on your screen). Not to make the
situation even worse, you should first backup the rpm database, namely all the
files in /var/lib/rpm catalog. A good page on this operation can be found here:
http://www.rpm.org/hintskinks/repairdb/

I hope that helps.

Errata: "metadata_expire" is controlled from the /etc/yum.conf file.

One can also try "yum clean all" to remove all headers, metadata and packages.
Otherwise, if the package is still "seen", then "yum update
--exclude=bind-config" should work as a temporary workaround.

For the record, it was pilot error in my case.   Our internal mirror was out of
space and only partially updated.  After I pointed my configuration to the
current  public mirror, it worked as expected.