When java-latest-openjdk (java-latest-openjdk-17.0.0.0.35-1.rolling.fc34.x86_64) is installed, the java selection (configuation) as selected by 'alternatives' is changed in some circumstances. If, before the upgrade, java-latest-openjdk was selected then after the installation of the RPM, the default java is selected. e.g. before: # alternatives --config java There are 3 programs which provide 'java'. Selection Command ----------------------------------------------- + 1 java-latest-openjdk.x86_64 (/usr/lib/jvm/java-16-openjdk-16.0.2.0.7-1.rolling.fc34.x86_64/bin/java) * 2 java-11-openjdk.x86_64 (/usr/lib/jvm/java-11-openjdk-11.0.12.0.7-4.fc34.x86_64/bin/java) 3 java-1.8.0-openjdk.x86_64 (/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.302.b08-2.fc34.x86_64/jre/bin/java) and after selection: # alternatives --config java There are 3 programs which provide 'java'. Selection Command ----------------------------------------------- 1 java-1.8.0-openjdk.x86_64 (/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.302.b08-2.fc34.x86_64/jre/bin/java) *+ 2 java-11-openjdk.x86_64 (/usr/lib/jvm/java-11-openjdk-11.0.12.0.7-4.fc34.x86_64/bin/java) 3 java-latest-openjdk.x86_64 (/usr/lib/jvm/java-17-openjdk-17.0.0.0.35-1.rolling.fc34.x86_64/bin/java) The upgrade should preserve the selection of java-latest-openjdk, it does not.
Maybe this is related to the 'priority' that is given to java-11 (unbelievably high - 11001207) /usr/lib/jvm/java-11-openjdk-11.0.12.0.7-4.fc35.x86_64/bin/java - family java-11-openjdk.x86_64 priority 11001207 So it may be a problem with the java-1-openjdk package rather than java-latest-openjdk
Hi Jiri, Could you take a quick look at this when you have a minute please? (Updates should not touch user configs, and change in alternatives seems to qualify as a change in user configurations?) Thanks very much
*** This bug has been marked as a duplicate of bug 2001567 ***