On Tue, 3 Mar 2026 22:37:41 +0300 Michael Tokarev <[email protected]> wrote:
Aha, this makes sense indeed - when you remove carefully added configuration changes aimed to keep your system running, things will break, unless you take care of them somehow. Maybe paying attention to `ansible-playbook -CD` output after upgrade is a good idea too.
Usual practice with apt/dpkg is giving a manual prompt if maintainer supplied config conflicts with user modified changes, letting the user inspect changes manually. I'm not sure if other packages edit config files through a postinst script.
It's always a trade-off, - as I said, you're the only one who faced this issue so far (it's been quite a number of upgrades since trixie is out). For the rest of users, such NEWS entry would be a useless noise. There's already quite some differences in postfix packaging in trixie (removal of the postfix@- unit etc). I wanted to keep it as compact as possible. Adding this change to NEWS didn't occur to me at all, though, because it seemed like something which I solved by editing config.
I think editing config files in postinst is not a standard way users expect to know about a config change, so I still think this would be useful. But I'll let you make the call as the maintainer.
I'm not sure if any other change has an high impact like this.
I thought this was pretty close as it was talking about the sasl path needing manual action, though why this was needed indeed changed.>> Also, it's a bad habit to hijack an old bug report which talks about >> a version which were many debian releases ago - it's unlikely to be >> the same issue.> > I have seen people recommending to check existing issues and comment on > them rather than opening new issues.Yeah. When it's the same issue. But doesn't matter anymore. That bug was not useful anyway, 17 years after its been filed.
OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
