[Bug 912544] Re: incorrect handling of config files when going from lucid to precise

[Rolf Leggewie]

*** This bug is a duplicate of bug 903137 ***
    https://bugs.launchpad.net/bugs/903137

Same thing for a few other packages which I will add here

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.

** This bug has been marked a duplicate of bug 903137
   lucid->precise upgrade - prompt to update unmodified conf files in /etc/update-motd.d: 00-header, 10-help-text, 99-footer

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/912544

Title:
  incorrect handling of config files when going from lucid to precise

Status in “update-motd” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  New

Bug description:
  Today I updated one of my computer from lucid to precise.  During the
  update I got a prompt for three config files belonging to update-motd
  package whether I wanted to accept upstream config files or keep my
  locally, modified copy.  I never change the local copy so I suspect
  there must be a packaging issue here.  Should be easy enough to
  reproduce for anyone out there going from lucid to precise.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-motd/+bug/912544/+subscriptions