Summary: | [MAINTAINER] dns/unbound upgrade to 1.7.1 | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Jaap Akkerhuis <jaap> | ||||
Component: | Individual Port(s) | Assignee: | Martin Wilke <miwi> | ||||
Status: | Closed FIXED | ||||||
Severity: | Affects Many People | CC: | krion, miwi, portmaster | ||||
Priority: | --- | ||||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
Jaap Akkerhuis
2018-05-03 11:13:42 UTC
A commit references this bug: Author: miwi Date: Thu May 10 14:50:20 UTC 2018 New revision: 469556 URL: https://svnweb.freebsd.org/changeset/ports/469556 Log: - Update to 2.5.9 - Update WWW PR: 227949 Submitted by: maintainer Sponsored by: iXsystems Inc. Changes: head/dns/unbound/Makefile head/dns/unbound/distinfo head/dns/unbound/pkg-descr head/dns/unbound/pkg-plist Perhaps I should start a new pr(1). But this pr references a bug that was supposed to be fixed: - Fix unbound-control get_option aggressive-nsec However, walking up the commits from 1.70, to 1.73 unbound-control stats always returns: # unbound-control stats unbound.conf:22: error: unknown keyword 'aggressive-nsec' unbound.conf:22: error: stray ':' unbound.conf:22: error: unknown keyword 'yes' read unbound.conf failed: 3 errors in configuration file [1539739636] unbound-control[76861:0] fatal error: could not read config file when unbound.conf(5) contains: aggressive-nsec: yes or aggressive-nsec yes Any hopes of ever getting this fixed on FreeBSD? I don't see any more evidence of this error in any of the other commit messages, or pr(1)'s other than this. Thank you! P.S. happens on both 11 && 12 @ 1.70-1.73 (In reply to Chris Hutchinson from comment #2) It seems you have configuration file which is not supported by the version you use. Upgrade to a later version (1.8.1 is the latest). And yes, consider a new pr rather adding to an old closed issue. |