Red Hat Bugzilla – Bug 475183
yum erase cause problem when solving dependencies
Last modified: 2008-12-08 10:18:02 EST
Created attachment 326119 [details] yum erase zip - log Description of problem: Problems appeared on various system, not only ia64, but there it had problems when install software back. When uninstalling program "zip" many bugs in uninstalling process. It causes, that tomcat5 cannot be installed back. It seems to be /usr/bin/rebuild-gcj-db (java-1.4.2-gcj-compat) missing, because gcj is uninstalled before should be uninstalled. Problems are in dependencies solving erase process. It isn't problem only tomcat5 application suite, but various java applications. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. yum install tomcat5 2. yum remove zip 3. yum install tomcat5 then try package-cleanup --problem commnad and you shlould se unsolved dependencies for tomcat5. Tomcat is already installed. Actual results: >> logs in attachment on i386 (without problems with install back) Running Transaction Erasing : libgcj [ 1/40] warning: /usr/lib/security/classpath.security saved as /usr/lib/security/classpath.security.rpmsave Erasing : tomcat5-common-lib [ 2/40] /usr/bin/rebuild-gcj-db: line 6: /usr/bin/gcj-dbtool: No such file or directory dirname: missing operand Try `dirname --help' for more information. mkdir: missing operand Expected results: without problems when erasing packages Additional info:
Created attachment 326120 [details] yum install tomcat5 - log
Created attachment 326121 [details] package-cleanup --problem - log
So this bug is about the ordering of the erase transaction, yes? What is getting erased, and what needs to be erased for dependencies ... is correct? Reassigning to rpm, if I've screwed up what the problem is ... please assign back.
Yes, I thing, problem is, that yum do not resolve dependencies in right way. java-1.4.2-gcj-compat should be erased at the end, not before uninstalling tomcat or other java libraries.
*** This bug has been marked as a duplicate of bug 448153 ***
The packages looks right, it has: Requires(post): java-gcj-compat >= 1.0.31 Requires(postun): java-gcj-compat >= 1.0.31 ...which is provided by java-1.4.2-gcj-compat-1.4.2.0-40jpp.115, which provides /usr/bin/rebuild-gcj-db.