Hi, I'm having trouble working out the correct way to fix this. On an upgrade to opennms with a new package I've built it fails as JAVA_HOME is not set in /etc/default/opennms.
The postinst script should work, although the current logic prefers runjava -s over manually hacking the JAVA_HOME: if [ -x /usr/lib/jvm/java-6-openjdk/bin/java ]; then /usr/share/opennms/bin/runjava -q -S /usr/lib/jvm/java-6-openjdk/bin/java || : (grep -v ^JAVA_HOME /etc/default/opennms ; echo 'JAVA_HOME=/usr/lib/jvm/java-6-openjdk') > /etc/default/opennms.new mv /etc/default/opennms.new /etc/default/opennms However the runjava script prefers to set-up the configuration in $opennms_home/etc/java.conf which is not where the init script looks. I'm assuming the use of runjava in the postinst script was intended so should I just make runjava debian aware? While on the subject, what was the rational of separating the debian module from the rest of the src tree? I only mention it as the first thing I did in my tree was add the debian dir back into my main repo so it could be updated alongside the rest of opennms. -- Alex Bennee, Software Engineer What the world *really* needs is a good Automatic Bicycle Sharpener. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-devel mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-devel