Thanks for your reply, Thomas. I now agree that it is the maintainer's
choice as to which of the proposed implementations should be used. I've
made a separate branch with the more complex conditional and attached it
to this ticket.
What's the next step? I'm new to the whole ubuntu package
Thanks for your reply, Thomas. I now agree that it is the maintainer's
choice as to which of the proposed implementations should be used. I've
made a separate branch with the more complex conditional and attached it
to this ticket.
What's the next step? I'm new to the whole ubuntu package
I don't really understand why we need to add a conditional at all. It's
always safe to run resolvconf -u one time too many; but running it one
time too few will introduce subtle bugs (like this one).
The proposed conditional only suppresses running resolvconf -u if
ENABLED=1 and resolvconf is not
I don't really understand why we need to add a conditional at all. It's
always safe to run resolvconf -u one time too many; but running it one
time too few will introduce subtle bugs (like this one).
The proposed conditional only suppresses running resolvconf -u if
ENABLED=1 and resolvconf is not
I agree that the postinst is a better place than the init script to run
resolvconf -u.
I'm not sure that it should be conditional on IGNORE_RESOLVCONF though -
given that the update script will be run next time anything touches
resolvconf, what's to be gained by not running it in the postinst?
I agree that the postinst is a better place than the init script to run
resolvconf -u.
I'm not sure that it should be conditional on IGNORE_RESOLVCONF though -
given that the update script will be run next time anything touches
resolvconf, what's to be gained by not running it in the postinst?
Public bug reported:
The first time that dnsmasq is started, DNS resolution is broken for a
few seconds. You can see this on initial installation:
root@phil-test-1:~# apt-get install dnsmasq ; dig github.com
Reading package lists... Done
Building dependency tree
Reading state information... Done
Public bug reported:
The first time that dnsmasq is started, DNS resolution is broken for a
few seconds. You can see this on initial installation:
root@phil-test-1:~# apt-get install dnsmasq ; dig github.com
Reading package lists... Done
Building dependency tree
Reading state information... Done
