Pulled in as dependency from rhino-1.6, all of which have been marked stable on ppc for some reason. rhino-1.5.5-r2 has no problems and does not pull in packages that seem to have been marked stable on ppc for no particular reason. I was not watching closely and believe there are other packages that have been marked stable prematurely. These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild N ] dev-java/dom4j-1.6.1 [ebuild N ] dev-java/jaxen-1.1_beta2-r1 [ebuild N ] dev-java/xml-xmlbeans-20041217 [ebuild NS ] dev-java/rhino-1.6.1-r2
QA issues do not belong under the Developer Relations product; reassigning.
Looking at other arch markings, and Changelogs, all of these looks perfectly fine. Is there some reason you think they were marked stable too quickly? (Do they work?)
Testing it out a bit, I don't see a problem either. David, did you have a problem?
Concur with the comment on "premature." Was this tested on PPC? Expected: Successful completion of each of the following. USE="jikes" emerge =dev-java/jaxen-1.1_beta2-r1 emerge =xml-xmlbeans-20041217 Actual: Failure to build package above packages, as listed. See attached logs. "jaxen" builds OK only without jikes USE. "xml-xmlbeans" does not build at all (jikes not being relevant). Notes: $sudo /bin/su - -c 'java-config -L' [ibm-jdk-bin-1.4.2.03] "IBM JDK 1.4.2.03" (/etc/env.d/java/20ibm-jdk-bin-1.4.2.03) * [ibm-jdk-bin-1.5.0] "IBM JDK 1.5.0" (/etc/env.d/java/20ibm-jdk-bin-1.5.0) [blackdown-jdk-1.3.1] "Blackdown JDK 1.3.1" (/etc/env.d/java/20blackdown-jdk-1.3.1)
Created attachment 83246 [details] Emerge log of jaxen with jikes use flag
Created attachment 83247 [details] Emerge log of xml-xmlbeans.
Created attachment 83248 [details] Emerge info output with sensitive information removed.
xml-beans compiles fine on my stable ppc system, the problem you're having is the same as with lots of other java packages: IBM's java does not work correctly with utf8 locales. Sorry, but it's a known issue. http://bugs.gentoo.org/show_bug.cgi?id=93649 jaxen with jikes enabled is the only package and option that I can reproduce any issues with and I'll look into fixing it. You can use /etc/portage/package.use to disable jikes for this one package for now.
(In reply to comment #8) > xml-beans compiles fine on my stable ppc system, the problem you're having is > the same as with lots of other java packages: IBM's java does not work > correctly with utf8 locales. Too bad that the following produces identical failure: # LC_ALL="C" emerge xml-xmlbeans Mind sharing what your JVM setup on PPC is? blackdown-jdk is hard-masked for PPC now, as deprecated, so if you're using that, then the issue of these packages not really being stable remains.
As I said above, I've got a stable ppc system that I'm testing on, with the default locales (no changes). I'm using ibm's jdk 1.4.2.03, (the stable version).
OK. Solution for users with unicode locale. (Probably anyone outside the USA and many inside, including myself, which is why this is so important for 'stable' packages.) echo 'unset LC_ALL' > /etc/portage/bashrc emerge xml-xmlbeans echo '' > /etc/portage/bashrc Why doesn't this work? LC_ALL="C" emerge xml-xmlbeans See new bug 128420 . http://bugs.gentoo.org/show_bug.cgi?id=128420 Digression: http://bugs.gentoo.org/show_bug.cgi?id=93649 This says that version 1.4.2.03 fixes the unicode issue. # java -version java version "1.4.2" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2) Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxppc32142ifx-20060209 (SR4-1) (JIT enabled: jitc)) # epm -qGa | grep ^dev-java | wc -l 56 And xml-xmlbeans rhino-1.6* are the only java packages requiring a portage hack. Hmm... (Rhino requires the locale hack with, or without, jikes, which in my mind, indicates crappy software coding, seeing that two compilers fail. Really should be ~ppc.)
well, jdom-1.0 also has this issue. Is it related to the others? For grins, I re-emerge all java packages on my system. Of ~60 packages, only these packages have locale issues: jdom-1.0 rhino-1.6* xml-xmlbeans
Don't really see a QA problem here.
closing -- the locales problem seemed to be the main complaint, and fixed versions of ibm sdk have been stable on ppc for some time now.
