Description of problem:  Installed the latest version of bind and bind-chroot from updates-testing.  After they were installed, the named demon failed.  It wouldn't start because the new bind had a dependency that wasn't installed, that it didn't pull in.  I had to change configuration on eth0 to get a link back.  Then I updated bind-utils and bind-sdb to the latest versions, and everything worked again.


Version-Release number of selected component (if applicable):
bind-9.8.1-1.fc15.src.rpm

How reproducible:
I only did it once, but I assume every time

Steps to Reproduce:
1. Update bind-chroot, bind
2. 
3.
  
Actual results:
Named fails

Expected results:
Pulls in the required dependency for libraries, and named works fine.

Additional info:  A few years ago, I used to run Rawhide regularly.  Because of all the dependency errors that occur in Rawhide, I developed scripts that updated packages individually given a list of updates in a file from yum list updates command.  That way, I could install everything without errors and save error messages, especially dependency errors, to be reported.  I continue to run updates using those scripts.  In this case, it was installing bind-chroot, and pulled in bind as a dependency, but failed to pull in all the required dependencies.  I didn't save the actual error when I tried to restart named manually, but it was something about a lib not being accessible; I think it was something like libicss.  After I installed the other packages, which don't have any libs in them, everything worked.  Both of them access libs like that, so possibly both are necessary dependencies.