Version 3.4.0 seem to change build behavior, the bind backend is no longer included when not configured explicitly. Upgrading 3.3.1 to 3.4.0 causes bind style zone files to not longer load on startup due to missing bind backend. A small addition to the ebuild is required to restore old behavior or a new USE flag for the bind backend needs to be introduced. Reproducible: Always Steps to Reproduce: 1. upgrade from 3.3.1 to 3.4.0 2. bind style zone files will no longer load, missing bind backend support 3. analyze log output of crashed startup Actual Results: bind backend in default build is missing Expected Results: behavior of versions < 3.4.0 with default support of bind style zone files via included backend module Needed trivial ebuild patch: --- /usr/portage/net-dns/pdns/pdns-3.4.0.ebuild 2014-10-23 13:15:39.000000000 +0200 +++ /usr/local/portage/net-dns/pdns/pdns-3.4.0.ebuild 2014-10-25 01:38:52.428480393 +0200 @@ -54,7 +54,7 @@ doc? ( app-doc/doxygen )" src_configure() { - local dynmodules="pipe geo" # the default backends, always enabled + local dynmodules="pipe geo bind" # the default backends, always enabled local modules="" #use db2 && dynmodules+=" db2"
Confirmed with upstream. Neglected to read the CHANGELOG when I modified the ebuild for Bug #518930. Woops! Your fix works for me :)
pdns-3.4.1 has been merged with these fixes, can this be closed?
3.4.1 is running without any issues on my test boxes. I would promote closing.
You should be able to close this yourself seeing as you are the reporter :)
