Bugzilla Bug 199003

gramps ebuild ran fine, but when I try to run it, it crashes with the following
traceback from python:

  File "/usr/share/gramps/gramps.py", line 81, in ?
    import gramps_main 
  File "/usr/share/gramps/gramps_main.py", line 57, in ?
    import GrampsBSDDB
  File "/usr/share/gramps/GrampsBSDDB.py", line 37, in ?
    from bsddb import dbshelve, db
  File "/usr/lib/python2.4/bsddb/__init__.py", line 47, in ?
    import _bsddb
ImportError: No module named _bsddb

For a (possible) fix see
http://gramps-project.org/wiki/index.php?title=Install_latest_BSDDB#Remove_old_BSDDB_and_replace_with_new_in_GRAMPS

You have to emerge bsddb3 before applying the changes.
Watch out, it's not only changing "import bsddb" but also some lines starting
with "from bsddb."!

Worked for me, gramps 2.2.8 is running just fine now.

Adam, could you please check if comment #1 helps you?

Yep, the directions worked to fix the problem, thanks.

Closing then.

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

(In reply to comment #4)
> Closing then.

Manually messing with installed files != fix. 

Please make a patch that solves this. Because editing the source files of a
ebuild 
to get a package to work is not the solution.

(In reply to comment #7)
> Please make a patch that solves this.

There's no patch needed for this; this is a python issue (see Bug 179377).

I see...his problem seems to take ages to fix....It's been about 8 months since
the python problem was reported.

(In reply to comment #9)
> I see...his problem seems to take ages to fix....It's been about 8 months since
> the python problem was reported.

 Maybe the bug slipped for the Python team...I will commit the fix as soon as I
made clear if the proposed fix is sane.  It uses some features from EAPI=1
(slot dependencies) and I will check with someone else.  Or do you know
something that stands against EAPI=1 in the (stable) tree, jakub?

(In reply to comment #10)
> something that stands against EAPI=1 in the (stable) tree, jakub?

Hmmm? No, there's tons of stuff using EAPI=1 now. Just make sure to revbump the
thing and get it stabilized ASAP, thanks... ;)

Fixed I hope.  Closing. -r9 should go stable soon, I try to take care of it.

(In reply to comment #12)
> Fixed I hope.  Closing. -r9 should go stable soon, I try to take care of it.
> 

Still waiting on this to go stable ...

(In reply to comment #13)
> (In reply to comment #12)
> > Fixed I hope.  Closing. -r9 should go stable soon, I try to take care of it.
> Still waiting on this to go stable ...

 You sure have talent for it...give it some time, python team did not react to
my request, but I will come to it next week (need to check there are no other
bugs holding it back).