>> I think that the current solution is not enough. The NEWS file sits >> there, but people do not usually read the NEWS files of all packages >> when they upgrade them. > >no, it doesn't have to just sit there. install apt-listchanges.
I did not know about it, thanks. I installed it now, and I see that its README speaks about changelog files, not NEWS files. If it really displays all new changelog entries, I will get hundreds of lines each time I upgrade, and this will not help with this issue (and would be generally useless, IMO). >there is no other clean way to do this (afaik). There are some packages which occasionally require user intervention during upgrade, by displaying a warning through debconf. For example, when parts of the libc are changed which require restarting daemons, a notice is displayed, and the user is required to confirm. Or if you try to uninstall the currently running kernel package, you are required to confirm. But i remember having occasionally seen others, maybe samba a long time ago when incompatible configuration changes where introduced. These are very rare occurrences: I argue that passing to the new storebackup version is one of these rare occurrences. I do not know what are the official guidelines in this case, though. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
