Red Hat Bugzilla – Bug 591091
No junit4 package on ppc64
Last modified: 2012-06-04 11:27:17 EDT
I wanted to build bouncycastle for EPEL6.
It seems there is no junit4 package in RHEL6beta ppc64.
Is this intentional?
It's a noarch package. See ftp://ftp.redhat.com/pub/redhat/rhel/beta/6/i386/os/Packages/junit4-4.5-5.3.el6.noarch.rpm
I don't know why it didn't make it to ppc64.
It needs to be in ppc64 properly to permit EPEL packages on ppc64 to use it.
junit4 is only being pulled into the tree as a dependency of eclipse-jdt, and the eclipse stack is only included on x86_64 and i386. Perhaps junit4 could be copied into EPEL on ppc64?
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
Dennis, Due to the way koji works we can not provide packages in epel for only one architecture and we cant provide it for all.
RHEL-5 epel has no ppc support. Id like to promote ppc64 java support but perhaps we have to limit it for EL-6
Can the component be changed to koji or EPEL or something?
Dennis - can't someone build an exclusivearch ppc junit in EPEL?
We cant build packages for just one arch in EPEL, if we do the package will only then be available for the epel built arches. the only way to do it would be kinda messy. but have say junit-epel which is ppc64 only and provides all the junit provides.
there is not a clean easy way to do this other than for Red HAt to provide the same set of rpms across all arches. even if they are base on some arches and in optional on others.
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
This bug should have been labelled as priority: urgent, severity: urgent from the start, and should have been fixed the day after it was reported. I don't get why it is not solved yet more than two months after it was reported.
The solution for this is to build junit4 in EPEL for the arches that need it. (If that requires building it on all arches, so be it.)
The other solution is just ExcludeArch ppc64 for bouncycastle. I have zero
interest in seeing a ppc64 build and if redhat just want to drop this stack
on ppc64 so be it.