incorrect handling of config files when going from lucid to precise
Bug #912544 reported by
Rolf Leggewie
This bug report is 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.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| update-motd (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| upstart (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
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.
| summary: |
- update-motd config files + incorrect handling of config files when going from lucid to precise |
Revision history for this message
| Rolf Leggewie (r0lf) wrote | #1 |
To post a comment you must log in.
Same thing for a few other packages which I will add here
cron for /etc/crontab
sudo for /etc/sudoers
upstart for /etc/init/
procps for /etc/init/
mountall for /etc/init/
hostname for /etc/init/
The latter had all been deleted on my system, not sure when or why that happened.