java-21-openjdk-devel-21.0.2.0.13-alt2.x86_64	alt-alternatives-vs-ghost	info	Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib/jvm/java-openjdk is an alternative in package java-1.8.0-openjdk-devel-1.8.0.402.b06-alt1_1jpp8.x86_64. Consider removing the ghost file /usr/lib/jvm/java-openjdk.; 
java-21-openjdk-devel-21.0.2.0.13-alt2.x86_64	bin-permissions	info	not executable file /usr/bin/serialver; ; 
java-21-openjdk-headless-21.0.2.0.13-alt2.x86_64	alt-alternatives-vs-ghost	info	Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib/jvm/jre-openjdk is an alternative in package java-1.8.0-openjdk-headless-1.8.0.402.b06-alt1_1jpp8.x86_64. Consider removing the ghost file /usr/lib/jvm/jre-openjdk.; 
java-21-openjdk-headless-21.0.2.0.13-alt2.x86_64	bin-permissions	info	not executable file /usr/bin/rmiregistry; 
java-21-openjdk-headless-debuginfo-21.0.2.0.13-alt2.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/.build-id/f8/7da04a7d25af80df1b24fbd94d4edb80dcb056.debug is different from the same symlink in the package java-17-openjdk-headless-debuginfo-17.0.10.0.7-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
java-21-openjdk-javadoc-21.0.2.0.13-alt2.x86_64	alt-alternatives-vs-ghost	info	Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/share/javadoc/java is an alternative in package java-1.8.0-openjdk-javadoc-1.8.0.402.b06-alt1_1jpp8.noarch. Consider removing the ghost file /usr/share/javadoc/java.; 
java-21-openjdk-javadoc-21.0.2.0.13-alt2.x86_64	arch-dep-package-has-big-usr-share	info	The package has a significant amount of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.;