Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#23231 - Bad directory name. Python api is broken.

Attached to Project: Community Packages
Opened by Greg Warner (gdw2) - Thursday, 10 March 2011, 21:45 GMT
Last edited by Ionut Biru (wonder) - Thursday, 10 March 2011, 23:56 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The python interface to the SDK can't find the xpcom module because it's looking in /usr/lib/virtualBox (capital B) when it's really in /usr/lib/virtualbox. When I 'ln -s /usr/lib/virtualbox /usr/lib/virtualBox', things work.


Additional info:
* virtualbox 4.0.4-1
* virtualbox-sdk 4.0.4-1


Steps to reproduce:

Run the following python script:

import vboxapi
b = vboxapi.VirtualBoxManager(None, None)

And you will get this:

Traceback (most recent call last):
File "delme.py", line 2, in <module>
b = vboxapi.VirtualBoxManager(None, None)
File "/usr/lib/python2.7/site-packages/vboxapi/__init__.py", line 514, in __init__
exec "self.platform = Platform"+style+"(platparams)"
File "<string>", line 1, in <module>
File "/usr/lib/python2.7/site-packages/vboxapi/__init__.py", line 350, in __init__
import xpcom.vboxxpcom
ImportError: No module named xpcom.vboxxpcom


This task depends upon

Closed by  Ionut Biru (wonder)
Thursday, 10 March 2011, 23:56 GMT
Reason for closing:  Fixed
Additional comments about closing:  4.0.4-2
Comment by Ionut Biru (wonder) - Thursday, 10 March 2011, 21:56 GMT
thanks for reporting this bug.

the problem is here: VBOX_INSTALL_PATH="/usr/lib/virtualBox"

i'll fix this shortly

Loading...