Yep, here's the executive summary which seems to go right back to when I
installed the system:
laney@iota zgrep ifupdown dpkg.log* | sort -t : -k 2 | sed -n '1p; /upgrade/p'
dpkg.log.7.gz:2012-08-23 16:51:00 install ifupdown none 0.7~beta2ubuntu8
dpkg.log.7.gz:2012-10-18 11:41:42 upgrade
Got it, thanks. So this is reproducible on a system that's continuously
upgraded from precise-quantal-raring-saucy. The reason is that, in
the precise-quantal upgrade, /etc/init.d/networking is taken over as a
conffile from netbase, and due to an ordering difference on upgrade vs.
new install,
** Changed in: ifupdown (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181856
Title:
Conffile prompt for /etc/init.d/networking on update to 0.7.5ubuntu3
To
** Branch linked: lp:ubuntu/ifupdown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181856
Title:
Conffile prompt for /etc/init.d/networking on update to 0.7.5ubuntu3
To manage notifications about
** Changed in: ifupdown (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181856
Title:
Conffile prompt for /etc/init.d/networking on update to
This bug was fixed in the package ifupdown - 0.7.5ubuntu4
---
ifupdown (0.7.5ubuntu4) saucy; urgency=low
* Due to the checkered history of /etc/init.d/networking, only remove the
upstart-job symlink in the preinst if the dpkg status is 'newconffile',
to avoid bogus conffile
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ifupdown (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181856
Title:
(Note that, in theory, we should be able to get all the information we
need to know from /var/lib/dpkg/status... but only *before* this has
been changed by dpkg as part of the upgrade to the new version.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Laney,
Can you please show the full upgrade history of this package on your
system (from /var/log/apt/term.log or /var/log/dpkg.log)? I didn't see
this problem here; I suppose the package took a different upgrade path
on your system historically, resulting in a different state of the
