An upgrade of readahead should not offer to "upgrade" /etc/readahead/boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
readahead-list (Ubuntu) |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
On upgrading readahead, I got the standard debconf prompt about a changed configuration file:
Configuration file `/etc/readahead
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : background this process to examine the situation
The default action is to keep your current version.
*** boot (Y/I/N/O/D/Z) [default=N] ?
I don't think this should even be mentioned at all. I can not see any reason why a user would want to replace the file generated explicitly for their system. Users who have not used the "profile" boot option will not see this question, and those who have have no use for it.
Changed in readahead: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
Agree to some extent.
An upgrade should replace its own lists, but not overwrite custom ones.