Description of problem: I try to install software with condition jre < 10 with installed package java-1.8.0-openjdk.x86_64 1:1.8.0.272.b01-0.1.ea.fc33 but it fails as Problém: package flexibee-client-2020.2.6-1.noarch requires jre < 10, but none of the providers can be installed" How reproducible: Install this package https://download.flexibee.eu/download/2020.2/2020.2.6/flexibee-client-2020.2.6-1.noarch.rpm with installed java-1.8.0-openjdk.x86_64 1:1.8.0.272.b01-0.1.ea.fc33 and the error package flexibee-client-2020.2.6-1.noarch requires jre < 10, but none of the providers can be installed apperars. This allow affects Fedora 32.
Reassigning to java-openjdk, seems like some packaging issues there or even in the flexibee-client.
Why is this bugged against java-openjdk and not against java-1.8.0-openjdk, which is the only provider of java 1.8.0? java-latest-openjdk harborurs jdk 15 nad java-11-openjdk provides java 11. The version F33 suggest, that some package suffered from https://fedoraproject.org/wiki/Changes/Java11 That enforced java-11 comaptible jdks have version-less provides, whcih java 1.8 is not: https://src.fedoraproject.org/rpms/java-1.8.0-openjdk/c/6b38e01a0e5aea56e80c2115cc839e2582f160e1 ; which affects maainly: https://src.fedoraproject.org/rpms/java-1.8.0-openjdk/blob/6b38e01a0e5aea56e80c2115cc839e2582f160e1/f/java-1.8.0-openjdk.spec#_1045 https://src.fedoraproject.org/rpms/java-1.8.0-openjdk/blob/6b38e01a0e5aea56e80c2115cc839e2582f160e1/f/java-1.8.0-openjdk.spec#_1083 and https://src.fedoraproject.org/rpms/java-1.8.0-openjdk/blob/6b38e01a0e5aea56e80c2115cc839e2582f160e1/f/java-1.8.0-openjdk.spec#_1105
Setting the component to java-1.8.0-openjdk.
Requires from the flexibee-client RPM (third party): $ rpm -q --requires -p flexibee-client-2020.2.6-1.noarch.rpm jre >= 1.7 jre < 10 /bin/sh /bin/sh /bin/sh /bin/sh rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 Provides from the F33 java-1.8.0-openjdk RPM: $ rpm -q --provides -p java-1.8.0-openjdk-1.8.0.272.b09-0.0.ea.fc33.x86_64.rpm application() application(java-1.8.0-openjdk-1.8.0.272.b09-0.0.ea.fc33.x86_64-policytool.desktop) java-1.8.0 = 1:1.8.0.272.b09-0.0.ea.fc33 java-1.8.0-openjdk = 1:1.8.0.272.b09-0.0.ea.fc33 java-1.8.0-openjdk(x86-64) = 1:1.8.0.272.b09-0.0.ea.fc33 jre-1.8.0 = 1:1.8.0.272.b09-0.0.ea.fc33 jre-1.8.0-openjdk = 1:1.8.0.272.b09-0.0.ea.fc33 Provides from the F33 java-11-openjdk RPM: $ rpm -q --provides -p java-11-openjdk-11.0.9.7-0.0.ea.fc33.x86_64.rpm java = 1:11.0.9.7-0.0.ea.fc33 java-11 = 1:11.0.9.7-0.0.ea.fc33 java-11-openjdk = 1:11.0.9.7-0.0.ea.fc33 java-11-openjdk(x86-64) = 1:11.0.9.7-0.0.ea.fc33 java-openjdk = 1:11.0.9.7-0.0.ea.fc33 jre = 1:11.0.9.7-0.0.ea.fc33 jre-11 = 1:11.0.9.7-0.0.ea.fc33 jre-11-openjdk = 1:11.0.9.7-0.0.ea.fc33 jre-openjdk = 1:11.0.9.7-0.0.ea.fc33 libjawt.so()(64bit) Like Jiri pointed out in comment 2, flexibee-client's requires cannot be satisfied on Fedora. That has to do with the changes made by https://fedoraproject.org/wiki/Changes/Java11. With F33 onwards the system JDK which provides the version-less jre provides is java-11-openjdk. flexibee-client-2020.2.6-1.noarch.rpm doesn't seem to work with JDK 11 (if I understand the intended requires correctly). TLDR: This is an issue with flexibee-client-2020.2.6-1.noarch.rpm. Please work with the provider to get this resolved. E.g. specifically requiring jre-1.8.0. As a work-around you could force-install the flexbee-client after you've installed java-1.8.0-openjdk with: $ rpm -ihv --force flexibee-client-2020.2.6-1.noarch.rpm
Sorry, but there is nothing we can do in Fedora.
Note this last works with F32, since for F32, JDK 8 was still the system JDK. $ rpm -q java-1.8.0-openjdk java-1.8.0-openjdk-1.8.0.265.b01-1.fc32.x86_64 $ rpm -q --provides java-1.8.0-openjdk | grep jre jre = 1:1.8.0.265.b01-1.fc32 jre-1.8.0 = 1:1.8.0.265.b01-1.fc32 jre-1.8.0-openjdk = 1:1.8.0.265.b01-1.fc32 jre-openjdk = 1:1.8.0.265.b01-1.fc32
I am facing the same issues and I must admit, that there is probably missing some explanation, why java-1.8.0-openjdk should not provide `jre = 1.8.0` as it used to. While I understand, that flexibee could probably run against java-11-openjdk, I don't understand, why you deliberately break flexibee. Is there some reason why it should not run with java-1.8.0-openjdk? If there is, I don't think it was clearly stated anywhere. OTOH, the truth is, that packaging guidelines does not mention `jre`, but `java`. Probably time to give a try to `create-fake-rpm` tool ...
BTW: ~~~ $ flexibee OpenJDK 64-Bit Server VM warning: Ignoring option MaxPermSize; support was removed in 8.0 Error occurred during initialization of boot layer java.lang.module.FindException: Module java.xml.ws not found $ rpm -q flexibee-client flexibee-client-2020.2.6-1.noarch $ rpm -q java* -a javapackages-filesystem-5.3.0-13.fc33.noarch java-11-openjdk-headless-11.0.9.11-1.fc34.x86_64 java-11-openjdk-11.0.9.11-1.fc34.x86_64 ~~~ So maybe it does not run with Java 11 after all.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.