Re: Upgrading OpenLDAP 2.1.30 to 2.2.x
An additional question, does nss_ldap and pam_ldap works with openldap 2.2 ? -cs Robert Fitzpatrick wrote: Can portupgrade be used to upgrade OpenLDAP 2.1.x to 2.2.x by changing WITH_OPENLDAP_VER in my /etc/make.conf file to 22? Or do I have to deinstall the 21 package, and reinstall 22 and everything that depends on it? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading OpenLDAP 2.1.30 to 2.2.x
On Sun, May 16, 2004 at 12:35:04PM -0400, Robert Fitzpatrick wrote: > On Sun, 2004-05-16 at 11:24, Matthew Seaman wrote: > > That means that all of the applications linked against the LDAP shlibs > > have suddenly stopped working. To fix them, all you need do is > > reinstall -- the situation is analogous to the problem with > > 'libintl.so.N no found' thing that keeps coming up over and over on > > this list. > > > > Thanks for the detailed response. I have decided to upgrade a number of > packages that are related, like Berkeley DB to version 4.2. Also, I have > the openldap-sasl-* packages installed working with SASL 2.1.18 and > Heimdal Kerberos 0.6, but I don't think I need upgrade these two > packages, they seem to be at their latest versions, so I guess from what > you're saying, I just need to reinstall these packages. Also, Postfix > 2.0.16 that has LDAP support and I want to upgrade to 2.1.x. Is there > any recommended order for this scenario, perhaps upgrade Berkeley first, > then openldap-sasl-server-2.1.30 and client, then Postfix and reinstall > all other dependencies? Right -- the sasl versions of the OpenLDAP client+server can be updated exactly as I showed. Just make sure you edit pkgtools.conf's MAKE_ARGS array so that 'WITH_SASL=yes' gets supplied to the openldap22 ports as well as the openldap21 ports. The ordering requirements are basically like I said: openldap client first, then openldap server then everything else that depends on openldap client. If you just let portupgrade sort out the order of all the other dependencies it will (probably) work just fine. Since you can install several different versions of the BDB libraries simultaneously, just install the one you want right at the beginning. Hmmm.. of course, this shouldn't need to be said, but make sure you dump out the contents of your LDAP server in ldif format or otherwise make a backup of it in a format *which doesn't depend on the precise version of the BDB libs you have installed*. I think BDB's on-disk data formats are pretty much compatible across versions, but I'm not entirely certain. Obviously make sure slapd and slurpd aren't running when you start doing any of this. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgpLMRRxa0oGu.pgp Description: PGP signature
Re: Upgrading OpenLDAP 2.1.30 to 2.2.x
On Sun, 2004-05-16 at 11:24, Matthew Seaman wrote: > That means that all of the applications linked against the LDAP shlibs > have suddenly stopped working. To fix them, all you need do is > reinstall -- the situation is analogous to the problem with > 'libintl.so.N no found' thing that keeps coming up over and over on > this list. > Thanks for the detailed response. I have decided to upgrade a number of packages that are related, like Berkeley DB to version 4.2. Also, I have the openldap-sasl-* packages installed working with SASL 2.1.18 and Heimdal Kerberos 0.6, but I don't think I need upgrade these two packages, they seem to be at their latest versions, so I guess from what you're saying, I just need to reinstall these packages. Also, Postfix 2.0.16 that has LDAP support and I want to upgrade to 2.1.x. Is there any recommended order for this scenario, perhaps upgrade Berkeley first, then openldap-sasl-server-2.1.30 and client, then Postfix and reinstall all other dependencies? -- Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading OpenLDAP 2.1.30 to 2.2.x
On Sun, May 16, 2004 at 10:25:33AM -0400, Robert Fitzpatrick wrote: > Can portupgrade be used to upgrade OpenLDAP 2.1.x to 2.2.x by changing > WITH_OPENLDAP_VER in my /etc/make.conf file to 22? Or do I have to > deinstall the 21 package, and reinstall 22 and everything that depends > on it? You can use portupgrade do that, but it's slightly more complicated than what you propose. The way to upgrade to not just a different version of the same port, but a completely different port is to use the '-o' option to portupgrade. Thus in principal to upgrade from openldap21-client to openldap22-client you would run: # portupgrade -o net/openldap22-client -f net/openldap21-client which will replace the openldap21 client side with the openldap22 stuff, fixing up all the dependcy linkages in pkgdb as it does. (Nb. there aren't any sanity checks while doing this, so you can in theory persuade the ports system that 'quake2server' is an adequate substitue for 'gcc34' and other insanities. Be sure you understand what you are doing.) Now, the astute reader will have noticed the weasel words 'in principal' in that first paragraph. That's because things are somewhat more complicated than you might hope. The problem is that the openldapXX-client ports provide several shlibs, and the ABI version number has changed from one openldap version to the other: % grep .so. openldap21-server/pkg-plist.client lib/liblber.so.2 lib/libldap.so.2 lib/libldap_r.so.2 % grep .so. openldap22-server/pkg-plist.client lib/liblber.so.202 @comment lib/liblber-2.2.so.7 lib/libldap.so.202 @comment lib/libldap-2.2.so.7 lib/libldap_r.so.202 @comment lib/libldap_r-2.2.so.7 That means that all of the applications linked against the LDAP shlibs have suddenly stopped working. To fix them, all you need do is reinstall -- the situation is analogous to the problem with 'libintl.so.N no found' thing that keeps coming up over and over on this list. Before we get too happy about doing that, first we need to take care of the openldap server. But that's only if you've got one running on this particular system. It just takes the same sort of command line as for the client upgrade: # portupgrade -o net/openldap22-server -f net/openldap21-server You may have to install some new versions of the Berkely DB library to get that to work correctly. Now you can re-install all of the other programs that link against the openldap shlibs -- which is basically all dependencies of the openldap-client port. Note that openldap-server is also a dependency of openldap-client, but there's no point in re-installing that again, or anything else updated after the OpenLDAP client software: # portupgrade -rf net/openldap22-client -x '>=openldap*client' And that is really all there is to it. Oh -- although don't forget to put 'WANT_OPENLDAP_VER=22' into your /etc/make.conf or /usr/local/etc/pkgtools.conf once you're done. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgpKRPLpuEOBb.pgp Description: PGP signature
