On 5 February 2015 at 21:28, Thomas Hood <jdth...@gmail.com> wrote: > Second, it might be simpler just for resolvconf to detect that > dnssec-triggerd is running and, in that case, to override the > immutability attribute when installing the symlink at > /etc/resolv.conf.
I have committed the change to resolvconf source so that resolvconf's postinst will remove the immutability attribute from /etc/resolv.conf at configure time if the dnssec-trigger package is installed. This new behavior will appear in (post-Jessie) version 1.77. So a future resolvconf-compatible version of dnssec-trigger should declare "Breaks: resolvconf (<< 1.77)" instead of the current not-versioned "Breaks: resolvconf". Dnssec-trigger could also "Suggests: resolvconf (>= 1.77)". > So (3) resolvconf should then cause > unbound to restart so that unbound notices resolvconf's presence and > registers its address with resolvconf. The way to do this is for the > unbound package to include a script > /usr/lib/resolvconf/dpkg-event.d/unbound which restarts unbound. I should have mentioned that this issue is independent of #776778. We can file a new bug report requesting that unbound include the file in question. Already on my TODO list (... in the resolvconf source tree in the debian/NOTES file: http://anonscm.debian.org/cgit/resolvconf/resolvconf.git/tree/debian/NOTES). -- Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
