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

[Rolf Leggewie]

Public bug reported:

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.

** Affects: update-motd (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: upstart (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: lucid2precise precise

** Summary changed:

- update-motd config files
+ incorrect handling of config files when going from lucid to precise

** Also affects: upstart (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-motd 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