Bug 2101524

Summary:	[rpminspect] Disable Java bytecode checks [java-17-openjdk, rhel-8]
Product:	Red Hat Enterprise Linux 8	Reporter:	Andrew John Hughes <ahughes>
Component:	java-17-openjdk	Assignee:	Andrew John Hughes <ahughes>
Status:	CLOSED ERRATA	QA Contact:	OpenJDK QA <java-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	---	CC:	jandrlik, pmikova
Target Milestone:	rc	Keywords:	Triaged, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	java-17-openjdk-17.0.3.0.7-3.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2109106 2109107 (view as bug list)		Environment:
Last Closed:	2022-11-08 09:32:03 UTC	Type:	Bug
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:	2109106, 2109107

Description Andrew John Hughes 2022-06-27 17:25:39 UTC

This bug was initially created as a copy of Bug #2023540

I am copying this bug because: 

RHEL 8 is now using rpminspect so we need the same change there.

rpminspect ensures that the Java bytecode of classes in an RPM package have a maximum version of the default version for that edition of RHEL.

This makes sense for Java applications, but not for the JDK itself, as a JDK handles its own bytecode rather than relying on a system default JDK to do so.

On RHEL 9, the default version is Java 11. So, while the test succeeds on JDK 8 & 11, as they both comply with the maximum, it fails on JDK 17 where the bytecode is Java 17 bytecode as it must be.

We should add an rpminspect.yaml [0] into the java-17-openjdk tree to disable the test for this package.

[0] https://one.redhat.com/rhel-developer-guide/#proc_modifying-a-per-package-rpminspect-yaml-file_rhel-dev-guide

Comment 9 errata-xmlrpc 2022-11-08 09:32:03 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (java-17-openjdk bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:6691