Bogus configuration file prompt on upgrade to trusty

[James Troup]

While upgrading from saucy to trusty, I get asked about modifications
to a configuration file I know I haven't modified:

| Setting up ifupdown (0.7.47.2ubuntu1) ...
|
| Configuration file '/etc/init.d/networking'
| ==> Modified (by you or by a script) since installation.
| ==> Package distributor has shipped an updated version.
| What would you like to do about it ? Your options are:
| Y or I : install the package maintainer's version
| N or O : keep your currently-installed version
| D : show the differences between the versions
| Z : start a shell to examine the situation
| The default action is to keep your current version.
| *** networking (Y/I/N/O/D/Z) [default=N] ? d
| --- /etc/init.d/networking 2013-08-26 22:19:11.000000000 +0000
| +++ /etc/init.d/networking.dpkg-new 2013-11-14 21:19:15.000000000 +0000
| @@ -12,6 +12,7 @@
| PATH="/sbin:/bin"
| RUN_DIR="/run/network"
| IFSTATE="$RUN_DIR/ifstate"
| +STATEDIR="$RUN_DIR/state"
|
| [ -x /sbin/ifup ] || exit 0
| [ -x /sbin/ifdown ] || exit 0
| @@ -55,6 +56,9 @@
| log_failure_msg "can't create $RUN_DIR"
| exit 1
| fi
| + if ! chown root:netdev "$RUN_DIR" ; then
| + log_warning_msg "can't chown $RUN_DIR"
| + fi
| fi
| if [ ! -r "$IFSTATE" ] ; then
| if ! :> "$IFSTATE" ; then
| @@ -163,7 +167,7 @@
| process_options
|
| log_action_begin_msg "Reloading network interfaces configuration"
| - state=$(cat /run/network/ifstate)
| + state=$(ifquery --state)
| ifdown -a --exclude=lo $verbose || true
| if ifup --exclude=lo $state $verbose ; then
| log_action_end_msg $?
|

[Launchpad Janitor (janitor)]

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

[Stéphane Graber (stgraber)]

As I just said in the bug report I just marked as duplicate to this one, I'm unable to reproduce this from a clean 13.10 system upgrading to 14.04.

So there's clearly some upgrade path which messes things up (since both report contain an identical diff) but I don't have enough information to figure out what happened there as it's not as simple as 13.10 to 14.04...

Can anyone with this bug provide more history about their systems? What was the initial release installed on the box, what release upgrades did you do after that, ... ?

Thanks

[Stéphane Graber (stgraber)]

We may end up simply whitelisting the conffile in question and workaround the issue that way, but being able to reproduce it would be quite helpful...

[James Troup (elmo)]

Stéphane Graber <email address hidden> writes:

> Can anyone with this bug provide more history about their systems?
> What was the initial release installed on the box, what release
> upgrades did you do after that, ... ?

My system was installed as oneiric and has been upgraded to every
release in between, usually around the time of beta.

--
James

[Launchpad Janitor (janitor)]

This bug was fixed in the package ifupdown - 0.7.47.2ubuntu3

---------------
ifupdown (0.7.47.2ubuntu3) trusty; urgency=medium

  * Fix the preinst to match the current networking.init. (LP: #1283274)
 -- Stephane Graber <email address hidden> Thu, 03 Apr 2014 17:34:53 -0400