> Martin Fahrendorf <[EMAIL PROTECTED]> writes: > >> > do you know why postfix in cooker still uses sasl v1? >> > >> > anyway i just took the sources for sasl v1 and rebuild saslauthd for >> sasl1 (changing the socket path) and it works like charm with >> postfix. >> > >> > regards, >> > L. >> >> because ldap uses sasl v1 and postfix is bind to ldap and it is not >> good to use sasl v1 libs and sasl v2 libs in one application. > > Argh :(. Should I revert 2.0.12-2mdk change then? (pardon my lack > of knowledge in postfix field..) >
I think changing to sasl2 in postfix was a bit premature, since the dependencies are quite complex ... this is AFAIK how it works: Openldap, postfix, cyrus, should be compiled against the same libsasl. Openldap, sasl should be compiled against the same version of db4, and they Buildrequire each other. Openldap-2.1 requires db4-4.1 (I couldn't get it to build without bdb, and bdb requires db4-4.1) Any package that links directly to both sasl and openldap *must* be rebuilt, and rpm will also tell you that any package the requires libldap2 will need to be rebuilt (as dependencies will include libsasl7 instead of libsasl2). So, the way this should be done is: 1)get db4-4.1 into main 2)Rebuild sasl2 against db4-4.1 3)Rebuild openldap-2.1 against sasl2 4)Rebuild sasl2 against openldap-2.1 (I think there are some bits of sasl2 that require ldap) 5)Rebuild postfix against libldap2-2.1 and sasl2 6)Rebuild all other apps dependant on libldap2 and sasl (samba,samba3,kdebase,pam_ldap,nss_ldap,directory_administrator,gq, etc etc) Packages involved in this that are ready (those with packages please add to the list): http://ranger.dnsalias.com/mandrake/cooker/db4-4.1.25-1mdk.src.rpm http://ranger.dnsalias.com/mandrake/cooker/openldap.spec (2.1.19, Oden has a 2.1.20 package, but there is still some work to be done on ensuring an existing directory will work after upgrade). I have Oden's openldap-2.1.20, and will see if I can get some pre/post combo to migrate data correctly from 2.0.x to 2.1.x (or just figure out how to turn off schema checking). Maybe we should agree when we want to do the switch, and get all the packages ready? Can we aim for Friday 20 June? BTW, there is a problem with the naming of the sasl2 packages IMHO. The library name is libsasl2 (ie use -lsasl2 for LDFLAGS), the major version is 2, so the lib packages should be libsasl2_2 instead of libsasl2. This makes understanding which package (libsasl2 vs libsasl7) much easier ... Regards, Buchan
