[raring] recent versions break python2.7-dbg: undefined symbol: Py_InitModule4_64
Bug #1091615 reported by
Martin Pitt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pygobject (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
python2.7 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
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/
from ._gi import _API, Repository
ImportError: /usr/lib/
[54700 refs]
This also happens when rebuilding pygobject. python2.7, python3.3, and python3.3-dbg are all fine.
Related branches
lp:~barry/ubuntu/raring/python2.7/merged
- Ubuntu branches: Pending requested
-
Diff: 88 lines (+56/-1)4 files modifieddebian/PVER-minimal.postrm.in (+3/-1)
debian/changelog (+27/-0)
debian/patches/series.in (+1/-0)
debian/patches/sys-multiarch.diff (+25/-0)
To post a comment you must log in.
The symbol seems to be there for the non-debug variant:
$ nm -D /usr/lib/ x86_64- linux-gnu/ libpython2. 7.so |grep Py_InitModule
000000000010cd50 T Py_InitModule4_64
but not for _d: x86_64- linux-gnu/ libpython2. 7_d.so |grep Py_InitModule raceRefs_ 64
$ nm -D /usr/lib/
000000000018df84 T Py_InitModule4T
However, that seems to have been the case for quantal as well for that particular library; maybe the symbol was provided by something else in earlier versions?