Package: dnssec-trigger Version: 0.13~svn685-3 Severity: important Control: affects -1 resolvconf
Dear Maintainer, installing resolvconf while dnssec-triggerd is running causes the installation of resolvconf to fail as follows: Setting up resolvconf (1.76.1) ... resolvconf.postinst: Error: Cannot replace the current /etc/resolv.conf with a symbolic link because it is immutable; to correct this problem, gain root privileges in a terminal and run 'chattr -i /etc/resolv.conf' and then 'dpkg --configure resolvconf'; aborting dpkg: error processing package resolvconf (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: resolvconf As far as I know, it's dnssec-triggerd which makes /etc/resolv.conf immutable and I can understand that measure. The workaround is to stop dnssec-triggerd (e.g. with "service dnssec-triggerd stop"), then install resolvconf (or run "dpkg --configure resolvconf" as suggested if it already failed), and then start dnssec-triggerd again (e.g. with "service dnssec-triggerd start"). -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (110, 'experimental'), (109, 'buildd-unstable'), (109, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.18.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dnssec-trigger depends on: ii gir1.2-networkmanager-1.0 0.9.10.0-5 ii init-system-helpers 1.22 ii libc6 2.19-14 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk2.0-0 2.24.25-1 ii libldns1 1.6.17-5+b1 ii libssl1.0.0 1.0.1k-1 ii python 2.7.8-2 ii python-gi 3.14.0-1 ii python-lockfile 1:0.8-2 ii unbound 1.4.22-3 dnssec-trigger recommends no packages. dnssec-trigger suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
