Clint Adams wrote:
On Thu, Mar 11, 2010 at 03:42:54PM -0500, Gary Dale wrote:
Except that dpkg is trying to do something with it during the
lbidb4.7-java-gcj update.
Yes. libdb4.7-java-gcj calls /usr/bin/rebuild-gcj-db which is
a script that is part of the libgcj-common package. rebuild-gcj-db
in turn goes through and looks for gcj-dbtool-4.2, gcj-dbtool-4.3,
and gcj-dbtool-4.4. It runs each one it finds.
In your case, it is obviously finding gcj-dbtool-4.2, so it is
running it. You have already established that gcj-dbtool-4.2 is
not associated with any associated package. It is this mysterious
gcj-dbtool-4.2 in your PATH, missing its library dependency, which
is the cause of your problem.
I gather it is in one or more scripts associated with the
libdb4.7-java-gcj package since I'm getting messages related to that
package immediately before and after the gcj-dbtool-4.2 error. Moreover,
dpkg seems to be saying that the program is referenced in both the old
and new packages.
See above.
All I know is that has just started happening and it's preventing me
from installing the Squeeze updates.
The source of you having a gcj-dbtool-4.2 despite the package not
being installed is the mystery that needs to be solved.
The gcj-dbtool-4.2 seems to be part of Lenny's gij-4.2 package. There is
a similarly named package gcj-dbtool in Squeeze that is part of
gcj-jre-headless & gcj-4.4-jre-headless. I'm guessing that somewhere in
the updates from Lenny to Squeeze something got messed up. The question
is, how do I fix it?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
