Package: python3-unbound
Version: 1.8.1-1
Severity: important

The python/python3-unbound packages ship both unbound and unboundmodule python
modules.  The unbound module seems to work (because the swig build for the
compile part is executed and then it is installed).  Currenlty though
unboundmodule is completely non-functional.  This is up to date sid:

Python 3.7.2 (default, Jan  3 2019, 02:55:40)
[GCC 8.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import unboundmodule
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/unboundmodule.py", line 14, in 
swig_import_helper
    return importlib.import_module(mname)
  File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
  File "<frozen importlib._bootstrap>", line 983, in _find_and_load
  File "<frozen importlib._bootstrap>", line 965, in _find_and_load_unlocked
ModuleNotFoundError: No module named '_unboundmodule'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3/dist-packages/unboundmodule.py", line 17, in <module>
    _unboundmodule = swig_import_helper()
  File "/usr/lib/python3/dist-packages/unboundmodule.py", line 16, in 
swig_import_helper
    return importlib.import_module('_unboundmodule')
  File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
ModuleNotFoundError: No module named '_unboundmodule'

The same error occurs with python2.7, the only variation is that paths in the
error message are, of course, different.

Looking at the source, I see compilable code in pythonmod directory that looks
like it is intended to provide the missing _unboundmodule, but I don't see a
functional Makefile to build it (i.e. like libunbound/python/Makefile).

It looks to me like the 'unbound' module wraps libunbound while
'unboundmodule' is meant to wrap the unbound application, so they both look
useful.

It would be nice to make unboundmodule work, but if it's not going to work,
the package shouldn't ship it.  My swig knowledge is approximately zero, so I
was unable to come up with a proper solution.

Scott K

Reply via email to