I indeed went back to my original comment and restarted from there. I notcied that there is a link that is created when openssl is installed in debian bullseye /lib/ssl/openssl.cnf -> /etc/ssl/openssl.cnf. If I change the name of this link, mbsync (the one installed by debian) works again.
I'm not really sure what that means, though. The openssl.cnf is not really changed. there is just a new link to it. This seems very strange. Have you seen this before? Best regards On Sat, Mar 13, 2021 at 02:10:55PM +0100, Oswald Buddenhagen wrote: > On Fri, Mar 12, 2021 at 09:29:06AM +0100, Joel Granados wrote: > > The systems are actually quite different (I forgot to mention it). > > > well, that kind of defeats the configuration difference based approach. > > but that working second system seems to be a side track anyway. you started > out with this: > > > > The (very) freaky thing is that when I uninstall openssl the error > > > goes away. > > so let's concentrate on that. > i'm assuming that you didn't rebuild mbsync after (un-)installing openssl, > so mbsync is actually linked against libssl in both runs. > the instruction to look for differences using ldd and strace was aimed at > that. > > > _______________________________________________ > isync-devel mailing list > isync-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/isync-devel
signature.asc
Description: PGP signature
_______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
