Borsenkow Andrej <[EMAIL PROTECTED]> writes: > One of annoying "features" of rpmdrake is that it completely ignores > errors during RPM installation phase - i.e. such things like bad RPM or > missing depndencies and removes all packages from list assuming they > have been installed. > > Unfortunately it turned out not to be easy to fix. grpmi calls > rpmRunTransactions and relies on it to return a list of problems during > install. Now rpm does not always returns something meaningful. It does > it in such cases like out of space or missing dependencies but does not > if you have corrupted RPM or in case of *any* other error during actual > installation. To test just truncate any RPM and see - you get just > overall "installation failed" status without any more detailed > information which RPM failed.
What could be done is to examine what has been installed, and to update according to what should have been installed. Fran�ois.
