lucid->precise upgrade - prompt to update unmodified conf files in /etc/update-motd.d: 00-header, 10-help-text, 99-footer

please attach the modified conffiles.

Note that this is probably a variation on bug #820233, but the checksums appear not to match the lucid version.

Original configuration files without .dpkg-dist extension.
Same installation than bug 903131

See also bug 903143 for another variation with /etc/init/failsafe-x.conf

And as for bug #903131, the checksums of these files exactly match the ones from the lucid package.

So something's seriously wrong here; either /var/lib/dpkg/status is corrupted, or dpkg itself is failing to detect checksum mismatches correctly on upgrade from lucid.

I can reproduce this by booting the current lucid 10.04.3 live system, switching apt to precise, and doing

  sudo apt-get install base-files

This is because in lucid, the files in /etc/update-motd.d/ are shipped by base-files, but are NOT marked as conffiles. They ARE conffiles in precise, but as their contents changed, you'll get a conffile prompt.

I see the same thing for a bunch of files on lucid2precise upgrade

cron for /etc/crontab
sudo for /etc/sudoers

upstart for /etc/init/upstart-udev-bridge.conf
procps for /etc/init/procps.conf
mountall for /etc/init/mountall.conf
hostname for /etc/init/hostname.conf

The latter had all been deleted on my system, not sure when or why that happened.

On Thu, Jan 05, 2012 at 11:04:07PM -0000, Rolf Leggewie wrote:
> I see the same thing for a bunch of files on lucid2precise upgrade

> cron for /etc/crontab
> sudo for /etc/sudoers

> upstart for /etc/init/upstart-udev-bridge.conf
> procps for /etc/init/procps.conf
> mountall for /etc/init/mountall.conf
> hostname for /etc/init/hostname.conf

> The latter had all been deleted on my system, not sure when or why that
> happened.

If you've deleted conffiles, that counts as a modification. It's not a bug
at all to be prompted in that case.

(I'm pretty sure /etc/init/mountall.conf didn't disappear on its own,
considering this is an essential part of the boot sequence in 10.04.)

On 06.01.2012 07:30, Steve Langasek wrote:
> If you've deleted conffiles, that counts as a modification.

Yes, of course. All I can say again right now is that I don't remember
deleting all those files. One possibility certainly is that they didn't
get restored properly from the backup.

FWIW, this is in a lucid vserver guest system that I had a LOT of
trouble with (actually, it never really ran ever since lucid was
released). The premature release of Upstart basically killed it. See
bug 701961 for the very unpleasant story.

just as apoint of information, this is causing upgrade test failure at:
https://jenkins.qa.ubuntu.com/view/Precise%20Upgrade%20Testing%20Dashboard/job/precise-upgrade-lts/PROFILE=lts-server-amd64,alderamin-upgrade=alderamin-upgrade/20/testReport/junit/lts-server-amd64/PostUpgradeTest/

This bug was fixed in the package base-files - 6.5ubuntu4

---------------
base-files (6.5ubuntu4) precise; urgency=low

  * debian/preinst: the non-conffile contents of /etc/update-motd.d had
    different md5sums in lucid, so include upgrade handling for those
    versions as well so we avoid spurious conffile prompts. LP: #903137.
 -- Steve Langasek <email address hidden> Wed, 25 Jan 2012 15:47:04 -0800

according to the QA team's weekly release report, this bug is still an issue because 99-footer is still generating a prompt.

This bug was fixed in the package base-files - 6.5ubuntu5

---------------
base-files (6.5ubuntu5) precise; urgency=low

  * debian/preinst: also handle 99-footer. Really closes LP: #903137.
 -- Steve Langasek <email address hidden> Fri, 27 Jan 2012 10:50:52 -0800