Bug 1857942

Summary:	frysk fails to build with java-11-openjdk
Product:	[Fedora] Fedora	Reporter:	jiri vanek <jvanek>
Component:	frysk	Assignee:	Cagney <cagney>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	cagney, decathorpe, java-maint-sig, jvanek, kasal, sgehwolf
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-18 15:27:00 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1825969

Description jiri vanek 2020-07-16 18:48:00 UTC

frysk 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=47151035
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 frysk; cd frysk;  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 03:45:43 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 Cagney 2020-07-17 16:39:20 UTC

(In reply to jiri vanek from comment #1)
> 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.

I'm not sure how to interpret this?

Comment 3 Severin Gehwolf 2020-07-17 17:03:59 UTC

(In reply to cagney from comment #2)
> (In reply to jiri vanek from comment #1)
> > 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.
> 
> I'm not sure how to interpret this?

fedpkg build --target f33-java11

needs to be used to reproduce the failure. The builds happened in a side tag for the time being, but the intention is to merge those build (tag them) into the f33 tag hierarchy in about 14 days. At which point a failure would be reproducible with "fedpkg build" (without the target).

Comment 4 Cagney 2020-07-18 15:27:00 UTC

(In reply to Severin Gehwolf from comment #3)
> (In reply to cagney from comment #2)
> > (In reply to jiri vanek from comment #1)
> > > 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.
> > 
> > I'm not sure how to interpret this?
> 
> fedpkg build --target f33-java11
> 
> needs to be used to reproduce the failure. The builds happened in a side tag
> for the time being, but the intention is to merge those build (tag them)
> into the f33 tag hierarchy in about 14 days. At which point a failure would
> be reproducible with "fedpkg build" (without the target).

I'm still not sure how to interpret this.

I pushed .73 which, to the best of my knowledge, fixed java 11 build problems.

- is this a follow-up to the bug's original description (and its appearance after I pushed the update purely coincidental)?
- or, you did a build of that update but found it still failed (if this happened I'm all ears, my mock build worked)?
- or, ?

Lets assume its the first, can I suggest next time:

- be clear that it is simply a follow-up with suggestions on how to debug should you be stuck
- include both the above and MOCK as ways to debug/test fixes (per web page)
- be clear of any expectation that the RPM also needs to be built in f33-java11 (I'm assuming this will happen automatically as a result of a mass rebuild)

Since I believe this to be fixed; I'm closing the bug.