Bug 1895561 - java 11 not found
Summary: java 11 not found
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: java-11-openjdk
Version: 32
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: jiri vanek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-07 05:00 UTC by FlyDove
Modified: 2021-05-25 17:30 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-25 17:30:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
java 11 on /etc/alternatives (514.69 KB, image/png)
2020-11-07 05:00 UTC, FlyDove
no flags Details
java in /usr/lib/jvm (231.32 KB, image/png)
2020-11-07 05:08 UTC, FlyDove
no flags Details
java 11 not found for eclispe (19.44 KB, image/png)
2020-11-07 05:09 UTC, FlyDove
no flags Details

Description FlyDove 2020-11-07 05:00:27 UTC
Created attachment 1727316 [details]
java 11 on   /etc/alternatives

/usr/lib/jvm

java-11 -> /etc/alternatives/java_sdk_11
java-11-openjdk -> /etc/alternatives/java_sdk_11_openjdk
jre-11 -> /etc/alternatives/jre_11

jre-11-openjdk -> /etc/alternatives/jre_11_openjdk


java_sdk_11 -> /usr/lib/jvm/java-11-openjdk-11.0.8.10-2.fc32.x86_64
 java_sdk_11_openjdk -> /usr/lib/jvm/java-11-openjdk-11.0.8.10-2.fc32.x86_64




rpm -qa | grep java-11
java-11-openjdk-headless-11.0.9.11-0.fc32.x86_64
java-11-openjdk-devel-11.0.9.11-0.fc32.x86_64
java-11-openjdk-11.0.9.11-0.fc32.x86_64

Comment 1 FlyDove 2020-11-07 05:08:38 UTC
Created attachment 1727317 [details]
java in  /usr/lib/jvm

Comment 2 FlyDove 2020-11-07 05:09:40 UTC
Created attachment 1727318 [details]
java 11 not found for eclispe

Comment 3 FlyDove 2020-11-07 05:17:05 UTC
do shell


sudo rm -fr /var/lib/dnf/history/* /var/lib/dnf/history.* /var/log/dnf*.log*

sudo rm -fr /var/lib/rpm/* && sudo rpm --rebuilddb 


sudo dnf group install  ****    --releasever=32 --allowerasing --skip-broken  --best -4 -y



rpm -qa | grep java-11
java-11-openjdk-headless-11.0.9.11-0.fc32.x86_64
java-11-openjdk-devel-11.0.9.11-0.fc32.x86_64
java-11-openjdk-11.0.9.11-0.fc32.x86_64

Comment 4 Fedora Program Management 2021-04-29 16:57:54 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
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 '32'.

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 32 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.

Comment 5 jiri vanek 2021-04-30 11:56:56 UTC
Could you had hit the https://bugzilla.redhat.com/show_bug.cgi?id=1200302 ?

Comment 6 Ben Cotton 2021-05-25 17:30:45 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.


Note You need to log in before you can comment on or make changes to this bug.