Bug#540939: upgrade has broken several packages: gcj-4.4-jre-headless cannot be configured
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-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540939: upgrade has broken several packages: gcj-4.4-jre-headless cannot be configured
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-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540939: upgrade has broken several packages: gcj-4.4-jre-headless cannot be configured
On 10.08.2009 23:55, Graham Cobb wrote: Package: gcj-4.4-jre-headless Version: 4.4.1-1 Severity: important Doing 'aptitude safe-upgrade' on my squeeze system has resulted in gcj-4.4-jre-headless being unable to be configured. The aptitude error is: Setting up gcj-4.4-jre-headless (4.4.1-1) ... update-alternatives: error: alternative rmiregistry can't be master: it is a slave of java dpkg: error processing gcj-4.4-jre-headless (--configure): subprocess installed post-installation script returned error exit status 2 This problem then causes several other packages to not be configurable because they have dependency on gcj-4.4-jre-headless. These broken packages are causing other problems and I cannot remove them without uninstalling important packages like openoffice. the recent dpkg doesn't allow mixed master/slave alternatives anymore. Not sure how dpkg deals with this when a user has such packages installed, and then upgrades to the new dpkg. 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. Matthias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540939: upgrade has broken several packages: gcj-4.4-jre-headless cannot be configured
On Fri, 11 Sep 2009, Matthias Klose wrote: Setting up gcj-4.4-jre-headless (4.4.1-1) ... update-alternatives: error: alternative rmiregistry can't be master: it is a slave of java dpkg: error processing gcj-4.4-jre-headless (--configure): subprocess installed post-installation script returned error exit status 2 This problem then causes several other packages to not be configurable because they have dependency on gcj-4.4-jre-headless. These broken packages are causing other problems and I cannot remove them without uninstalling important packages like openoffice. the recent dpkg doesn't allow mixed master/slave alternatives anymore. Not sure how dpkg deals with this when a user has such packages installed, and then upgrades to the new dpkg. On upgrade, dpkg will remove the master alternative rmiregistry if it's also slave of another alternative. You should thus ensure that all packages agree on what's slave and what's master. 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. You should certainly add conflicts or breaks to known packages shipping the bad alternative. You can also clone the bug report and reassign it to the package shipping the bad alternative. Why shouldn't rmiregistry be a slave of java? If it's only because it's shipped in another package, it might not be a big deal. update-alternatives will happily accept missing slaves and the same --install call duplicated in another package will add the slave symlink when the slave has appeared. Cheers, -- Raphaël Hertzog -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540939: upgrade has broken several packages: gcj-4.4-jre-headless cannot be configured
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. 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? Graham -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540939: upgrade has broken several packages: gcj-4.4-jre-headless cannot be configured
Package: gcj-4.4-jre-headless Version: 4.4.1-1 Severity: important Doing 'aptitude safe-upgrade' on my squeeze system has resulted in gcj-4.4-jre-headless being unable to be configured. The aptitude error is: Setting up gcj-4.4-jre-headless (4.4.1-1) ... update-alternatives: error: alternative rmiregistry can't be master: it is a slave of java dpkg: error processing gcj-4.4-jre-headless (--configure): subprocess installed post-installation script returned error exit status 2 This problem then causes several other packages to not be configurable because they have dependency on gcj-4.4-jre-headless. These broken packages are causing other problems and I cannot remove them without uninstalling important packages like openoffice. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (900, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) Locale: lang=en...@euro, lc_ctype=en...@euro (charmap=ISO-8859-15) (ignored: LC_ALL set to en...@euro) Shell: /bin/sh linked to /bin/bash Versions of packages gcj-4.4-jre-headless depends on: ii gcj-4.4-base 4.4.1-1 The GNU Compiler Collection (gcj b ii libc6 2.9-23GNU C Library: Shared libraries ii libgcc11:4.4.1-1 GCC support library ii libgcj10 4.4.1-1 Java runtime library for use with ii zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime gcj-4.4-jre-headless recommends no packages. Versions of packages gcj-4.4-jre-headless suggests: ii fastjar 2:0.97-3 Jar creation utility pn gcj-4.4-jdk none (no description available) pn libgcj10-awt none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
