[Stephen Fox] > I rebuilt subversion without SASL after realizing SASL is an optional > dependency, and svn is working fine. I suppose a way to isolate it to > the ABI issue would be rebuilding the SASL libs, and building svn > against that? I don't entirely understand the implications of Bug > #665476.
I didn't spend any time trying to figure out the implications of #665476 either. It may or may not be related. In any case, Subversion is not failing for me, so I'd appreciate if someone could figure out how to reproduce the problem - is there some specific configuration of the Cyrus SASL library that triggers it, e.g.? The failure is in initializing libsasl2-2. Of course we could figure out how to init the library on demand, so that for cases like yours, it would never even travel that code path, but as this extraneous library init has not been a problem before, I'd rather find and fix the _real_ bug. As for just compiling without SASL support: SASL is indeed 'optional' in that not all servers will require it in order to authenticate. So that's a valid workaround for individual users. Not for the Debian build as a whole, though, as probably some servers _do_ require more advanced SASL authentication modes. Thanks, Peter -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
