[Debian-med-packaging] Bug#570739: imagej missing required dependencies

[Bob McGowan]

Package: imagej
Version: 1.43b-1ubuntu1
Severity: normal



-- System Information:
Debian Release: squeeze/sid
  APT prefers karmic-updates
  APT policy: (500, 'karmic-updates'), (500, 'karmic-security'), (500, 'karmic')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.31.6 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages imagej depends on:
ii  default-jre [java2-r 1.6-30ubuntu5       Standard Java or Java compatible R
ii  gcj-4.4-jre [java2-r 4.4.1-5ubuntu2      Java runtime environment using GIJ
ii  gcj-jre [java2-runti 4:4.4.1-1ubuntu2    Java runtime environment using GIJ
ii  openjdk-6-jre [java2 6b16-1.6.1-3ubuntu1 OpenJDK Java runtime, using Hotspo

imagej recommends no packages.

Versions of packages imagej suggests:
pn  java2-compiler                <none>     (no description available)

-- no debconf information

Per email (included below) from Charles Plessy (plessy at debian.org), I'm
creating this report so the 'imagej' dependencies are listed.  The problem
I reported was "fixed" by installing "default-jre" and "gcj-jre", Charles'
speculation that tightening the dependencies may be the correct answer.

---

  Le Sat, Feb 20, 2010 at 06:16:19PM -0800, Bob McGowan a écrit :
  > > Due to not properly generating a JAVA_HOME when the variable is not
  > > defined in the user's environment.
  > > 
  > > I happen to be running Kubuntu, so if I should be sending this to
  > > someone else, let me know who.
  > > 
  > > The error, when running 'imagej', unmodified, on the command line, is:
  > > 
  > >     Open other images in this ImageJ panel as follows:
  > >       imagej -p 1 <image1> [<image2> ... <imageN>]
  > > 
  > >     cat: /usr/share/imagej/jni/*: No such file or directory
  > >     /usr/bin/imagej: line 418: //bin/java: No such file or directory

  Dear Bob,

  I just tried on my computer and did not reproduce the problem. But there are so
  many variants of Java around, maybe the problem comes from that we are not
  using the same combination of packages?

  Do not hesitate to report your problem using the command-line tool ‘reporbug’. It
  will conveniently append a list of packages installed on your system, on which
  imagej depends. That will be very helpful.

  Since you are using kubuntu, you will need to pass the option --bts=debian,
  otherwise your report will go to Launchpad instead. Actually, there seems
  to be a similar report in Launchapd already:

  https://bugs.launchpad.net/ubuntu/+source/imagej/+bug/471127

  Maybe we only have to tighten the dependancies in imagej ?

  Have a nice day,

  --
  Charles Plessy
  Debian Med packaging team,
  http://www.debian.org/devel/debian-med
  Tsurumi, Kanagawa, Japan

---

Bob