On Sunday 13 September 2009 10:01:55 Raphael Hertzog wrote: > What is the package that provides the java alternative with the > rmiregistry slave ?
From looking at the output of update-alternatives --query java it appears to be this alternative that is causing the problem: Alternative: /usr/bin/gij-wrapper-3.3 Priority: 33 Slaves: java.1.gz /usr/share/man/man1/gij-wrapper-3.3.1.gz rmiregistry /usr/bin/rmiregistry-3.3 rmiregistry.1.gz /usr/share/man/man1/rmiregistry-3.3.1.gz /usr/bin/gij-wrapper-3.3 is provided by gij-3.3 1:3.3.6-7 > Make your /var/lib/dpkg/alternatives/java file available in the log > as well as the package name and package version that provides > /usr/bin/java /usr/bin/java is currently linked to /usr/bin/gij-4.4 (provided by gcj-4.4-jre-headless 4.4.1-1). Here is my /var/lib/dpkg/alternatives/java file: auto /usr/bin/java java.1.gz /usr/share/man/man1/java.1.gz rmiregistry /usr/bin/rmiregistry rmiregistry.1.gz /usr/share/man/man1/rmiregistry.1.gz /etc/alternatives/kaffe-system/bin/java 300 /usr/share/man/man1/java.kaffe.1.gz /usr/bin/gij-4.1 41 /usr/bin/gij-4.2 42 /usr/bin/gij-4.3 43 /usr/bin/gij-4.4 1044 /usr/bin/gij-wrapper-3.3 33 /usr/share/man/man1/gij-wrapper-3.3.1.gz /usr/bin/rmiregistry-3.3 /usr/share/man/man1/rmiregistry-3.3.1.gz /usr/bin/gij-wrapper-4.0 40 /usr/share/man/man1/gij-wrapper-4.0.1.gz /usr/lib/jvm/java-gcj/jre/bin/java 1043 /usr/lib/jvm/java-gcj/man/man1/java.1.gz > Then this bug should be cloned to that package (or those if needed) > once those cloned bugs are fixed, gcj-4.4-jre-headless and other can > conflicts with the broken versions of those packages. Does this give you enough to work out who needs to fix the bug? > > I would certainly not be happy to see it closed as WONTFIX -- won't this > > break the upgrade process to squeeze for many people? And what is the > > workround? My system is currently broken, how do I fix it? > > Remove the package(s) providing the java alternative that contains the > rmiregistry slave. I tried removing gij-3.3 -- that fixed the problem and gcj-4.4-jre-headless, ecj, ecj-gcj, java-gcj-compat-headless, java-gcj-compat and java-gcj-compat-dev were all able to be configured correctly. No more errors from aptitude! Thanks for your help. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
