This bug was fixed in the package python-jpype - 0.5.4.2-3
---
python-jpype (0.5.4.2-3) unstable; urgency=low
[ Jakub Wilk ]
* Use canonical URIs for Vcs-* fields.
[ TANIGUCHI Takaki ]
* Bump Standards Version to 3.9.4 (with no changes).
* debian/patches/default_jvm_path:
** Changed in: python-jpype (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1023806
Title:
jpype.getDefaultJVMPath() fails
To manage notifications ab
** Changed in: python-jpype (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1023806
Title:
jpype.getDefaultJVMPath() fails
To manage notifications about t
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python-jpype (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1023806
Title:
I've opened a companion bug with Debian as the problem exists there too.
( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683048 )
As a workaround you can set the JAVA_HOME enviroment variable. Assuming
that the JVM was installed in /usr/lib/jvm/java-7-openjdk-amd64/ you run
python like this:
