Bug#1019140: unbound-resolvconf.service will always be in failed state when you set RESOLVCONF=false

2023-01-12 Thread Michael Tokarev
12.01.2023 18:40, Michael Tokarev wrote: Control: tag -1 + moreinfo On Tue, 4 Oct 2022 17:31:42 +0200 Thomas Deutschmann wrote: Hi, may I suggest to apply the following changes? >  do_resolvconf_start() { > -    [ false != "$RESOLVCONF" -a -x /sbin/resolvconf ] || return > +    [ false !=

Bug#1019140: unbound-resolvconf.service will always be in failed state when you set RESOLVCONF=false

2023-01-12 Thread Michael Tokarev
Control: tag -1 + moreinfo On Tue, 4 Oct 2022 17:31:42 +0200 Thomas Deutschmann wrote: Hi, may I suggest to apply the following changes? > do_resolvconf_start() { > -[ false != "$RESOLVCONF" -a -x /sbin/resolvconf ] || return > +[ false != "$RESOLVCONF" -a -x /sbin/resolvconf ] ||

Bug#1019140: unbound-resolvconf.service will always be in failed state when you set RESOLVCONF=false

2022-10-04 Thread Thomas Deutschmann
Hi, may I suggest to apply the following changes? $ diff -u /usr/libexec/unbound-helper.ori /usr/libexec/unbound-helper --- /usr/libexec/unbound-helper.ori 2022-10-04 17:25:48.531922943 +0200 +++ /usr/libexec/unbound-helper 2022-10-04 17:26:58.143255583 +0200 @@ -24,7 +24,7 @@ fi

Bug#1019140: unbound-resolvconf.service will always be in failed state when you set RESOLVCONF=false

2022-09-04 Thread Thomas Deutschmann
Package: unbound Version: 1.16.2-1 Severity: normal Dear Maintainer, I am using unbound as recursive dns resolver for my local network, not just for localhost. My /etc/resolv.conf is mintainted by systemd-resolved and DNS server gets set by systemd-networkd. In the past,