On Thu, 2015-05-07 at 13:15 +0900, Norbert Preining wrote: > On Thu, 07 May 2015, Michael Biebl wrote: > > The attached patch should fix the issue. Will poke upstream for a review > > and upload tomorrow. > > Thanks for the quick fix!
Got found and fixed yesterday in nm-1-0... In git master there is no longer fallback if resolvconf fails for some reason; but the resolv.conf manager is now a config option. So we'd expect distros to ship a sub-package that drops a config snippet into /etc/NetworkManager/conf.d/ enabling resolvconf which also requires the resolvconf package itself, so that when the config option is set, resolvconf is always installed. We may need some tweaking of the default handling here, but the idea is that if the user specifically chose resolvconf and it fails, that should be a hard failure and NM shouldn't be touching resolv.conf since the user told NM not to... Dan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
