dilberts_left_nut wrote:Bugs318 wrote:Still not sure ... why the two upstream packages are said to conflict for only some people
Read the bug report I linked.
You nailed it, friend. I had an issue similar to this. Recently, like yesterday, I installed jessie and was wondering why my networking kept ceasing to work after 5-10 minutes (or so). Checking resolv.conf showed only ipv6 dns servers. I updated the networkmanager config and within a few seconds it prepended the correct ipv4 server to resolv.conf. 5-10 minutes later name resolution had quit again; resolv.conf showed only ipv6 servers again (with no "edited by networkmanager" comment anymore). Per a debian wiki about NetworkManager, I saw my system was using both dhclient and networkmanager, so I presumed dhclient was the culprit. I changed its config to append the correct servers. The problem recurs while I'm trying to run a dist-upgrade. I notice the dist-upgrade shows an unresolvable conflict with rdnssd: "systemd : Breaks: rdnssd (< 1.0.1-5) but 1.0.1-1+b1 is to be installed." I DuckDuckGo that error which brings me here. I decide to remove rdnssd, presuming network manager will take care of ipv6 dns and rolling the dice. The problem stops (and my dist-upgrade to testing resolves conflicts and completes successfully, with ipv6 still functioning).
That bug report you linked,
https://bugs.debian.org/cgi-bin/bugrepo ... bug=740998, perfectly describes the issue. Frank Heckenbach also posted a simple patch that prepends the rdnssd data to resolv.conf rather than overwriting:
Code: Select all
--- /etc/rdnssd/merge-hook
+++ /etc/rdnssd/merge-hook
@@ -23,6 +23,7 @@
if [ -x /sbin/resolvconf ]; then
/sbin/resolvconf -a 000.rdnssd < "$INPUT"
else
- cat -- "$INPUT" > "/etc/resolv.conf"
+ orig=`grep -v ^nameserver "/etc/resolv.conf"`
+ { echo "$orig"; cat -- "$INPUT"; } > "/etc/resolv.conf"
fi
I just wanted to say thanks for posting that as it confirms the behavior I was seeing was indeed a problem where I was not the root cause. As an aside, I reinstalled rdnssd and aptitude showed resolvconf as a dependency (despite rdnssd being installed by default in Jessie but not resolvconf, hence the issues to being with) and from here on out, resolvconf has been properly managing resolv.conf.
I'm a little unsure why Jessie would, during a default graphical install, install rdnssd, dhclient, and NetworkManager but not require resolvconf to properly mediate changes to resolv.conf.