vboxapisetup.py - No module named distutils.core => fixed in SVN

[gwr]

Attempting to install VirtualBox-3.0.2-SunOS-r49928.pkg on Solaris Nevada (snv_119) and saw this error:

    pkgadd -d VirtualBox-3.0.2-SunOS-r49928.pkg
    [...]
    ## Executing postinstall script.
    Loading VirtualBox kernel modules...
    VirtualBox Host kernel module loaded.
    VirtualBox NetAdapter kernel module loaded.
    VirtualBox NetFilter kernel module loaded.
    VirtualBox USB kernel module loaded.
    Configuring services and drivers...
    Installing Python bindings...
    Traceback (most recent call last):
      File "./vboxapisetup.py", line 17, in ?
        from distutils.core import setup
    ImportError: No module named distutils.core
    Updating boot archive...
    Done.
    
    Installation of <SUNWvbox> was successful.

My system was installed with the SUNWCuser "cluster", ("End User System Support") not the "full distribution".

The installed Python packages are:

    gwr# pkginfo |grep SUNWPython
    GNOME2      SUNWPython                      The Python interpreter, libraries and utilities
    GNOME2      SUNWPython-extra                Supplemental Python libraries and utilities
    GNOME2      SUNWPython25                    The Python interpreter, libraries and utilities
    GNOME2      SUNWPython26                    The Python interpreter, libraries and utilities
    GNOME2      SUNWPython26-extra              Supplemental Python libraries and utilities

It looks like distutils.core file is part of this package:

    SUNWPython-devel

This solved the problem for me:

    pkgadd -d ... SUNWPython-devel
    pkgrm SUNWvbox
    pkgadd -d VirtualBox-3.0.2-SunOS-r49928.pkg

[gwr]

The "depend" file in the SUNWvbox package really should include

P SUNWPython-devel	The Python interpreter, libraries and utilities - development files

[gwr]

Or alternatively, make that part of the postinstall script check for existence of the distutils.core object and skip setting up the Python bindings if that's missing.

[Ramshankar Venkataraman]

Thanks a lot for the report. This has been fixed in internal SVN and should be part of the next release.