lucid->precise upgrade - prompt to update unmodified conf files: /etc/init/networking.conf /etc/init/network-interface.conf , /etc/network/if-up.d/upstart

It's incredibly unlikely for these config files to have been modified as part of a normal system install. Please attach the modified conffiles in question.

Also, how did you do this fresh install of lucid?

The base Lucid system was installed in 2 different ways:
1. From a Lucid 10.04.3 Server ISO
2. With vmbuilder

After the initial installation:
1. Update the system:
  $ apt-get update && apt-get dist-upgrade
2. Reboot
3. Upgrade
  $ do-release-upgrade -d

When prompted for a configuration change, I selected to keep the install version.

Configuration files attached (original config files without .dpkg-dist extension)

Each of the files you've attached exactly matches the one from the lucid-updates version of the package.

What was the version of ifupdown shown to be installed on the system prior to the upgrade?

I'm unable to reproduce this in a lucid chroot because do-release-upgrade -d is failing miserably for me before the upgrade even begins...

ifupdown 0.6.8ubuntu29.2 was installed on the system prior to upgrade.

This reproduces nicely with booting current lucid live system, switching apt to precise, and upgrading. I get exactly the same three conffile questions.

Just like 903137, this seems to be a case of files in /etc that were not conffiles at the time because of by-hand packaging. :(

This bug was fixed in the package ifupdown - 0.7~alpha5.1ubuntu6

---------------
ifupdown (0.7~alpha5.1ubuntu6) precise; urgency=low

  * debian/ifupdown.preinst: further conffile upgrade handling is needed
    for three files to get smooth upgrades from lucid (two of these were
    modified in a lucid SRU, one was modified in oneiric that previously
    didn't need special handling because the old and new checksums always
    matched). LP: #903131.
 -- Steve Langasek <email address hidden> Fri, 16 Dec 2011 23:16:47 -0800