On Mon, Mar 22, 2021 at 11:19:24PM +0100, Joel Granados wrote:
On Thu, Mar 18, 2021 at 11:03:00PM +0100, Oswald Buddenhagen wrote:
On Thu, Mar 18, 2021 at 09:09:53PM +0100, Joel Granados wrote:
> 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.
>
fwiw, it's /usr/lib/ssl/openssl.cnf.
nope, on my system it is /lib/ssl/openssl.cnf.
given that on your system /lib is a symlink to /usr/lib, you need to
reassess your observations.
and I cannot find what package installed it:
the explanation is in /var/lib/dpkg/info/openssl.postinst .
- your openssl.cnf in /etc is somehow causing that weird error, which
deserves investigation
I don't think so as both the /usr/lib/ssl/openssl.cnf and /etc/ssl/openssl.cnf
are unchanged when mbsync actually works. Note that
/usr/lib/ssl/openssl.cnf is a link to /etc/ssl/openssl.cnf
but by extension the one in /etc should be actually read when the
symlink is present.
- the debian packaging deserves a bug report - it's insane that installing
an opional package with command line tools changes the behavior of the
underlying library package.
Not sure I follow here. what optional package are you talking about?
openssl. installing it changes the behavior of libssl1.1, which is
further up the dependency chain. that's unacceptable.
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
