Upgrade Error

[stevepusser]

The error message is misleading; "is to be installed" actually means that older version is already installed. I'd focus on trying to upgrade rdnssd to the testing version with aptitude with the simulation "-s" argument and see if any informative errors show up there...you don't have it pinned for any reason, do you? Other people have had the same kind of issues in posts here, and it turned out to be a pinned package they had forgotten.

[Bugs318]

I have pinned packages in other distros before, but don't believe I have here. I do not have a /etc/apt/preferences file. There is an /etc/apt/preferences.d directory, but it is empty (even of hidden files). Is there anywhere else I can verify if I pinned it and forgot?

If run with the -s it still asks about uninstalling required packages. If I click yes, will it simulate the removal there too without actually doing so?

Another thought: would it be possible to remove rdnssd and then install it, or update then install it, as the source pointed to by both apt and aptitude is the current testing package?

[stevepusser]

Usually, you should be able to directly download the deb package from the bottom of this page and install it with dpkg. It looks like it doesn't depend on any other testing packages.

[Bugs318]

dpkg tells me that it conflicts with network-manager, but I presume network-manager likely also has a non-conflicting upgraded version too that I can reinstall later?

[Bugs318]

Hmmm, latest package of network manager is the one aptitude and apt tell me that upgraded versions of rdnssd conflict with (1.2.4-2) I MAY be the only one who has a stable version of rdnssd installed in a testing system, but I can't be the only one being told the newest versions of these two packages in testing conflict, can I?

[stevepusser]

Pretty weird...what's the exact error message? Sometime you can add the "-B" argument to the "dpkg -i" command to allow affected packages to deconfigure and then reconfigure with the new version, but I don't know if that's what's happening here.

You can also get older testing versions of the deb to try and install, if that helps: http://snapshot.debian.org/binary/rdnssd/

[kiyop]

I have a system from zareason. They claim to have installed testing as per my request. The install disc they sent with my install was, indeed, testing.

Why not asking zareason?
http://zareason.com/shop/contact.html
Why did you request testing?

I will never buy PC/laptop from zareason

http://forums.debian.net/viewtopic.php? ... 13#p624052

433 not upgraded.

Why not executing "apt full-upgrade"?

derek@derek-laptop2: 1779: /etc/apt/sources.list.d$upgrade

One of my debian stable's does not have a command "upgrade".
Did you write some custom script for "upgrade" or an alias for "upgrade"?
If yes, post the concrete contents of it.
If not, execute the following and post the result:

Code: Select all

which upgrade

I suggest you installing stable, without using the install disc given by zareason, and upgrading to testing if you dare to use testing.

[Bugs318]

dpkg error message:

dpkg: regarding rdnssd_1.0.1-6_amd64.deb containing rdnssd:
rdnssd conflicts with network-manager
network-manager (version 1.2.4-2) is present and installed.

dpkg: error processing archive rdnssd_1.0.1-6_amd64.deb (--install):
conflicting packages - not installing rdnssd
Errors were encountered while processing:
rdnssd_1.0.1-6_amd64.deb


'upgrade' is alias for 'sudo apt-get dist-upgrade' as mentioned earlier.

[dilberts_left_nut]

That looks straightforward - pick one and remove the other.

edit: https://bugs.debian.org/cgi-bin/bugrepo ... bug=740998

[Bugs318]

Is removing rdnssd generally an option? I thought it was a required system file?

[bw123]

Is removing rdnssd generally an option? I thought it was a required system file?

Bugs318

Posts: 30
Joined: 2010-05-25 14:48

i found this on a web search

rdnssd(8) - Linux man page
rdnssd is a daemon program providing client-side support for DNS configuration using the Recursive DNS Server (RDNSS) option, as described in RFC 5006.
linux.die.net/man/8/rdnssd

I think I agree with this post
http://forums.debian.net/viewtopic.php? ... 88#p624171

If aptitude can't come up with a solution, your path seems clear.

p.s. oh yeh by the way, this might be a good time to backup any data you don't want to lose, these things seems to spiral into who-knows-what very unpredictably.

[kiyop]

You executed "sudo apt-get update", didn't you?

Is removing rdnssd generally an option? I thought it was a required system file?

One of my debian jessie's does not have rdnssd

Code: Select all

$ LANG=C apt-cache policy rdnssd
rdnssd:
  Installed: (none)
  Candidate: 1.0.1-1+b1
  Version table:
     1.0.1-1+b1 0
        500 http://ftp.jp.debian.org/debian/ jessie/main i386 Packages

I don't know if your debian requires a daemon program providing client-side support for DNS configuration using the Recursive DNS Server (RDNSS) option, as described in RFC 5006 or not.

[Bugs318]

Well, I removed rdnssd and it seems to be working smoothly without. Good to know. Still not sure how that happened, nor why the two upstream packages are said to conflict for only some people, but it seems this fix is working for me.

Thanks to all who contributed.

[dilberts_left_nut]

Still not sure ... why the two upstream packages are said to conflict for only some people

Read the bug report I linked.

[Kajisav]

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.

[manosgem]

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.

I have the exact same problems as you , did upgrading solve connection issues ?
Can you please tell me the exact steps to follow (also commands to run)?
Up to now I decided to upgrade to Stretch , and the final apt-get dist-upgrade got me the same error and by chance I also "DuckDuckGo" that same error and got to this post.