188275 2007-08-09 22:02 0000 dev-java/jdom missing jaxen-1.1 DEPEND 2007-10-18 14:05:49 0000 1 1 1 Unclassified Gentoo Linux Ebuilds unspecified x86 Linux RESOLVED FIXED https://overlays.gentoo.org/svn/proj/java/java-experimental/dev-java/jdom-jaxen KEYWORDREQ P2 normal --- 1 denisr@websurfer.co.za java@gentoo.org denisr@websurfer.co.za 2007-08-09 22:02:58 0000 * jaxen detected - building jaxen support. * you can ignore the warnings below * one day there will be better solution * The ebuild is attempting to use jaxen-1.1 that is not declared in DEPEND. * Because you have this package installed the package will * build without problems, but please report this to * http://bugs.gentoo.org * The ebuild is attempting to use jaxen-1.1, without specifying --build-only, that is not declared in RDEPEND or PDEPEND. * The package will build without problems, but may fail to run * if you don't have jaxen-1.1 installed, so please report * this to http://bugs.gentoo.org Reproducible: Always Steps to Reproduce: 1. emerge -av dev-java/jdom 2. 3. Actual Results: It produces that message, and also the package seems never to emerge right, because each time i do emerge -av -uDN world, it is always there (as if it was not properly installed last time ) betelgeuse@gentoo.org 2007-08-10 10:05:52 0000 ali_bush: Is the work in https://overlays.gentoo.org/svn/proj/java/java-experimental/dev-java/jdom-jaxen what state to be merged? ali_bush@gentoo.org 2007-08-11 02:36:25 0000 Yes I do believe it is ready for the tree. =dev-java/jdom-1.0_beta9-r3 =dev-java/jdom-jaxen-1.0_beta9-r1 Who would like to do the honours of keywording ~x86 and adding to the tree. ali_bush@gentoo.org 2007-09-16 08:38:28 0000 I have just added to the tree 3 jdom ebuilds and 3 jdom-jaxen ebuilds (One for each existing slot). Arch's please rekeyword the following jdom ebuilds =jdom-1.0_beta10-r5 =jdom-1.0_beta9-r4 =jdom-1.0-r3 and the 3 new jdom-jaxen ebuilds that are PDEPEND'ed from jdom. Please use http://www.gentoo.org/proj/en/java/getting-involved.xml#doc_chap1 for help on testing as well as emerge -C jaxen jdom after each jdom slot has been tested. Thank you tester. ali_bush@gentoo.org 2007-09-24 09:49:48 0000 Ignore the latest post, just after I posted it I discovered I'd missed something. So here I go for good. I have just added to the tree 3 jdom ebuilds and 3 jdom-jaxen ebuilds (One for each existing slot). Arch's please rekeyword the following jdom ebuilds =jdom-1.0_beta10-r6 =jdom-1.0_beta9-r5 =jdom-1.0-r4 and the 3 new jdom-jaxen ebuilds that are PDEPEND'ed from jdom. (One for each slot) Please use http://www.gentoo.org/proj/en/java/getting-involved.xml#doc_chap1 for help on testing as well as emerge -C jaxen jdom after each jdom slot has been tested. Thank you testers. fauli@gentoo.org 2007-09-24 11:13:46 0000 x86 stable fauli@gentoo.org 2007-09-24 11:14:26 0000 (In reply to comment #5) > x86 stable Of course not, it has been keyworded. ali_bush@gentoo.org 2007-10-05 08:42:21 0000 bumping keyword request for outstanding ppc and ppc64 arch's corsair@gentoo.org 2007-10-09 14:01:41 0000 added ~ppc64 nelchael@gentoo.org 2007-10-18 14:05:49 0000 Marked ~ppc.