Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1858076 - python-jnius fails to build with java-11-openjdk
Summary: python-jnius fails to build with java-11-openjdk
Keywords:
Status: CLOSED DUPLICATE of bug 1826539
Alias: None
Product: Fedora
Classification: Fedora
Component: python-jnius
Version: 33
Hardware: All
OS: All
unspecified
high
Target Milestone: ---
Assignee: Raphael Groner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1865297 (view as bug list)
Depends On: 1826539
Blocks: F33FTBFS Java11
TreeView+ depends on / blocked
 
Reported: 2020-07-16 21:50 UTC by jiri vanek
Modified: 2020-10-01 18:29 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-01 18:29:11 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description jiri vanek 2020-07-16 21:50:14 UTC 
python-jnius 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=47161642
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 python-jnius; cd python-jnius;  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:30 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 Raphael Groner 2020-08-04 07:08:02 UTC 
*** Bug 1865297 has been marked as a duplicate of this bug. ***
Comment 3 Ben Cotton 2020-08-11 15:24:39 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.
Comment 4 Fedora Release Engineering 2020-09-30 18:40:49 UTC 
Dear Maintainer,

your package has an open Fails To Build From Source bug for Fedora 33.
Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this Bugzilla report.

Following the policy for such packages [2], your package will be orphaned if
this bug remains in NEW state more than 8 weeks (not sooner than 2020-09-10).

A week before the mass branching of Fedora 34 according to the schedule [3],
any packages not successfully rebuilt at least on Fedora 32 will be
retired regardless of the status of this bug.

[1] https://fedoraproject.org/wiki/Updates_Policy
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html
Comment 5 Raphael Groner 2020-10-01 18:29:11 UTC 
This will be fixed with successful bump to version 1.3.0, see bug #1826539.

*** This bug has been marked as a duplicate of bug 1826539 ***
Note You need to log in before you can comment on or make changes to this bug.