On 10/21/23 12:24, Andreas Metzler wrote:
However I still do not get it.
* Is there a useful scenario where someone would set save_seen=none in
the apt stanza?
*shrug* I don't know. That design decision was made long before my time.
I don't see any good reason to change it given that if anybody /is/
taking advantage of it for whatever reason, then doing so would cause
them trouble.
* Would I be reshown changelog entries when I had already seen them
before but aborted the upgrade if save_seen=/var/lib/apt/listchanges
was set?
In version 3.x of apt-listchanges, if you aborted the update and then
ran it again you would be shown the changes again. In the current 4.x
version of apt-listchanges, you will /not/ be shown the changes again if
you abort and rerun an update.
Your question has prompted me to think further about this and now I'm
not convinced the change in behavior in 4.x is correct. What do you
think? Do you think the program should only "commit" the changes to the
database and not display them again if the user goes through with the
update?
jik
