Bogus configuration file prompt on upgrade to trusty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ifupdown (Ubuntu) |
Fix Released
|
Critical
|
Stéphane Graber |
Bug Description
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.
| ==> 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.
| +++ /etc/init.
| @@ -12,6 +12,7 @@
| PATH="/sbin:/bin"
| RUN_DIR=
| IFSTATE=
| +STATEDIR=
|
| [ -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_
| - state=$(cat /run/network/
| + state=$(ifquery --state)
| ifdown -a --exclude=lo $verbose || true
| if ifup --exclude=lo $state $verbose ; then
| log_action_end_msg $?
|
Status changed to 'Confirmed' because the bug affects multiple users.