On Fri, 11 Sep 2009, Graham Cobb wrote: > On Friday 11 September 2009 14:24:49 Raphael Hertzog wrote: > > On Fri, 11 Sep 2009, Matthias Klose wrote: > > > the only "fix" I can think of would be adding conflicts to every > > > package listing rmiregistry et al as a slave alternative. But I > > > don't know these packages, so it's likely that we close this report > > > as a won't fix. > > > > You can ask the bug submitter at the very least to find out. > > I'm not sure what I am supposed to be finding out. If someone can explain to > me I am happy to give it a go! By the way, I understand packaging and can > use dpkg and apt. But I am not familiar with how the alternatives system > works.
What is the package that provides the java alternative with the rmiregistry slave ? 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 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. > 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. Cheers, -- Raphaël Hertzog -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
