On Tue, 5 Jul 2005, Jeremy C. Reed wrote:

> I am not sure how to turn on any debugging or troubleshoot python errors.
>
> On another system, running gramps fails with:
>
> Fatal Python error: could not import ORBit module
> Aborted

I ran python2.4 and did an "import ORBit" and clearly saw the problem:

>>> import ORBit
Traceback (most recent call last):
   File "<stdin>", line 1, in ?
ImportError: libglib-2.0.so.400: cannot open shared object file: No such 
file or directory

And then ldd and objdump led me to a broken libIDL package from last 
October.

Then running gramps again, I get back to my first problem (as I saw on 
other system):

montecristo:/usr/lib$ gramps
Traceback (most recent call last):
   File "/usr/share/gramps/gramps.py", line 81, in ?
     import gramps_main
   File "/usr/share/gramps/gramps_main.py", line 56, in ?
     import GrampsBSDDB
   File "/usr/share/gramps/GrampsBSDDB.py", line 36, in ?
     from bsddb import dbshelve, db
   File "/usr/lib/python2.4/bsddb/__init__.py", line 47, in ?
     import _bsddb
ImportError: No module named _bsddb

I see that lang/python24/patches/patch-am has:

+disabled_module_list = ["_bsddb", "_curses", "_curses_panel", "_tkinter", "bsddb", "gdbm", "mpz", "pyexpat", "readline"]

What should I do?

  Jeremy C. Reed

  	  	 	 BSD News, BSD tutorials, BSD links
 	  	 	 http://www.bsdnewsletter.com/