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, this gets stored to the conffile database with the md5sum
of /lib/init/upstart-job. Thus, when removing the conffile from the
system in the ifupdown preinst, dpkg views this as a "local diff" to the
previous conffile version and prompts about the local change.
When the first install is from quantal or later, dpkg does *not* store
the md5sum for /etc/init.d/networking -> /lib/init/upstart-job. Instead
it stores the file state as 'newconffile'.
So to reproduce this in a clean raring environment, it's sufficient to
run the following command:
sudo sed -i -e'/etc.init.d.networking/
s/newconffile/ce96a6f22cc836088eef6673d853a765/' /var/lib/dpkg/status
(this is the md5sum of the precise version of /lib/init/upstart-job.)
So this is reproducible, now to figure out how to get around dpkg here.
** Changed in: ifupdown (Ubuntu)
Importance: Undecided => Medium
** Changed in: ifupdown (Ubuntu)
Status: Incomplete => Triaged
--
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1181856/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
