Hide Forgot
Description of problem: /etc/alternatives/policytool: broken symbolic link to `/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.72-1.b15.fc22.i386/jre/bin/policytool' Version-Release number of selected component (if applicable): -1.8.0.72-1.b15.fc22.i386 How reproducible: every version update. Steps to Reproduce: 1. file /etc/alternatives/policytool gives... /etc/alternatives/policytool: broken symbolic link to `/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.72-1.b15.fc22.i386/jre/bin/policytool' 2. 3. Actual results: file /etc/alternatives/policytool gives... /etc/alternatives/policytool: broken symbolic link to `/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.72-1.b15.fc22.i386/jre/bin/policytool' Expected results: A valid file. Additional info:
Hello! This is not general issue as I was not able to reproduce under nay condition. The policy tool recently - September/October 2014 moved from devel to (headless) jre. However, yours /java-1.8.0-openjdk-1.8.0.72-1.b15.fc22.i386/ suggest that it do not update. Do you have some additional suggestion what may stay behind the broken update ath?
yum/dnf update - does not indicate a problem (is there anything that would now yum/dnf is in such a flux - with no "yum verify", what did replace that?). [root@loki ~]# file /etc/alternatives/policytool /etc/alternatives/policytool: broken symbolic link to `/usr/lib/jvm/java-1.8.0-o penjdk-1.8.0.72-1.b15.fc22.i386/jre/bin/policytool' [root@loki ~]# ls -l /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.72-1.b15.fc22.i386/jr e/bin/policytool ls: cannot access /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.72-1.b15.fc22.i386/jre/b in/policytool: No such file or directory [root@loki ~]# ls -l /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.72-1.b15.fc22.i386/jr e/bin total 188 -rwxr-xr-x. 1 root root 6604 Jan 28 22:33 java -rwxr-xr-x. 1 root root 6620 Jan 28 22:33 jjs -rwxr-xr-x. 1 root root 6628 Jan 28 22:33 keytool -rwxr-xr-x. 1 root root 6636 Jan 28 22:33 orbd -rwxr-xr-x. 1 root root 6632 Jan 28 22:33 pack200 -rwxr-xr-x. 1 root root 6624 Jan 28 22:33 rmid -rwxr-xr-x. 1 root root 6632 Jan 28 22:33 rmiregistry -rwxr-xr-x. 1 root root 6636 Jan 28 22:33 servertool -rwxr-xr-x. 1 root root 6640 Jan 28 22:33 tnameserv -rwxr-xr-x. 1 root root 115492 Jan 28 22:33 unpack200 [root@loki ~]# rpm -q --whatprovides /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.72-1.b15.fc22.i386/jre/bin java-1.8.0-openjdk-headless-1.8.0.72-1.b15.fc22.i686 Eventually, removing (explicitly that package, just java-1.8.0-openjdk did not work), java-1.8.0-openjdk-headless-1.8.0.72-1.b15.fc22.i686 & reinstalling libreoffice seems to have solved it, but how did it happen? and, is there "JUNK" here still? [root@loki ~]# ls -l /usr/lib/jvm/ total 24 drwxr-xr-x. 3 root root 4096 Dec 15 2014 java-1.8.0-openjdk-1.8.0.25-5.b18.fc21.i386 drwxr-xr-x. 3 root root 4096 Mar 19 2015 java-1.8.0-openjdk-1.8.0.40-21.b25.fc21.i386 drwxr-xr-x. 3 root root 4096 Aug 28 2015 java-1.8.0-openjdk-1.8.0.60-14.b27.fc21.i386 drwxr-xr-x. 3 root root 4096 Aug 28 2015 java-1.8.0-openjdk-1.8.0.60-14.b27.fc22.i386 drwxr-xr-x. 3 root root 4096 Oct 21 18:36 java-1.8.0-openjdk-1.8.0.65-3.b17.fc21.i386 drwxr-xr-x. 3 root root 4096 Jan 28 22:29 java-1.8.0-openjdk-1.8.0.72-1.b15.fc22.i386 lrwxrwxrwx. 1 root root 21 Mar 11 10:00 jre -> /etc/alternatives/jre lrwxrwxrwx. 1 root root 27 Mar 11 10:00 jre-1.8.0 -> /etc/alternatives/jre_1.8.0 lrwxrwxrwx. 1 root root 35 Mar 11 10:00 jre-1.8.0-openjdk -> /etc/alternatives/jre_1.8.0_openjdk lrwxrwxrwx. 1 root root 47 Jan 28 22:29 jre-1.8.0-openjdk-1.8.0.72-1.b15.fc22.i386 -> java-1.8.0-openjdk-1.8.0.72-1.b15.fc22.i386/jre lrwxrwxrwx. 1 root root 29 Mar 11 10:00 jre-openjdk -> /etc/alternatives/jre_openjdk The vagaries of yum/dnf/rpm at times are mystifying!
Sorry I thought I'd emailed the above - seems it didn't get through...
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.