Red Hat Bugzilla – Bug 159008
preun script failure while removing sets of packages leads to unmet dependencies
Last modified: 2007-11-30 17:07:18 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 SUSE/1.0.4-1.1
Description of problem:
If package A requires package B, and both are installed, and you attempt to remove both at once using rpm --erase, and A's preun script fails, B will still be removed, which leaves A installed and B not installed. Since A requires B, this situation should not occur.
As an example, on RHEL 4AS, there are several packages that depend on metacity, one of which is firstboot. If you use rpm --erase to remove these packages all at once, metacity's removal will succeed, but firstboot's preun scriptlet fails. At the end of the transaction, metacity has been removed, but firstboot remains.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. On a stock RHEL 4AS install, run the following command as root: rpm --erase gnome-volume-manager gnome-session control-center system-config-display firstboot metacity
2. Run the following command: rpm -q firstboot metacity
Actual Results: During step 1, firstboot's preun script failed. Step 2 returned the following output:
package metacity is not installed
Expected Results: RPM should have attempted to uninstall firstboot BEFORE uninstalling metacity. Since firstboot could not successfully be removed, RPM should have refused to remove metacity.
RPM in RHEL has never done sorted erasures based on requirements.
Work is going on in Fedora and rpm-4.4.x/HEAD atm to get sorted erasures working.
*** This bug has been marked as a duplicate of 89500 ***