Installation fails even if openjdk-6-jdk is installed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tomcat5.5 (Debian) |
Fix Released
|
Unknown
|
|||
tomcat5.5 (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Hardy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: tomcat5.5
I just installed tomcat5.5 from Hardy. It installed openjdk-6-jre, so the init script failed at line 48 because openjdk-6-jre does not include bin/jdb
As bug #179447 explains, bin/jdb is part of a -jdk vs. a -jre package, and tomcat5.5's dependencies should ensure one is installed. It seems to me this could be achieved by depending on "java2-sdk" instead of "java2-runtime". I added this comment to Debian bug #458412, however I admittedly know little about the Java packaging policy...
In the meantime, I installed openjdk-6-jdk, but the tomcat5.5 init script still fails because line 40 does not include "/usr/lib/
[/etc/init.
JDK_DIRS=
# Look for the right JVM to use
for jdir in $JDK_DIRS; do
[...]
Perhaps a more maintainable way to find the right JVM would be to:
for jdir in /usr/lib/jvm/*; do
[...]
- or perhaps JAVA_HOME=/usr would work, since /usr contains bin/java and bin/jdb. This would keep the default JAVA_HOME consistent with /etc/alternatives
Again, I confess to knowing little about the Java packaging policy.
Thanks for maintaining Tomcat, Jack
Changed in tomcat5.5: | |
status: | Triaged → In Progress |
Changed in tomcat5.5: | |
status: | Unknown → Fix Committed |
Changed in tomcat5.5: | |
status: | Fix Committed → Fix Released |
Changed in tomcat5.5 (Debian): | |
status: | Fix Released → New |
Changed in tomcat5.5 (Debian): | |
status: | New → Fix Released |
debdiff for Hardy.