Summary: | [java-experimental] dev-java/jboss-module-security-4.0.2 doesn't like javacc-4.0 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Uwe Klosa <uwe.klosa> |
Component: | Current packages | Assignee: | Java team <java> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | Keywords: | InOverlay |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | java-experimental | ||
Package list: | Runtime testing required: | --- |
Description
Uwe Klosa
2006-06-20 11:56:05 UTC
*** Bug 137404 has been marked as a duplicate of this bug. *** *** Bug 137405 has been marked as a duplicate of this bug. *** *** Bug 137406 has been marked as a duplicate of this bug. *** I'm sorry for the mess but i always got a connection reset when submitting the bug. As with jboss-module-common, the answer lies in the ebuild itself. # this doesn't like javacc-4 apparently, but depending on =3* would create a # up/downgrade cycle So you should try with javacc-3* (assuming you have javacc-4) Now I wanna know why azureus is keyworded -* because of "hard migration path" and these apparently known-to-be-broken ebuilds are ~arch, no package.mask or -* :) Thanks for the hint. With javacc-3 it compiles. The jboss-* ebuilds in java-experimental aren't maintained for many years and no one is going to use them anymore. Marking this one obsolete. Thanks for the report though. |