broken upgrade or whitespace diff?

Bug #1647393 reported by Dimitri John Ledkov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
resolvconf (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I got a conffile prompt off:

$ diff -u head head.dpkg-old
--- head 2016-11-28 23:37:41.000000000 +0000
+++ head.dpkg-old 2016-01-27 06:04:06.414599155 +0000
@@ -1,5 +1,3 @@
 # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
 # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
-# 127.0.0.53 is the systemd-resolved stub resolver.
-# run "systemd-resolve --status" to see details about the actual nameservers.

Is this just a whitespace difference? Or is there a broken conf upgrade.

Changed in resolvconf (Ubuntu):
assignee: nobody → Steve Langasek (vorlon)
Revision history for this message
Steve Langasek (vorlon) wrote :

> Is this just a whitespace difference? Or is there a broken conf upgrade.

Neither. With a pristine yakkety version, dist-upgrade does not give me a conffile prompt. It seems that somehow dpkg had a wrong checksum recorded for your previous version of the conffile.

Changed in resolvconf (Ubuntu):
status: New → Incomplete
Steve Langasek (vorlon)
Changed in resolvconf (Ubuntu):
assignee: Steve Langasek (vorlon) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for resolvconf (Ubuntu) because there has been no activity for 60 days.]

Changed in resolvconf (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.