Bug 1416561 - ca-certificates upgrade breaking maven central pom retrieval
Summary: ca-certificates upgrade breaking maven central pom retrieval
Keywords:
Status: CLOSED DUPLICATE of bug 1415137
Alias: None
Product: Fedora
Classification: Fedora
Component: ca-certificates
Version: 25
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kai Engert (:kaie) (inactive account)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-25 19:57 UTC by Justin Venus
Modified: 2017-01-26 16:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-26 16:54:45 UTC
Type: Bug


Attachments (Terms of Use)
Maven build failure with updated ca-certificates installed (16.17 KB, text/plain)
2017-01-25 19:57 UTC, Justin Venus
no flags Details

Description Justin Venus 2017-01-25 19:57:09 UTC
Created attachment 1244397 [details]
Maven build failure with updated ca-certificates installed

Description of problem:
Updated ca-certificates package breaks mvn.  The first package released with fc25 works as expected.


Version-Release number of selected component (if applicable):
ca-certificates-2017.2.11-1.0.fc25.noarch.rpm

How reproducible:
100% with a mesos build


Steps to Reproduce:
1. install/upgrade to ca-certificates-2017.2.11-1.0.fc25.noarch.rpm
2. git clone https://github.com/apache/mesos.git
3. cd mesos && git checkout tags/1.0.0
4. mkdir build && ./bootstrap && cd build
5. ../configure --without-python --with-java  # ignore warning about flags
6. cd src/mesos/java
7. MAVEN_OPTS="-Xmx1024m" mvn -X -B -f mesos.pom clean package

Actual results:
#see attachement `maven-failure.log` for more detail
[DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/jvenus/.m2/repository
[INFO] Scanning for projects...
[DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2
[DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2
[INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/apache/11/apache-11.pom
[DEBUG] Writing tracking file /home/jvenus/.m2/repository/org/apache/apache/11/apache-11.pom.lastUpdated
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for org.apache.mesos:mesos:1.0.0: Could not transfer artifact org.apache:apache:pom:11 from/to central (https://repo.maven.apache.org/maven2): java.security.ProviderException: java.lang.NegativeArraySizeException and 'parent.relativePath' points at wrong local POM @ line 18, column 11
 @
[ERROR] The build could not read 1 project -> [Help 1]
org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for org.apache.mesos:mesos:1.0.0: Could not transfer artifact org.apache:apache:pom:11 from/to central (https://repo.maven.apache.org/maven2): java.security.ProviderException: java.lang.NegativeArraySizeException and 'parent.relativePath' points at wrong local POM @ line 18, column 11

    at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:422)


Expected results:
resolve dependencies

Additional info:

Comment 1 Kai Engert (:kaie) (inactive account) 2017-01-26 13:40:52 UTC
Are you sure the problem is caused by the ca-certificates package, and can be fixed by downgrading the ca-certificates package, only?

Or could this bug be a duplicate of bug 1415137 which is about openjdk being incompatible with latest NSS 3.28 (because openjdk uses a private interface of NSS, which requires openjdk to be rebuilt).

I'm asking, because I see an exception related to ECKeyPairGenerator in your attachment.

Could you please try to upgrade to the newer java package that is made available in that bug, and check if it fixes your issue?

Comment 2 Justin Venus 2017-01-26 16:23:20 UTC
Kai, yeah I've seen that exact segfault (randomly) and erroneously attributed it to running a build in docker.  I believe we can close this as a duplicate.

Comment 3 Justin Venus 2017-01-26 16:54:45 UTC

*** This bug has been marked as a duplicate of bug 1415137 ***


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