Bug 195382 – dev-java/java-config-2.1.1 tracebacks when no valid VM is set

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Andrew Gaffney (RETIRED) 2007-10-10 14:12:40 UTC]

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.

[Comment 1 Alistair Bush (RETIRED) 2007-10-10 17:59:15 UTC]

Thank you, I have confirmed and located the problem, but will not be able to fix it until tonight.

Thanks for the bug report.

[Comment 2 Andrew Gaffney (RETIRED) 2007-10-12 11:42:44 UTC]

*** Bug 195584 has been marked as a duplicate of this bug. ***

[Comment 3 Petteri Räty (RETIRED) 2007-10-12 19:21:32 UTC]

Why is release interested? This only affects ~arch users.

[Comment 4 Chris Gianelloni (RETIRED) 2007-10-13 17:06:51 UTC]

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.

[Comment 5 Alistair Bush (RETIRED) 2007-10-13 20:14:31 UTC]

*** Bug 195744 has been marked as a duplicate of this bug. ***

[Comment 6 Alistair Bush (RETIRED) 2007-10-14 01:36:34 UTC]

New release of java-config is coming, hopefully it has actually hit the rsync mirrors by now.  Closing.