Bug 1858074 - protobuf fails to build with java-11-openjdk
Summary: protobuf fails to build with java-11-openjdk
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: protobuf
Version: 33
Hardware: All
OS: All
unspecified
high
Target Milestone: ---
Assignee: Igor Raits
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: Java11
TreeView+ depends on / blocked
 
Reported: 2020-07-16 21:46 UTC by jiri vanek
Modified: 2020-09-25 18:07 UTC (History)
12 users (show)

Fixed In Version: protobuf-3.13.0-1.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-25 18:07:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description jiri vanek 2020-07-16 21:46:08 UTC
protobuf fails to build with java-11-openjdk as sytem JDK. See https://fedoraproject.org/wiki/Changes/Java11 .
See especially part about known failures: https://fedoraproject.org/wiki/Changes/Java11#common_issues_packagers_can_face_and_gathered_solutions

For the build logs, see: https://koji.fedoraproject.org/koji/taskinfo?taskID=47161440
We run the rebuild longer then 10days ago. Log may be gone. Also your package may be passing in regular rawhide.
To reproduce, simply: fedpkg clone protobuf; cd protobuf;  fedpkg build --target f33-java11; #The target is crucial.

We run two reruns your package failed both.


We had tried 650 packages, and 500 had passed, so the java-11-openjdk will be system JDK in f33, and you should fix your package if you want to keep it alive. Usually the fix is simple, and best is to update the package to latest upstream version.
There will be usual mass rebuild once f33 branches. You may got another FTBFS bug.
Let us know here if you have any questions, here in bug, or at java-devel.org .

We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side if needed.

Comment 1 jiri vanek 2020-07-17 04:03:05 UTC
highlight: This was rebuild in sidetag f33-java11. Thus --target is really necessary to reproduce failure.
please note: This side tag, f33-java11, will be merged to main f33 buildroot in aprox 14 days.

Comment 2 Adrian Reber 2020-07-17 06:04:31 UTC
I had a look at the error message:

[INFO] Running com.google.protobuf.ExtensionRegistryFactoryTest
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.003 s <<< FAILURE! - in com.google.protobuf.ExtensionRegistryFactoryTest
[ERROR] initializationError(com.google.protobuf.ExtensionRegistryFactoryTest)  Time elapsed: 0.002 s  <<< ERROR!
java.lang.ExceptionInInitializerError
	at com.google.protobuf.ExtensionRegistryFactoryTest.getLiteOnlyClassLoader(ExtensionRegistryFactoryTest.java:259)
	at com.google.protobuf.ExtensionRegistryFactoryTest.<clinit>(ExtensionRegistryFactoryTest.java:59)

This happens during %check.

It seems there is an upstream bug report for this: https://github.com/protocolbuffers/protobuf/issues/4269

The upstream bug has been closed but there are still comments that this is not fixed.

No idea how this can fixed right now.

Comment 3 Ben Cotton 2020-08-11 15:24:33 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Comment 4 Charalampos Stratakis 2020-08-26 19:10:29 UTC
PR: https://src.fedoraproject.org/rpms/protobuf/pull-request/5

The update however introduces a soname bump so an announcement to the devel list and a rebuild of all the dependent packages will be required.

Comment 5 Fedora Update System 2020-09-25 18:07:57 UTC
FEDORA-2020-7cb9b0c7a3 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.


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