i just tried doing a "yum update" on a system that's somewhat behind in terms of updates (0.94 release), and after much disk activity, i got: Gathering header information file(s) from server(s) Server: Red Hat Linux 0.94 - i386 - Base Server: Red Hat Linux 0.94 - Updates Finding updated packages Downloading needed headers Resolving dependencies ....identical dependency loop exceeded package dbus-qt needs dbus = 0.11.91 (not provided) a quick check shows that the yum repository has 4 dbus-related RPMS, while the local system has 5 -- the additional one being dbus-qt, which is not represented in the repository and which is clearly the cause of the problem. i have no idea from where came dbus-qt, which raises a number of questions: 1) is this an oversight on the part of the repository? or did someone manually add the dbus-qt RPM to this local system which is messing up the yum update? 2) can i assume that, if any kind of update problem is detected, nothing will be done to the local system and the entire update will be abandoned? 3) does yum have some sort of "--test" or "--dry-run" option? the man page makes no mention of such a feature. rday