Bug 84992 - keywording request for dev-java/commons-logging-1.0.4-r1
|
Bug#:
84992
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: All
|
Status: RESOLVED
|
Severity: enhancement
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: luckyduck@gentoo.org
|
Reported By: luckyduck@gentoo.org
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: keywording request for dev-java/commons-logging-1.0.4-r1
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2005-03-12 08:44 0000
|
the old ebuild (-r0) made use of binary packages (see #75856). to remove these
dependencies we had to add some new packages to the tree. these recently
introduced packages missing some keywords which the -r0 ebuild has. i dropped
these keywords from the -r1 ebuild for the moment. ppc, ppc64 and sparc:
please mark the following packages ~arch, afterwards feel free to re-add your
keywords to dev-java/commons-logging-1.0.4-r1:
=dev-java/avalon-logkit-1.2
=dev-java/avalon-framework-4.2.0
thanks.
since ppc and sparc are still on cc, i just add another request to this list
i have to drop ~ppc and ~sparc from another package, fop-0.20.5-r2 because that version doesn't make use of packed jars any longer (fixed bug #63262). it relies the avalon-framework-4.1* which miss these keywords:
RDEPEND.bad 1
dev-java/fop/fop-0.20.5-r2.ebuild: ~ppc ['=dev-java/avalon-framework-4.1*']
RDEPEND.badindev 1
dev-java/fop/fop-0.20.5-r2.ebuild: ~sparc ['=dev-java/avalon-framework-4.1*']
please also add your keywords to that version, and afterwards to the new fop revision if appropriate.
~sparc done for commons-logging.
Some observations:
xerces-2 doesn't seem to like FEATURES="usersandbox userpriv" for us at least, the jvm will sig11 otherwise.
fop can use sun-jai-bin, which includes a binary-only component for x86, isn't this required at all/optional optimizations or what? (this question applies to other arches too).
fop breaks on batik-1.5, again, with a sig11 on the jvm. I didn't find a workaround. Dunno if the later batik-1.5.1*'s would cut it.
avalon-logkit-2.0 seems to be sensitive when USE="jms" is enabled and you have jms, openjms & openjms-bin around. This might be a sparc-specific thingy though (jvm sig11).
fixed the rdepend issues,
some thoughts, the problems gustavoz said are on ppc also, better to review the openjms thingie completely, i'll talk to luckduck about it.
greetings
i can't reproduce the sig11 problems on either x86, amd64 or ppc. that seems to
be indeed related to sparc. i've excluded openjms from ppc for the moment. it
seems that that package and some of the deps needs some loving again. i'll do
that in the next week or something. marking this one as fixed, thanks for your
effort.
