Bug 1269629 - [epel7s390x] bouncycastle-pkix SRPM does not build correctly on s390x
Summary: [epel7s390x] bouncycastle-pkix SRPM does not build correctly on s390x
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: bouncycastle-pkix
Version: epel7
Hardware: s390x
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: epel7s390x
TreeView+ depends on / blocked
 
Reported: 2015-10-07 19:15 UTC by IBM Bug Proxy
Modified: 2020-04-14 11:05 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-04-14 11:05:13 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 131434 0 None None None 2019-02-21 09:28:03 UTC

Description IBM Bug Proxy 2015-10-07 19:15:33 UTC
Comment 1 IBM Bug Proxy 2015-10-07 19:15:35 UTC 
The EPEL 7 SRPM for bouncycastle-pkix 
https://dl.fedoraproject.org/pub/epel/7/SRPMS/b/bouncycastle-pkix-1.50-1.el7.src.rpm 
does not build correctly in Mock on s390x.

The compilation succeeded with no error. But the unit tests encountered issue with signing, therefore preventing RPM from being built. 

Here is the stack trace of erroneous unit test:
    [junit] Testcase: testEncryptedValue took 2.332 sec
    [junit]     Caused an ERROR
    [junit] cannot create key generator: JCE cannot authenticate the provider BC
    [junit] org.bouncycastle.cert.crmf.CRMFException: cannot create key generator: JCE cannot authenticate the provider BC
    [junit]     at org.bouncycastle.cert.crmf.jcajce.CRMFHelper.createKeyGenerator(CRMFHelper.java:158)
    [junit]     at org.bouncycastle.cert.crmf.jcajce.JceCRMFEncryptorBuilder$CRMFOutputEncryptor.<init>(JceCRMFEncryptorBuilder.java:80)
    [junit]     at org.bouncycastle.cert.crmf.jcajce.JceCRMFEncryptorBuilder.build(JceCRMFEncryptorBuilder.java:67)
    [junit]     at org.bouncycastle.cert.crmf.test.AllTests.testEncryptedValue(AllTests.java:262)
    [junit] Caused by: java.security.NoSuchProviderException: JCE cannot authenticate the provider BC
    [junit]     at javax.crypto.b.a(Unknown Source)
    [junit]     at javax.crypto.KeyGenerator.getInstance(Unknown Source)
    [junit]     at org.bouncycastle.jcajce.NamedJcaJceHelper.createKeyGenerator(NamedJcaJceHelper.java:65)
    [junit]     at org.bouncycastle.cert.crmf.jcajce.CRMFHelper.createKeyGenerator(CRMFHelper.java:147)
    [junit] Caused by: java.util.jar.JarException: file:/usr/share/java/bcprov.jar has unsigned entries - org/bouncycastle/LICENSE.class
    [junit]     at javax.crypto.a.a(Unknown Source)
    [junit]     at javax.crypto.a.a(Unknown Source)
    [junit]     at javax.crypto.a.a(Unknown Source)
    [junit]     at javax.crypto.b.b(Unknown Source)
    [junit]     at javax.crypto.b.a(Unknown Source)
Comment 2 Mat Booth 2015-10-08 08:30:03 UTC 
Changing product to "EPEL"...
Comment 3 IBM Bug Proxy 2016-02-23 17:32:23 UTC 
------- Comment From vsandhya.com 2016-02-23 12:11 EDT-------
Any updates?
Comment 4 IBM Bug Proxy 2020-04-14 08:02:24 UTC 
------- Comment From tstaudt.com 2020-04-14 03:54 EDT-------
With no activity in this bug for years, I'm now closing this on the IBM side.
If the problem still needs to be addressed, please re-open or preferably open a new bug.

Thanks.
Note You need to log in before you can comment on or make changes to this bug.