Re: symbolic links problem due to do-release-upgrade (postfix 3.6.4)

2022-11-23 Thread Michael Tokarev
Hello Victor! Just by a chance I noticed this email and wanted to add a comment. 04.10.2022 02:52, Viktor Dukhovni wrote: .. Perhaps you previously had a "backports" package that uses a non-default release label, and it persisted across the upgrade... You may need to also look at the configs (I

Re: symbolic links problem due to do-release-upgrade (postfix 3.6.4)

2022-10-03 Thread Viktor Dukhovni
On Mon, Oct 03, 2022 at 08:43:18PM +, Martin wrote: > yes, I'm afraid that's true, these are the contents of that old > directory (I renamed it and put a symbolic link to the sbin directory carrying > the current executables): > root@jerakeen:/usr/libexec/postfix/sbin.OLD# find . -type f -prin

Re: symbolic links problem due to do-release-upgrade (postfix 3.6.4) - was: manually build 3.7.2 denies SASL although included in make command

2022-10-03 Thread Wietse Venema
Martin: > HI Wietse, > > yes, I'm afraid that's true, these are the contents of that old > directory All those binaries have mail_version=3.4.13, therefore none will work Postfix 3.6 libraries. > I assume there has been a kind of new configuration between old postfix > version and the 3.6.4 one.

Re: symbolic links problem due to do-release-upgrade (postfix 3.6.4) - was: manually build 3.7.2 denies SASL although included in make command

2022-10-03 Thread Martin
HI Wietse, yes, I'm afraid that's true, these are the contents of that old directory (I renamed it and put a symbolic link to the sbin directory carrying the current executables): root@jerakeen:/usr/libexec/postfix/sbin.OLD# find . -type f -print | while read file; do echo -n "$file -> "; strin