Bug 2051182 - jnr-x86asm fails to build with java-17-openjdk
Summary: jnr-x86asm fails to build with java-17-openjdk
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: jnr-x86asm
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: mo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2024265
TreeView+ depends on / blocked
 
Reported: 2022-02-06 15:07 UTC by jiri vanek
Modified: 2022-11-10 22:24 UTC (History)
8 users (show)

Fixed In Version: jnr-x86asm-1.0.2-29.fc37
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-10 22:24:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description jiri vanek 2022-02-06 15:07:53 UTC
jnr-x86asm fails to build with java-17-openjdk as sytem JDK. See https://fedoraproject.org/wiki/Changes/Java17 .
See especially part about known failures: https://fedoraproject.org/wiki/Changes/Java17#common_issues_packagers_can_face_and_gathered_solutions

For the build logs, see: https://koji.fedoraproject.org/koji/taskinfo?taskID=82429807
https://kojipkgs.fedoraproject.org/work/tasks/9920/82429920/mock_output.log
https://kojipkgs.fedoraproject.org/work/tasks/9920/82429920/hw_info.log
https://kojipkgs.fedoraproject.org/work/tasks/9920/82429920/state.log
https://kojipkgs.fedoraproject.org/work/tasks/9920/82429920/build.log
https://kojipkgs.fedoraproject.org/work/tasks/9920/82429920/root.log
We run the rebuild in side tag f36-java17, but as fail ratio was small, we expect this side tag to be merged into rawhide 7 or 8 of February 2022.
To reproduce before this date simply: fedpkg clone jnr-x86asm; cd jnr-x86asm;  fedpkg build --target f36-java17; #The target is crucial.
After this date the usual fedpkg build in f36 and up should do.

We run two reruns your package failed both.

We had also run the mass rebuilds in copr since November. We keep all encountered failures. See them here: https://copr.fedorainfracloud.org/coprs/jvanek/java17//package/jnr-x86asm
You may find interesting additional informations here. Also we were spamming maintainers regualrly, check you spam folder.
              

We had tried aprox 500 packages, and aprox 65 had failed, so the java-17-openjdk will be system JDK in f36, 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 f36 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 2022-02-06 15:08:45 UTC
[ERROR] Source option 6 is no longer supported. Use 7 or later.
[ERROR] Target option 6 is no longer supported. Use 7 or later.
[INFO] 2 errors 
[INFO] -------------------------------------------------------------

intialus trivialus

Comment 2 Ben Cotton 2022-02-08 20:12:13 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.

Comment 3 Fedora Update System 2022-10-25 13:08:30 UTC
FEDORA-2022-c1bd2c6cac has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-c1bd2c6cac

Comment 4 Fedora Update System 2022-10-26 16:18:07 UTC
FEDORA-2022-c1bd2c6cac has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-c1bd2c6cac`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-c1bd2c6cac

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2022-11-10 22:24:56 UTC
FEDORA-2022-c1bd2c6cac has been pushed to the Fedora 37 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.