The java-gnome ebuilds need to be version bumped as follows: glib-java 0.2.2 -> 0.2.3 libgtk-java 2.8.2 -> 2.8.3 libglade-java 2.12.1 -> 2.12.2 the others stay the same. You'll naturally want to update the java-gnome meta ebuild to 2.12.3 as well. Note that both libgtk-java 2.8.2 and 2.8.3 *need* >= glib-java 0.2.2 ; libgtk-java's configure doesn't enforce that requirement which leeds to messy bugs if [at least] glib-java 0.2.2 isn't present. AfC (Upstream release maintainer)
In portage. Please sync and test in ~2 hours.
It's fine, except that there's a problem that the jar symlinks are missing from when I was maintaining these ebuilds. Upstream expects jars to be properly installed and certain symlinks are missing, as follows: /usr/share/glib-java-0.2/lib/glib0.2.jar -> glib-java-0.2.3.jar /usr/share/cairo-java-1.0/lib/cairo1.0.jar -> cairo-java-1.0.2.jar /usr/share/libgtk-java-2.8/lib/gtk2.8.jar -> libgtk-java-2.8.3.jar /usr/share/libgnome-java-2.12/lib/gnome2.12.jar -> whatever /usr/share/libglade-java-2.12/lib/gldae2.12.jar -> libglade-java-2.12.2.jar /usr/share/libgconf-java-2.12/lib/gconf2.12.jar -> whatever You can rename the actual jars to whatever you want, but you need to put the jar names in that upstream projects are expecting or they'll never find them. Changing the JAR names before java-gnome 3.x represents an ABI breakage and violates the GNOME release policies that we have to follow. AfC
(as an alternative, you could just restore the symlinks as installed by the java-gnome meta package. I know there are some people out there who are just relying on /usr/share/java-gnome/lib/gtk2.8.jar and so on. I'd prefer the individual symlinks per package be fixed, but this could be an option for you) AfC
Should be fixed now with -r1 of the java-gnome packages.
