Bug 177257

Something's wonky with your rebuild-gcj-db.  What version of
java-1.4.2-gcj-compat do you have?

That's what I thought. I am using jpackage 0:1.4.2.0-40jpp_31rh.FC4.2. I may
have broken it crowbaring out an update using force, the post scriptlets were
not working properly. This may also explain a problem I am having with the
eclipse help system, it can't find the logger classes for tomcat.

Hi Herbert,

Could you please attach your /usr/bin/rebuild-gcj-db just to make sure nothing
is messed up there?


Also what version where you upgrading from? Did you already try to remove and
reinstall both eclipses? If so what was the result?

Created attachment 123161 [details]
/usr/bin/rebuild-gcj-db

requested /usr/bin/rebuild-gcj-db from my system attached. 

I am getting out the crowbar again, starting by removing the packages synaptic
tells me are broken,

eclipse-bugzilla	1:0.1.0_fc-16
eclipse-cdt		1:3.0.0_fc-1.FC4
eclipse-changelog	1:2.0.1_fc-21
eclipse-jdt		1:3.1.1-1jpp_1fc.FC4.4
eclipse-pydev		1:0.9.3_fc-7

synaptic can't remove them, the post scriptlets won't run. Error messages are
basically the same as original post, rebuild-gcj-db doesn't run. I will run rpm
by hand with --nopost to force the remove.

I may end up completely tearing out java, and re-installing. I will try to
upgrade to the 06 version of sun java 1.5, if jpackage will get off the dime
and release an upgrade to the sun nosrc package. The sun upgrade has been out
for a month now.

Carl

Yeah, your rebuild-gcj-db is messed up.  I don't know how.  You can copy the
rebuild-gcj-db that I have posted below into yours and hopefully that'll fix up
all the %post{,un} sections.  This is on my updated FC4 system:

[andrew@localhost ~]$ rpm -q java-1.4.2-gcj-compat
java-1.4.2-gcj-compat-1.4.2.0-40jpp_31rh.FC4.2
[andrew@localhost ~]$ rpm -qV java-1.4.2-gcj-compat
..?......   /etc/java/security/security.d/1000-gnu.java.security.provider.Gnu
[andrew@localhost ~]$ md5sum /usr/bin/rebuild-gcj-db
0151e861d78c9e23229a2bfd0a9243d5  /usr/bin/rebuild-gcj-db
[andrew@localhost ~]$ cat !$
cat /usr/bin/rebuild-gcj-db
#!/bin/bash
# rebuild-gcj-db

if [ $# != 0 ]; then
    # we allow the old LIBDIR argument to stop existing rpms from choking.
    if [ $# != 1 -o $1 != /usr/lib ]; then
        cat 1>&2 <<EOF
rebuild-gcj-db: re-build the gcj classmap database

usage: $0
EOF
        exit 1
    fi
fi

dbLocation=`/usr/bin/gcj-dbtool -p /usr/lib`
dirname $dbLocation | xargs mkdir -p
/usr/bin/gcj-dbtool -n $dbLocation 64
locations="$dbLocation.d /usr/lib/gcj"
oldlocation=/usr/lib/gcj-4.0.0/classmap.db.d
if [ $dbLocation.d != $oldlocation -a -d $oldlocation ]; then
    locations="$locations $oldlocation"
fi
find $locations -name '*.db' -print0 | \
    xargs -0 /usr/bin/gcj-dbtool -m $dbLocation $dbLocation

Thank you Andrew, rebuild-gcj-db now works. Yesterday, I removed eclipse
sucessfully. However, when I reinstalled eclipse, the tomcat5 that it pulled in
reported errors:

While installing package tomcat5-5.5.9-1jpp:

/usr/bin/build-jar-repository: error: Could not find jdtcore Java extension for
this JVM
/usr/bin/build-jar-repository: error: Could not find jdtCompilerAdapter Java
extension for this JVM
/usr/bin/build-jar-repository: error: Some specified jars were not found for
this jvm
/usr/bin/build-jar-repository: error: Could not find jdtcore Java extension for
this JVM
/usr/bin/build-jar-repository: error: Could not find jdtCompilerAdapter Java
extension for this JVM
/usr/bin/build-jar-repository: error: Some specified jars were not found for
this jvm

I think this tomcat rpm doesn't understand Java 1.5. Maybe Gary B. has something
to offer.

Eclipse starts, but the help system still doesn't work. See bug #174258.

Thanks, Carl

(In reply to comment #6)
> While installing package tomcat5-5.5.9-1jpp:

This is coming from the JPackage repository.  There are known issues with
interoperability between the Fedora packages and the JPackage packages. 
Fedora's packages are basically a fork of the JPackage ones and there is some
version skew in some places.  I believe this is one of them.

This bug is filed against FC4 which is no longer supported. Please re-test with
FC5 or FC6 and reopen the bug if the problem still exists. Thanks.