This is an FYI bug. The java-gnome project has released a bug fix to the stable branch of libgtk-java, upgrading 2.4.6 to libgtk-java-2.4.7. It, however, has a mis-applied patch, and so fails to compile. I'm working with upstream and when we get a patch I'll back port it to a libgtk-java-2.4.7 ebuild until 2.4.7.1 (or whatever) is released. AfC Sydney
Updated ebuilds are at http://www.operationaldynamics.com/reference/software/gentoo/ specifically, http://www.operationaldynamics.com/reference/software/gentoo/java-gnome-2.8.2-r3_ebuilds.tar.gz Unpack that in a Portage CVS checkout, and it should be good to go. Specific updates are libgtk-java (now 2.4.7.2 upstream), libglade-java (now 2.8.2.2 upstream), and the java-gnome meta task ebuild (my revision at java-gnome-2.8.2-r3). The ChangeLogs should be alright. Your JNI fix of a few weeks ago is there, but I reverted the patches to specifically naming 2.4.6 as I don't want to have to copy and rename the patches for every bloody minor revision. Next major release I'll clean up the names of the enduring patches. AfC Sydney
commited (hope i didn't miss anything) few realy minor notes: had to do the jni thing in all of the them metadata.xml follows a _very_ strict(stupid?) dtd yours weren't valid changelog format's veren't exactly correct (echangelog can help, but i guess you need cvs access for that?) javadoc was broken in java-gnome
Thanks Thomas. Ebuilds as committed work fine here. As this is a bug fix update to the 2.8 stable release branch, I want to get all five ebuilds marked x86 quickly. AfC Sydney
