Bug#534446: java-gcj-compat-dev: update-alternatives error when installing in a buildd

[Matthias Klose <doko@debian.org>]

Gustavo Noronha Silva schrieb:
> Package: java-gcj-compat-dev
> Version: 1.0.80-5
> Severity: important
> 
> Installing this package in an otherwise clean environment (used as a
> buildd), I get the following:
> 
> Setting up java-gcj-compat-dev (1.0.80-5) ...
> update-alternatives: error: alternative path /usr/lib/jvm/java-gcj/bin/jarsigner doesn't exist.
> dpkg: error processing java-gcj-compat-dev (--configure):
>  subprocess installed post-installation script returned error exit status 2
> dpkg: dependency problems prevent configuration of default-jdk:
>  default-jdk depends on java-gcj-compat-dev (>= 1.0.77-4); however:
>   Package java-gcj-compat-dev is not configured yet.
> dpkg: error processing default-jdk (--configure):
>  dependency problems - leaving unconfigured
> dpkg: dependency problems prevent configuration of default-jdk-builddep:
>  default-jdk-builddep depends on default-jdk (= 1.5-32); however:
>   Package default-jdk is not configured yet.
> dpkg: error processing default-jdk-builddep (--configure):
>  dependency problems - leaving unconfigured
> Errors were encountered while processing:
>  java-gcj-compat-dev
>  default-jdk
>  default-jdk-builddep
> E: Sub-process /usr/bin/dpkg returned an error code (1)

strange. /usr/lib/jvm/java-gcj is a symlink pointing to the directory
java-1.5.0-gcj-4.3-1.5.0.0, which is in the java-gcj-compat-headless package.
Still not seeing how the path /usr/lib/jvm/java-gcj/bin/jarsigner is
non-existant. Plus jarsigner is not the first alternative which is created, and
there doesn't seem to be an error for appletviewer.