Public bug reported:
I had sun-java5-jdk=1.5.0-08-0ubuntu1 installed, and selected as my
default JVM:
# ls -l /etc/alternatives/java.1.gz
lrwxrwxrwx 1 root root 59 2006-11-16 08:29 /etc/alternatives/java.1.gz ->
/usr/lib/jvm/java-1.5.0-sun-1.5.0.08/jre/man/man1/java.1.gz
I then received the update to sun-java5-jdk=1.5.0-sun-1.5.0.11. After
this upgrade, however, the symlinks in /etc/alternatives were not
changed, causing my daily runs to moan at me:
/etc/cron.daily/man-db:
mandb: warning: /usr/share/man/man1/java.1.gz is a dangling symlink
mandb: warning: /usr/share/man/man1/rmiregistry.1.gz is a dangling symlink
mandb: warning: /usr/share/man/man1/javaws.1.gz is a dangling symlink
mandb: warning: /usr/share/man/man1/pack200.1.gz is a dangling symlink
mandb: warning: /usr/share/man/man1/policytool.1.gz is a dangling symlink
mandb: warning: /usr/share/man/man1/rmid.1.gz is a dangling symlink
mandb: warning: /usr/share/man/man1/unpack200.1.gz is a dangling symlink
mandb: warning: /usr/share/man/man1/appletviewer.1.gz is a dangling symlink
mandb: warning: /usr/share/man/man1/servertool.1.gz is a dangling symlink
mandb: warning: /usr/share/man/man1/orbd.1.gz is a dangling symlink
mandb: warning: /usr/share/man/man1/tnameserv.1.gz is a dangling symlink
This was easily fixed with:
$ update-java-alternatives -s java-1.5.0-sun
However, I think that failing to do this automatically violated the
Principle of Least Surprise - the user has installed and selected a JDK,
and expects everything to work, and continue working, even after
receiving an update. Can the post-install scripts for the various JDKs
make sure that alternatives are still set sanely?
** Affects: Ubuntu
Importance: Undecided
Status: Unconfirmed
--
java alternatives are not updated with the package, causing dangling symlinks
https://launchpad.net/bugs/93619
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
