[Debian-med-packaging] Bug#732222: fiji acted - was:Re: Bug#732222: imagej: does not "see" present JAVA

[Andreas Tille]

Hi Martin,

On Mon, Dec 16, 2013 at 04:30:39PM +0100, Martin Weiser wrote:
> problem solved. Probably there was some interference in setting
> environment variables between Imagej and Fiji.
> 
> I purged Fiji, ImageJ, Java, 
> then re-installed ImageJ:
> ImageJ worked 
> 
> When I added Fiji, ImageJ stopped to work with the originally
> bug-reported quote.
> 
> When I purged Fiji, ImageJ still did not work.
> 
> I purged Imagej and Java again, and then re-installed Imagej.
> ImageJ works.

Thanks for tracking down what we had no chance for!

> Maybe it is openjdk/gcj java problem:
> 
> Simple removal of ImageJ did not helped, as installing Fiji leads to
> installing gcj-java. When there were both these Javas (gcj and openjdk),
> ImageJ refuted to work. 
> 
> It seems to me that maybe the problem is that ImageJ tries to work with
> openjdk Java, while it should work with gcj? Or anything else? (Or maybe
> even better: Fiji should not depend on another Java?)

I have no idea from where you are installing Fiji since there are no
official Debian packages of it.  While we considered this in the past
people who know more about internals of Fiji considered this a bad idea
(there should be some record at the Debian Med list about this
discussion).  In any case it seems to be a bad idea to not depend from
openjdk if you want to run on a recent Debian system.  Those inofficial
Fije packages should be fixed ... or even better the maintainers should
cooperate with us instead of making trouble to their users.

> Thank you for your interest and help.

Thanks for your report in any case.  Please let us know about your ideas
about Fiji maintained in Debian.

Kind regards

      Andreas.

-- 
http://fam-tille.de