resolvconf postrm is broken, purge breaks DNS

[Dan Mick]

apt-get remove resolvconf incorrectly leaves a symlink from /etc/resolv.conf to ../run/resolvconf/resolv.conf. apt-get purge resolvconf leaves that symlink with no target, so DNS is broken.

The problem is in postrm: it's examining /etc/resolv.conf to see if it's a link to /run/resolvconf/resolv.conf, but it's a relative link to ../run/resolvconf/resolv.conf, so the comparison fails, resulting in the failures above.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: resolvconf 1.78ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Jun 16 23:52:41 2016
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: resolvconf
UpgradeStatus: No upgrade log present (probably fresh install)

[Thomas Hood (jdthood)]

Thanks for the bug report. Yes, this is a bug. Here's a patch I have applied to the Debian version which will appear shortly in Debian resolvconf version 1.80. This should fix the bug in the Ubuntu version of the package when it's merged.

[Nish Aravamudan (nacc)]

https://anonscm.debian.org/cgit/resolvconf/resolvconf.git/commit/?id=05a25d1d831ebe3955fb9641a3ba708bca68d35a

1.80 isn't out yet, so we should probably just backport the fix to the affected releases.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.