Kai Schaetzl wrote on Wed, 26 Mar 2008 12:31:16 +0100: > I'll dig up all the packages from the yum log and try it. That still fails for a few packages because of the order I got from the log. I was able to erase all of them from the rpm db now. But the whole thing very much looks like a bug, or actually two bugs, in the uninstallation procedure. I now got the errors again that I had neglected to write down earlier. rpm -e tomcat5-common-lib-5.5.23-0jpp.3.0.2.el5.i386 /var/tmp/rpm-tmp.89407: line 1: /usr/bin/rebuild-gcj-db: No such file or directory error: %postun(tomcat5-common-lib-5.5.23-0jpp.3.0.2.el5.i386) scriptlet failed, exit status 127 rpm -e tomcat5-jsp-2.0-api-5.5.23-0jpp.3.0.2.el5.i386 /var/tmp/rpm-tmp.32859: line 5: /usr/bin/rebuild-gcj-db: No such file or directory error: %postun(tomcat5-jsp-2.0-api-5.5.23-0jpp.3.0.2.el5.i386) scriptlet failed, exit status 127 rpm -e tomcat5-servlet-2.4-api /var/tmp/rpm-tmp.99715: line 5: /usr/bin/rebuild-gcj-db: No such file or directory error: %postun(tomcat5-servlet-2.4-api-5.5.23-0jpp.3.0.2.el5.i386) scriptlet failed, exit status 127 in consequence some other packages could not be removed because of dependencies To me that looks like two bugs: 1. several packages all want to remove the same file that obviously got already removed by another package in the chain 2. the postuninstall scriptlet lets the whole erase procedure fail because of a missing file, I think that's rather drastic If that is a bug, where to report? Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com