Is it OK to stabilize =dev-java/mx4j-core-3.0.2 ? If so, please CC arches and add STABLEREQ keyword. Stabilization of this package has been repoman-checked on the following arches: x86, amd64
Maintainer timeout, arches go ahead.
I guess are needed other dev-java/mx4j-*-3.0.2 @java what do you say ?
(In reply to comment #2) > I guess are needed other dev-java/mx4j-*-3.0.2 > > @java what do you say ? Indeed it would make more sense to try stabilize the meta dev-java/mx4j-3.0.2 as a whole.
@java: The following keyword changes are necessary to proceed: #required by dev-java/mx4j-3.0.2[examples], required by dev-java/mx4j (argument) >=dev-java/jython-2.5.1-r2 ~amd64 #required by dev-java/mx4j-3.0.2[examples], required by dev-java/mx4j (argument) >=dev-java/hessian-4.0.3 ~amd64 are ready to stabilize?
Re-add amd64 when bug 379283 is fixed and when you're ok to stabilize also the others packages ~arch pulled by mx4j
Looks like jython-2.5.1 is full of bugs which are fixed in jython-2.5.2. A version bump before stabilizing would likely make sense.
*** Bug 396879 has been marked as a duplicate of this bug. ***
*** Bug 396881 has been marked as a duplicate of this bug. ***
(In reply to comment #6) > Looks like jython-2.5.1 is full of bugs which are fixed in jython-2.5.2. A > version bump before stabilizing would likely make sense. OK, let's call this one off until bug 366105 is realized. x86 pass. Closing wontfix.