OK, so the symbol is expected, but is breaking "import gi" expected as
well? What could the "gi" module do wrong that triggers this with the
new python2.7?
** Also affects: pygobject (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1091615
Title:
[raring] recent versions break python2.7-dbg: undefined symbol:
Py_InitModule4_64
Status in “pygobject” package in Ubuntu:
New
Status in “python2.7” package in Ubuntu:
Invalid
Bug description:
One of the last python2.7 uploads seems to have broken the -dbg
variant:
$ python2.7-dbg -c 'import gi'
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/lib/python2.7/dist-packages/gi/__init__.py", line 27, in <module>
from ._gi import _API, Repository
ImportError: /usr/lib/python2.7/dist-packages/gi/_gi.so: undefined symbol:
Py_InitModule4_64
[54700 refs]
This also happens when rebuilding pygobject. python2.7, python3.3, and
python3.3-dbg are all fine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1091615/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
