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 KloseThu, 20 Dec 2012 19:13:41 +0100
--
You received this bu
This bug was fixed in the package pygobject - 3.7.3-0ubuntu2
---
pygobject (3.7.3-0ubuntu2) raring; urgency=low
* Rebuild.
* Re-enable the tests for 2.7-dbg. Closes: #1091615.
-- Matthias KloseThu, 20 Dec 2012 19:13:41 +0100
** Changed in: pygobject (Ubuntu)
Status: N
This bug was fixed in the package python2.7 - 2.7.3-12ubuntu5
---
python2.7 (2.7.3-12ubuntu5) raring; urgency=low
* Don't include the _tkinter extension in libpython2.7-dbg.
-- Matthias KloseThu, 20 Dec 2012 14:54:08 +0100
** Changed in: python2.7 (Ubuntu)
Status: Inval
** Branch linked: lp:ubuntu/raring-proposed/python2.7
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1091615
Title:
[raring] recent versions break python2.7-dbg: undefined symbol
yes, the import fails, when you don't have python-gi-dbg installed.
after installing python-gi-dbg, I get:
$ python2.7-dbg -c 'import gi'
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/dist-packages/gi/__init__.py", line 27, in
from ._gi import _API, Rep
Adding a pygobject task then, as something is obviously wrong, but I
don't know what.
0 (master) martin@donald:~/upstream/pygobject
$ git grep Py_InitModule
gi/_glib/pyglib-python-compat.h:PyObject *module =
Py_InitModule(fullpkgname, functions); \
gi/_glib/pyglib-python-compat.h:module =
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 memb
