I'm still hitting this bug both under Gutsy and Hardy versions of the
package when importing with python-dbg (2.5) on Amd64. In particular,
with the hardy version:
import pyinotify
Traceback (most recent call last):
File stdin, line 1, in module
File
Bug reopened, I'm hitting exactly the same problem, though when doing it
from python-dbg
** Changed in: pyinotify (Ubuntu)
Status: Fix Released = New
--
Undefined symbol error when importing pyinotify
https://bugs.launchpad.net/bugs/85705
You received this bug notification because you
Ok, sorry, problem is that it lacks a -dbg version. Leaving bug as it
was, and opening a new one as a request.
** Changed in: pyinotify (Ubuntu)
Status: New = Fix Released
--
Undefined symbol error when importing pyinotify
https://bugs.launchpad.net/bugs/85705
You received this bug
And has hit Feisty, so closing this bug.
** Changed in: pyinotify (Ubuntu)
Status: Fix Committed = Fix Released
--
Undefined symbol error when importing pyinotify
https://launchpad.net/bugs/85705
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Your debdiff looks great, applies fine. A test build and install was
fine for both python2.4 and python2.5, so I've uploaded it.
In future please subscribe ubuntu-universe-sponsors, so that someone can
look at it quicker as opposed to me stumbling over it. :-)
--
Undefined symbol error when
** Changed in: pyinotify (Ubuntu)
Status: Unconfirmed = Fix Committed
--
Undefined symbol error when importing pyinotify
https://launchpad.net/bugs/85705
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
It turns out that setup.py doesn't segregate the _inotify.so library
based upon which version of python it's built against. This debdiff
fixes it, by rebuilding the module against the right version of python
before installing it.
** Attachment added: Debdiff to make _inotify.so link against
