I did a "yum groupremove Java" and that failed "somehow". Yum listed all group members as "erased", but some rpm packages failed because of missing config files or so. As a result none of the 50 packages were removed from the rpm database, but all of their files seem to have been removed. How can I clean them out from the rpm db?
Kai
On Wed, 2008-03-26 at 01:09 +0100, Kai Schaetzl wrote:
I did a "yum groupremove Java" and that failed "somehow". Yum listed all group members as "erased", but some rpm packages failed because of missing config files or so. As a result none of the 50 packages were removed from the rpm database, but all of their files seem to have been removed. How can I clean them out from the rpm db?
---- rpm -e --justdb some_package
rpm --help
Craig
Craig White wrote on Tue, 25 Mar 2008 17:26:04 -0700:
rpm -e --justdb some_package
I had hoped for a solution that "automagically" removes those 50 packages. Thanks, anyway, I'll dig up all the packages from the yum log and try it.
rpm --help
It's easy to overlook functionality in that long list :-(
Kai
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
-
Craig White -
Kai Schaetzl