Thanks Matthias! I just uploaded a rebuild / reenabling tests, and then saw that you already did that:
pygobject (3.7.3-0ubuntu2) raring; urgency=low * Rebuild. * Re-enable the tests for 2.7-dbg. Closes: #1091615. -- Matthias Klose <[email protected]> Thu, 20 Dec 2012 19:13:41 +0100 -- 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: Fix Released Status in “python2.7” package in Ubuntu: Fix Released 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 : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
