On Mon, 8 Aug 2011, Tom Hendrikx wrote:

I did some more research on this and I think I found the culprit.
Attached is a patch against unbound 1.4.12 that adds the site-packages
dir to the search path when initialising the python module.

With this patch, things Work For Me (tm) :)

I can confirm this fixes the pythonmod loading! Thanks! I've built it
for fedora rawhide, and over the next few days should trickly up in all
branches.

Wouter: Please apply patch to git^Wsvn


We're still seeing installs in the wrong dir though:

[paul@bofh unbound]$ rpm -ql unbound-python
/usr/lib/python2.7/site-packages/_unbound.so
/usr/lib/python2.7/site-packages/_unbound.so.2
/usr/lib/python2.7/site-packages/_unbound.so.2.12.0
/usr/lib/python2.7/site-packages/unbound.py
/usr/lib/python2.7/site-packages/unbound.pyc
/usr/lib/python2.7/site-packages/unbound.pyo
/usr/lib/python2.7/site-packages/unboundmodule.py
/usr/lib/python2.7/site-packages/unboundmodule.pyc
/usr/lib/python2.7/site-packages/unboundmodule.pyo

That should be /usr/lib64/ not /usr/lib/

Paul
_______________________________________________
Unbound-users mailing list
[email protected]
http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users

Reply via email to