Bug 200282 – ebuild <foo> unpack backtrace

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Carsten Lohrke (RETIRED) 2007-11-25 13:30:42 UTC]

Intended to unpack jdbc-jaybird-2.1.0-r1, which apparentely needs Java 1.5, which I do not have installed. Fine so far, but Portage went wild on it:

Traceback (most recent call last):
  File "/usr/bin/depend-java-query", line 85, in ?
    (options, args) = parser.parse_args()
  File "/usr/lib/python2.4/optparse.py", line 1277, in parse_args
    stop = self._process_args(largs, rargs, values)
  File "/usr/lib/python2.4/optparse.py", line 1317, in _process_args
    self._process_long_opt(rargs, values)
  File "/usr/lib/python2.4/optparse.py", line 1392, in _process_long_opt
    option.process(opt, value, values, self)
  File "/usr/lib/python2.4/optparse.py", line 709, in process
    return self.take_action(
  File "/usr/lib/python2.4/optparse.py", line 728, in take_action
    self.callback(self, opt, value, parser, *args, **kwargs)
  File "/usr/bin/depend-java-query", line 49, in get_vm
    vm = verman.get_vm(value)
  File "/usr/share/java-config-2/pym/java_config/VersionManager.py", line 154, in get_vm
    raise Exception("Couldn't find suitable VM. Possible invalid dependency string.")
Exception: Couldn't find suitable VM. Possible invalid dependency string.
 * Unable to determine VM for building from dependencies:
NV_DEPEND: || ( =virtual/jdk-1.5* =virtual/jdk-1.4* )
        app-arch/unzip
        dev-java/log4j
        jni? ( dev-java/cpptasks )
        test? (
                dev-java/junit
                dev-java/ant-junit
        )  >=dev-java/java-config-2.0.33-r1 >=sys-apps/portage-2.1.2.7 source? ( app-arch/zip ) >=dev-java/javatoolkit-0.2.0-r1 >=sys-apps/portage-2.1.2.7  dev-java/ant-core
VNEED:
 *
 * ERROR: dev-java/jdbc-jaybird-2.1.0-r1 failed.


Please let Portage act a little more graceful in such a case.

[Comment 1 Carsten Lohrke (RETIRED) 2007-11-25 13:34:00 UTC]

Um, should cc the Java team, as it is java-config producing the error in the first place.

[Comment 2 Alistair Bush (RETIRED) 2007-11-25 18:18:22 UTC]

Fix is InSVN.  This is purely a java-config error,  and portage is behaving as it should, IMO.

output of java-config should be

> depend-java-query -v "=virtual/jdk-1.7*"
> !!! ERROR: Couldn't find suitable VM. Possible invalid dependency string.

I am going to try push the java-config release this week.

[Comment 3 Alistair Bush (RETIRED) 2010-03-09 11:09:24 UTC]

This has been fixed for a long time.  Time to be closed.