Bug 195382 - dev-java/java-config-2.1.1 tracebacks when no valid VM is set
|
Bug#:
195382
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: java@gentoo.org
|
Reported By: agaffney@gentoo.org
|
|
Component: Java
|
|
|
URL:
|
|
Summary: dev-java/java-config-2.1.1 tracebacks when no valid VM is set
|
|
Keywords: InCVS
|
|
Status Whiteboard:
|
|
Opened: 2007-10-10 14:12 0000
|
I'm doing a new install, and when I try to select a gen 2 VM with
java-config-2, I get the following traceback:
kirara ~ # java-config-2 -L
Traceback (most recent call last):
File "/usr/bin/java-config-2", line 13, in <module>
from java_config.EnvironmentManager import EnvironmentManager
File "/usr/share/java-config-2/pym/java_config/EnvironmentManager.py", line
444, in <module>
EnvironmentManager = EnvironmentManager()
File "/usr/share/java-config-2/pym/java_config/EnvironmentManager.py", line
35, in __init__
self.load_active_vm()
File "/usr/share/java-config-2/pym/java_config/EnvironmentManager.py", line
103, in load_active_vm
raise InvalidVMError
java_config.Errors.InvalidVMError
If I downgrade to dev-java/java-config-2.0.33-r1, I can run the above command
without a problem. Betelgeuse has confirmed the behavior on a "clean" install.
Thank you, I have confirmed and located the problem, but will not be able to
fix it until tonight.
Thanks for the bug report.
*** Bug 195584 has been marked as a duplicate of this bug. ***
Why is release interested? This only affects ~arch users.
Well, we're trying to track issues that we think might affect us. Quite
frankly, if people are going to be rude about it, then I'm not going to bother
giving a crap, either. Removing release.
*** Bug 195744 has been marked as a duplicate of this bug. ***
New release of java-config is coming, hopefully it has actually hit the rsync
mirrors by now. Closing.