Bug#335479: /usr/share/man/man1/rmic.1.gz is a dangling symlink

[Wolfgang Baer <WBaer@gmx.de>]

tags 335479 + patch
thanks

Hi Thomas,

Thomas Schoepf wrote:
> Hello Wolfgang,
> 
> 
>>OK is it correctly configured and do you have java-gcj-compat-dev
>>installed and configured (its the one providing rmic) ?
> 
> 
> No, java-gcj-compat-dev is not installed. There are no depend, recommend or
> suggest headers with java-gcj-compat.

Thats right. java-gcj-compat is the JRE  and java-gcj-compat is the JDK
like java environment. There is no point to suggest or recommend a JDK
if one installs a JRE.

> Why is java-gcj-compat registering an alternative for a file that it does
> not contain? That's how I understand the problem at the moment.

Well, package structure changes and mistakes happens. But know I found
the problem ...

GCC-Maintainers:
The postinst registers rmic instead of rmiregistry and the prerm does
not deregister gcj-dbtool - Patches (against 1.0.41-2) attached.

Wolfgang

--- debian/java-gcj-compat.postinst.orig	2005-10-25 13:54:12.000000000 +0000
+++ debian/java-gcj-compat.postinst	2005-10-25 13:56:35.000000000 +0000
@@ -14,8 +14,8 @@
 }
 
 jdk_alternative jar
-jdk_alternative rmic
 jdk_alternative java
+jdk_alternative rmiregistry
 jdk_alternative gcj-dbtool
 
 #DEBHELPER#

--- debian/java-gcj-compat.prerm.orig	2005-10-25 13:57:04.000000000 +0000
+++ debian/java-gcj-compat.prerm	2005-10-25 13:57:23.000000000 +0000
@@ -12,5 +12,6 @@
 jdk_alternative jar
 jdk_alternative java
 jdk_alternative rmiregistry
+jdk_alternative gcj-dbtool
 
 #DEBHELPER#