Summary: | ImportError: No module named bsddb | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sébastien Wilmet <sebastien.wilmet> |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | gentoo |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | My emerge --info |
Description
Sébastien Wilmet
2011-06-22 17:25:05 UTC
What errors are shown in terminal when running exaile from it and reproducing the problem? I solved the problem. Here is the interesting output of exaile --debug: > 17:14:07,411:ERROR : Failed to open music DB. (xl.trax.trackdb) > 17:14:07,412:DEBUG : Exception caught! > Traceback (most recent call last): > File "/usr/lib64/exaile/xl/trax/trackdb.py", line 169, in load_from_location > protocol=common.PICKLE_PROTOCOL) > File "/usr/lib64/python2.7/shelve.py", line 239, in open > return DbfilenameShelf(filename, flag, protocol, writeback) > File "/usr/lib64/python2.7/shelve.py", line 223, in __init__ > Shelf.__init__(self, anydbm.open(filename, flag), protocol, writeback) > File "/usr/lib64/python2.7/anydbm.py", line 82, in open > mod = __import__(result) > File "/usr/lib64/python2.7/dbhash.py", line 7, in <module> > import bsddb > ImportError: No module named bsddb > (xl.trax.trackdb) I found this mail with the same error: http://www.mail-archive.com/python-list@python.org/msg305529.html So the solution is to compile python 2.7 with the 'berkdb' USE flag. Not true. Exaile is not using bsddb, and already has a depend on the database flag "sqlite" which it uses. Works just fine without berkdb. I suppose this is somekind of python upgrade issue... So moving to python maintainers. python ebuild has this: ewarn "You are migrating from =${CATEGORY}/${PN}-${PV%%.*}*[berkdb] to =${CATEGORY}/${PN}-${PV%%.*}*[-berkdb]." ewarn "You might need to migrate your databases." so I suppose the "You might need to migrate your databases." in this case means deleting ~/.local/share/exaile/*.db files, or propably whole ~/.local/share/exaile directory I don't think either one, exaile, or python can do anything more than warn you with that message Close as WORKSFORME? Yes you're right. It was old configuration files. After cleaning ~/.local/share/exaile, it works without berkdb. *** Bug 355367 has been marked as a duplicate of this bug. *** |