That is surely a temporary hack, but it seems to me that the real problem is not in libpeas but in python-gobject, where libpyglib-2.0-pythonx.y doesn't get linked to libpython-x.y. I am looking at the sources right now and the package build gives warning about this issue (libpyglib-2.0-pythonx.y uses routines that are not found in none of its libraries). I am not an automake expert, neither I know the architecture of python-gobject, but it seems like a missing -lpythonx.y somewhere.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857348 Title: All python plugins are broken by a bad import To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpeas/+bug/857348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
