Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!

Full Text Bug Listing

* 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 )

ali_bush: Is the work in 
https://overlays.gentoo.org/svn/proj/java/java-experimental/dev-java/jdom-jaxen
what state to be merged?

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.

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.

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.

x86 stable

(In reply to comment #5)
> x86 stable

 Of course not, it has been keyworded.

bumping keyword request for outstanding ppc and ppc64 arch's

added ~ppc64

Marked ~ppc.