Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#66763 - [unbound] provide python module

Attached to Project: Community Packages
Opened by Vladimir (_v_l) - Sunday, 24 May 2020, 07:32 GMT
Last edited by Bruno Pagani (ArchangeGabriel) - Saturday, 24 July 2021, 16:55 GMT
Task Type Feature Request
Category Packages: Testing
Status Closed
Assigned To David Runge (dvzrv)
Bruno Pagani (ArchangeGabriel)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


Description: unbound upstream provides python module (option '--with-pyunbound' has to be passed to 'configure' script) with 'unbound' sources but currently it is not build and not provided. There is 'python-unbound' package in AUR and it is used by 'hash-slinger' also available in AUR. The 'unbound' package could provides two packages: 'unbound' and 'python-unbound'.
This task depends upon

Closed by  Bruno Pagani (ArchangeGabriel)
Saturday, 24 July 2021, 16:55 GMT
Reason for closing:  Implemented
Additional comments about closing:  unbound 1.13.1-2 thanks to l/511
Comment by Gaetan Bisson (vesath) - Monday, 25 May 2020, 22:42 GMT
I would be happy to ship python bindings as part of the official package with python as optdepends.

However I find that enabling `--with-pyunbound` or `--with-python-module` makes link against That's really too big a hard dependency for such as small package as unbound so that'll have to live in a separate package. Since I have no interest in maintaining this, it's probably best to leave this on the AUR.

But please provide a patch against our PKGBUILD if you know how to enable python bindings without making link against

Comment by Vladimir (_v_l) - Tuesday, 26 May 2020, 05:46 GMT
I made some "workaround" (very "dirty" trick, like 'vim' package do) to provide python module but before present it I would like to understand why there are two python related options. I opened issue on github ( and hope to get answer, may be the linkage against 'libpython' is a bug.