I would think the python-gnucash dependency issue is a packaging bug. One could mark python-gnucash as a mandatory dependency. That may cause circular dependencies though because python-gnucash should depend on gnucash.
The other option is alter the package contents slightly. (Caveat: I'm not a packager so I may be talking nonsense) >From gnucash' point of view the python binding are really optional. It will not try to load any python script if the module libgncmod_python.so is not found. So I think that if this module is moved to the python- gnucash package, python-gnucash can really be a true optional module. There may be one issue: if python-gnucash is an architecture independent package, libgncmod_python.so can't just moved into that package because that would make it architecture dependent. If that's the case, I'll have to pass the issue to real packagers... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1369273 Title: gnucash crashed with ImportError in /usr/share/gnucash/python/init.py: No module named gnucash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1369273/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
