This happens with both RPM 3.0.5 and RPM 4.0.0-0.59. rpm -F doesn't add packages that are Required: among the upgrade/install list. An example: samba-2.0.3-8 installed. Running 'rpm -F *.rpm' in directory containing: --- -rw-rw-r-- 1 pekkas pekkas 1744775 Sep 27 1999 samba-2.0.5a-12.i386.rpm -rw-rw-r-- 1 pekkas pekkas 434243 Sep 27 1999 samba-client-2.0.5a-12.i386.rpm -rw-rw-r-- 1 pekkas pekkas 343001 Sep 27 1999 samba-common-2.0.5a-12.i386.rpm --- Causes the message: --- error: failed dependencies: samba-common = 2.0.5a is needed by samba-2.0.5a-12 --- Apparently RPM does not examine 'Provides:', 'Requires:' etc. headers at all (or not soon enough) and dependecies fail because RPM won't install samba-common. This is an essential feature and should definitely be included.
FWIW, "rpm -F ..." has never added other packages, so this is a RFE.
True, thus 'enhancement'. :)
Getting closer to a chance to implement, but up2date is the cat's pajamas at the moment (sigh)
up2date does not completely solve this problem - what if I want to upgrade from some custom list of packages (and some of them may be local or 3rd party)?
bash$ sudo rpm -Uvh curl-devel-7.9.5-2.i386.rpm warning: curl-devel-7.9.5-2.i386.rpm: Header V3 DSA signature: NOKEY, key ID 897da07a error: Failed dependencies: curl = 7.9.5-2 is needed by curl-devel-7.9.5-2 Suggested resolutions: curl-7.9.5-2.i386.rpm bash$ rpm --version RPM version 4.1 There's more to do of course