Hi,
Ondřej Surý wrote:
> Then we need to come up with solution that doesn't break resolvconf when
> installing it after dnssec-trigger is already installed.
Just an idea, but what about resolvconf checking in its postinst if
dnssec-triggerd is available and if so restarting it first? Then
dnssec-triggerd would notice that resolvconf is installed (as
/sbin/resolvconf already exists) and talks to resolvconf instead
making /etc/resolv.conf immutable again.
The only question I can't answer: Is resolvconf already ready for that
before the remainder of its postinst has been run.
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
