You can subscribe to this list here.
2000 |
Jan
|
Feb
(34) |
Mar
(9) |
Apr
|
May
(2) |
Jun
(14) |
Jul
(67) |
Aug
(34) |
Sep
(5) |
Oct
(20) |
Nov
(22) |
Dec
(31) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(15) |
Feb
(16) |
Mar
(20) |
Apr
(13) |
May
(72) |
Jun
(42) |
Jul
(41) |
Aug
(11) |
Sep
(19) |
Oct
(67) |
Nov
(59) |
Dec
(57) |
2002 |
Jan
(74) |
Feb
(69) |
Mar
(34) |
Apr
(55) |
May
(47) |
Jun
(74) |
Jul
(116) |
Aug
(68) |
Sep
(25) |
Oct
(42) |
Nov
(28) |
Dec
(52) |
2003 |
Jan
(19) |
Feb
(18) |
Mar
(35) |
Apr
(49) |
May
(73) |
Jun
(39) |
Jul
(26) |
Aug
(59) |
Sep
(33) |
Oct
(56) |
Nov
(69) |
Dec
(137) |
2004 |
Jan
(276) |
Feb
(15) |
Mar
(18) |
Apr
(27) |
May
(25) |
Jun
(7) |
Jul
(13) |
Aug
(2) |
Sep
(2) |
Oct
(10) |
Nov
(27) |
Dec
(28) |
2005 |
Jan
(22) |
Feb
(25) |
Mar
(41) |
Apr
(17) |
May
(36) |
Jun
(13) |
Jul
(22) |
Aug
(12) |
Sep
(23) |
Oct
(6) |
Nov
(4) |
Dec
|
2006 |
Jan
(11) |
Feb
(3) |
Mar
(5) |
Apr
(22) |
May
(1) |
Jun
(10) |
Jul
(19) |
Aug
(7) |
Sep
(25) |
Oct
(23) |
Nov
(5) |
Dec
(27) |
2007 |
Jan
(25) |
Feb
(17) |
Mar
(44) |
Apr
(8) |
May
(33) |
Jun
(31) |
Jul
(42) |
Aug
(16) |
Sep
(12) |
Oct
(16) |
Nov
(23) |
Dec
(73) |
2008 |
Jan
(26) |
Feb
(6) |
Mar
(46) |
Apr
(17) |
May
(1) |
Jun
(44) |
Jul
(9) |
Aug
(34) |
Sep
(20) |
Oct
(2) |
Nov
(4) |
Dec
(16) |
2009 |
Jan
(14) |
Feb
(3) |
Mar
(45) |
Apr
(52) |
May
(34) |
Jun
(32) |
Jul
(24) |
Aug
(52) |
Sep
(22) |
Oct
(23) |
Nov
(19) |
Dec
(10) |
2010 |
Jan
(10) |
Feb
(13) |
Mar
(22) |
Apr
(9) |
May
(1) |
Jun
(1) |
Jul
(8) |
Aug
(9) |
Sep
(10) |
Oct
(1) |
Nov
(2) |
Dec
(3) |
2011 |
Jan
|
Feb
(18) |
Mar
(39) |
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Ganesan R <rga...@my...> - 2002-12-19 03:42:25
|
>>>>> "Michael" =3D=3D Michael Str=F6der <mi...@st...> writes: > Ganesan R wrote: >> add(dn, modlist) >> add_s(dn, modlist) >> Performs an LDAP add operation on dn. The dn argument is the >> distinguished >> name (DN) of the entry to add, and addlist is a list of attributes to = be ^^^^^^^ >> added. The modlist is similar the one passed to modify(), except that = the >> operation integer is omitted from the tuples in modlist. You might wa= nt to >> look into sub-module ldap.modlist for generating the modlist. Oops, that should be modlist.=20 Ganesan --=20 Ganesan R |
From: <mi...@st...> - 2002-12-18 16:01:24
|
Ganesan R wrote: > add(dn, modlist) > add_s(dn, modlist) > > Performs an LDAP add operation on dn. The dn argument is the distinguished > name (DN) of the entry to add, and addlist is a list of attributes to be > added. The modlist is similar the one passed to modify(), except that the > operation integer is omitted from the tuples in modlist. You might want to > look into sub-module ldap.modlist for generating the modlist. Ok. Ciao, Michael. |
From: Joe L. <jl...@op...> - 2002-12-18 05:16:43
|
Ok.. though I think having the c headers/docs around is a good thing for python-ldap developers, I have relaxed the dependencies and made a better distinction between dependencies and prereqs (the latter provides ordering, required for python site-packages) You'll find new python-ldap RPM/SRPMS for RedHat 7.3 and 8.0 on ftp.open-it.org Enjoy. On Tuesday, December 17, 2002, at 08:05 PM, Ganesan R wrote: >>>>>> "Joe" == Joe Little <jl...@op...> writes: > >> The maintainer (perhaps me) does read this list, but generally >> sleeps at the hours being discussed :) > > That's a problem we'll have to live with I guess :-). > >> I classify python-ldap as Group: Development/Library so I have it >> depend >> on openldap-devel and other -devel level packages. Among other >> things, it >> builds against dynamic libraries which I just saw are present in both >> the >> openldap base and openldap-devel packages. Either way, you can >> convince >> me that these should simply be build prereqs. > > I guess you need convincing only on the openldap-devel package :-). > Let me > try. For C libraries a "library" package (the openldap package in this > case) > and a "devel" package make sense. The devel package usually contains > the > needed headers and archive libraries in case applications need to link > statically. End users, i.e. users who use applications linked to > OpenLDAP do > not need to install -devel packages. > > For python (and java), the distinction does not exist. As a > developer, I > obviously will install openldap-devel for looking at the documentation > or > for developing C applications. However, the end user installing my > python-ldap application should not need to install openldap-devel. > > Thank you very much for packaging python-ldap rpm. I am a Debian > developer > but use Redhat at work. Your work saved me a lot of time :-). > > Ganesan > > -- > Ganesan R > > > > ------------------------------------------------------- > This sf.net email is sponsored by: > With Great Power, Comes Great Responsibility > Learn to use your power at OSDN's High Performance Computing Channel > http://hpc.devchannel.org/ > _______________________________________________ > Python-LDAP-dev mailing list > Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-ldap-dev |
From: Ganesan R <rga...@my...> - 2002-12-18 04:03:48
|
>>>>> "Joe" == Joe Little <jl...@op...> writes: > The maintainer (perhaps me) does read this list, but generally > sleeps at the hours being discussed :) That's a problem we'll have to live with I guess :-). > I classify python-ldap as Group: Development/Library so I have it depend > on openldap-devel and other -devel level packages. Among other things, it > builds against dynamic libraries which I just saw are present in both the > openldap base and openldap-devel packages. Either way, you can convince > me that these should simply be build prereqs. I guess you need convincing only on the openldap-devel package :-). Let me try. For C libraries a "library" package (the openldap package in this case) and a "devel" package make sense. The devel package usually contains the needed headers and archive libraries in case applications need to link statically. End users, i.e. users who use applications linked to OpenLDAP do not need to install -devel packages. For python (and java), the distinction does not exist. As a developer, I obviously will install openldap-devel for looking at the documentation or for developing C applications. However, the end user installing my python-ldap application should not need to install openldap-devel. Thank you very much for packaging python-ldap rpm. I am a Debian developer but use Redhat at work. Your work saved me a lot of time :-). Ganesan -- Ganesan R |
From: Joe L. <jl...@op...> - 2002-12-17 16:18:14
|
corrections in my english below (just woke up) On Tuesday, December 17, 2002, at 07:54 AM, Joe Little wrote: > The maintainer (perhaps me) does read this list, but generally sleeps=20= > at the hours being discussed :) > > I classify python-ldap as Group: Development/Library so I have it=20 > depend on openldap-devel and other -devel level packages. Among other=20= > things, it builds against dynamic libraries which I just saw are=20 > present in both the openldap base and openldap-devel packages. Either=20= > way, you can convince me that these should simply be build prereqs. I=20= > assume that you'd want to have all the .h files (and openldap drafts)=20= > around for reference when building ldap tools with python since at=20 > times the python documentation is not complete. You are right that=20 > python-devel is probably not needed anymore. > > On Tuesday, December 17, 2002, at 03:51 AM, Ganesan R wrote: > >>>>>>> "Michael" =3D=3D Michael Str=F6der <mi...@st...> = writes: >> >>> Ganesan R wrote: >>>> 2.0.0pre6. First, the binary rpm depends on python-devel and >>>> openldap-devel which are not needed. python-devel and = openldap-devel >>>> should be in BuildRequires, not in Requires or Prereq lines of the=20= >>>> spec >>>> file. >> >>> Note that you have to contact the package maintainer if you think >>> something's wrong with dependencies of a particular package. >> >> Noted :-). I assumed that the maintainer will be reading the list. I >> remember seeing his mails in the archive. >> >>>> Second, I need SSL support which doesn't seem to be enabled by >>>> default. Is it possible to turn on SSL support by default? >> >>> What do you mean with "by default"? >> >>> If you build python-ldap yourself you can tweak setup.cfg to reflect >>> your needs and configuration. Note that OpenLDAP also has to be = built >>> and installed with option --with-tls before. When shipping=20 >>> python-ldap >>> one cannot foresee your particular system configuration. >> >> I didn't mean python-ldap distribution to turn on SSL by default.=20 >> Redhat 7.3 >> OpenLDAP libraries ship with SSL option compiled in. So it makes=20 >> sense for >> the RPM to be built with the option turned on. Again, this is an=20 >> issue for >> the package maintainer. >> >> --=20 >> Ganesan R >> >> >> ------------------------------------------------------- >> This sf.net email is sponsored by: >> With Great Power, Comes Great Responsibility >> Learn to use your power at OSDN's High Performance Computing Channel >> http://hpc.devchannel.org/ >> _______________________________________________ >> Python-LDAP-dev mailing list >> Pyt...@li... >> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev > > > > ------------------------------------------------------- > This sf.net email is sponsored by: > With Great Power, Comes Great Responsibility Learn to use your power=20= > at OSDN's High Performance Computing Channel > http://hpc.devchannel.org/ > _______________________________________________ > Python-LDAP-dev mailing list > Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-ldap-dev |
From: Joe L. <jl...@op...> - 2002-12-17 15:54:13
|
The maintainer (perhaps me) does read this list, but generally sleeps=20 at the hours being discussed :) A classify python-ldap as Group: Development/Library so I have it=20 depend on openldap-devel and other -devel level packages. Among other=20 things, it builds against dynamic libraries would I just saw are=20 present in both the openldap base and openldap-devel packages. Either=20 way, you can convince me that these should simply be build prereqs. I=20 assume that you'd want to have all the .h files (and openldap drafts)=20 around for reference when building ldap tools with python since at=20 times the python documentation is not complete. You are right that=20 python-devel is probably not needed anymore. On Tuesday, December 17, 2002, at 03:51 AM, Ganesan R wrote: >>>>>> "Michael" =3D=3D Michael Str=F6der <mi...@st...> writes: > >> Ganesan R wrote: >>> 2.0.0pre6. First, the binary rpm depends on python-devel and >>> openldap-devel which are not needed. python-devel and openldap-devel >>> should be in BuildRequires, not in Requires or Prereq lines of the=20= >>> spec >>> file. > >> Note that you have to contact the package maintainer if you think >> something's wrong with dependencies of a particular package. > > Noted :-). I assumed that the maintainer will be reading the list. I > remember seeing his mails in the archive. > >>> Second, I need SSL support which doesn't seem to be enabled by >>> default. Is it possible to turn on SSL support by default? > >> What do you mean with "by default"? > >> If you build python-ldap yourself you can tweak setup.cfg to reflect >> your needs and configuration. Note that OpenLDAP also has to be built >> and installed with option --with-tls before. When shipping = python-ldap >> one cannot foresee your particular system configuration. > > I didn't mean python-ldap distribution to turn on SSL by default.=20 > Redhat 7.3 > OpenLDAP libraries ship with SSL option compiled in. So it makes sense=20= > for > the RPM to be built with the option turned on. Again, this is an issue=20= > for > the package maintainer. > > --=20 > Ganesan R > > > ------------------------------------------------------- > This sf.net email is sponsored by: > With Great Power, Comes Great Responsibility > Learn to use your power at OSDN's High Performance Computing Channel > http://hpc.devchannel.org/ > _______________________________________________ > Python-LDAP-dev mailing list > Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-ldap-dev |
From: <mi...@st...> - 2002-12-17 15:19:53
|
Steffen Ries wrote: > Michael Str=F6der <mi...@st...> writes: >=20 > >Anyone in favour of re-enabling method set_rebind_proc()? >=20 > Well, I am. >=20 > To be exact. I am interested in the functionality provided by > set_rebind_proc, not necessarily in its implementation. This translates to: No problem to remove the related code from LDAPObject= =2Ec. >>It has been disabled quite a while ago and I would like to remove >>the code from LDAPObject.c. Callbacks are pretty un-pythonic and the >>functionality can be better achieved in a Python wrapper class. >=20 > The last time I looked into this issue, I did not see an easy way how > to build a wrapper class which encapsulates the rebinding. Do you > have more ideas in this direction? I'm not sure when I'll find the > time to work on this, but I may be able to contribute an > implementation. Derive from ldap.ldapobject.LDAPObject and override all the relevant meth= ods. I have a bunch of ideas like this. But I have to make up my mind how to=20 implement these without stacking to many classes above each other. Maybe = some kind of mix-in classes would help. One could think of a registration dictionary for exception handlers. > I currently use an implementation that is backward compatible with > OpenLDAP 1.x. You're own your own with that. > I didn't find any python-ldap-2.x > package for windows. Contributions welcome. Ciao, Michael. |
From: <mi...@st...> - 2002-12-17 15:04:51
|
Rakesh Naidu wrote: > do you you if ldapmodule-1.8 confirms to teh RFC1823 standards.. Since python-ldap is a Python module it cannot be compliant to RFC 1823 which specifies a LDAP C API. It can only be inspired by it. Also note that all LDAP C APIs available shifted away from RFC 1823 since it does not cover newer features. Most remarkable for python-ldap 2.0.x is that OpenLDAP 2.x implements draft-ietf-ldapext-ldap-c-api. This draft is expired though. Ciao, Michael. |
From: Rakesh N. <rn...@ze...> - 2002-12-17 14:29:13
|
michael, do you you if ldapmodule-1.8 confirms to teh RFC1823 standards.. thanks rakesh ----- Original Message ----- From: "Michael Ströder" <mi...@st...> To: "Rakesh Naidu" <rn...@ze...> Cc: "python-ldap" <pyt...@li...> Sent: Tuesday, December 17, 2002 5:24 PM Subject: Re: error installing ldapmodule1.8 > Rakesh Naidu wrote: > > > > please confirm if upgradation to OpenLDAP > > 2.0.13 is a must taking in to consideration the above conf. > > I'd even recommend that you SHOULD use the latest and greatest of the > OpenLDAP libs since the OpenLDAP project applied numerous bug fixes to the > client libs since 2.0.13. > > Ciao, Michael. > > |
From: Steffen R. <ste...@sy...> - 2002-12-17 13:59:42
|
Michael Str=F6der <mi...@st...> writes: > HI! >=20 > Anyone in favour of re-enabling method set_rebind_proc()? Well, I am. To be exact. I am interested in the functionality provided by set_rebind_proc, not necessarily in its implementation. > It has been disabled quite a while ago and I would like to remove > the code from LDAPObject.c. Callbacks are pretty un-pythonic and the > functionality can be better achieved in a Python wrapper class. The last time I looked into this issue, I did not see an easy way how to build a wrapper class which encapsulates the rebinding. Do you have more ideas in this direction? I'm not sure when I'll find the time to work on this, but I may be able to contribute an implementation. > If someone really needs it he/she should volunteer maintaining it > according to changes which might have been made in recent versions of > OpenLDAP 2.x. I currently use an implementation that is backward compatible with OpenLDAP 1.x. The main reason is my application works both on Unix and WinNT. Since I don't actively support WinNT (esp. I don't have the infrastructure to build C-Code on NT), I depend on pre-built packages. The last time I checked, I didn't find any python-ldap-2.x package for windows. /steffen --=20 ste...@sy... <> Gravity is a myth -- the Earth sucks! |
From: Jens V. <je...@zo...> - 2002-12-17 13:29:55
|
well thank you michael ;) On Tuesday, Dec 17, 2002, at 06:22 US/Eastern, Michael Str=F6der wrote: > Rakesh Naidu wrote: >> michael...can u throw some light on this error..... >> 2002-12-17T10:50:45 ERROR(200) Zope Could not import=20 >> Products.LDAPUserFolder >> Traceback (innermost last): >> [..] >> ImportError: No module named ldap > > This was recently discussed here. I've attached a posting by Jens=20 > before he has to repeat it. > > Furthermore you can search the mailing list archive for 'Zope'. > > Ciao, Michael > > -------- Original Message -------- > Subject: Re: Problems importing ldap in Zope > Date: Fri, 29 Nov 2002 20:12:57 -0500 > From: Jens Vagelpohl <je...@zo...> > To: Jorge Loureiro Dias <lou...@dt...> > CC: pyt...@li... > > this problem has nothing to do with zope. the ldap module zope is > trying to import is messed up. the one zope is trying to import is = most > likely not the same one that gets imported if you run python itself > from the command line. > > you need to locate the exact python binary zope uses and rebuild the > python-ldap module with that binary. > > jens > > > > ------------------------------------------------------- > This sf.net email is sponsored by: > With Great Power, Comes Great Responsibility Learn to use your power=20= > at OSDN's High Performance Computing Channel > http://hpc.devchannel.org/ > _______________________________________________ > Python-LDAP-dev mailing list > Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-ldap-dev |
From: Ganesan R <rga...@my...> - 2002-12-17 11:59:20
|
Hi, The documentation for the LDAP add operation reads (See http://python-ldap.sourceforge.net/doc/python-ldap/node11.html) ------ add(dn, modlist) add_s(dn, modlist) This function is similar to modify(), except that the operation integer is omitted from the tuples in modlist. You might want to like into sub-module ldap.modlist for generating modlist. ------ Apart from the typo there (like into sub-module instead of look into sub-module), the description seems to imply that add is a short cut for modify with LDAP_MOD_ADD. I'd change that to add(dn, modlist) add_s(dn, modlist) Performs an LDAP add operation on dn. The dn argument is the distinguished name (DN) of the entry to add, and addlist is a list of attributes to be added. The modlist is similar the one passed to modify(), except that the operation integer is omitted from the tuples in modlist. You might want to look into sub-module ldap.modlist for generating the modlist. Ganesan -- Ganesan R |
From: <mi...@st...> - 2002-12-17 11:54:31
|
Rakesh Naidu wrote: > > please confirm if upgradation to OpenLDAP > 2.0.13 is a must taking in to consideration the above conf. I'd even recommend that you SHOULD use the latest and greatest of the OpenLDAP libs since the OpenLDAP project applied numerous bug fixes to the client libs since 2.0.13. Ciao, Michael. |
From: Ganesan R <rga...@my...> - 2002-12-17 11:49:42
|
>>>>> "Michael" =3D=3D Michael Str=F6der <mi...@st...> writes: > Ganesan R wrote: >> 2.0.0pre6. First, the binary rpm depends on python-devel and >> openldap-devel which are not needed. python-devel and openldap-devel >> should be in BuildRequires, not in Requires or Prereq lines of the spe= c >> file.=20 > Note that you have to contact the package maintainer if you think > something's wrong with dependencies of a particular package. Noted :-). I assumed that the maintainer will be reading the list. I remember seeing his mails in the archive. >> Second, I need SSL support which doesn't seem to be enabled by >> default. Is it possible to turn on SSL support by default? > What do you mean with "by default"? > If you build python-ldap yourself you can tweak setup.cfg to reflect > your needs and configuration. Note that OpenLDAP also has to be built > and installed with option --with-tls before. When shipping python-ldap > one cannot foresee your particular system configuration. I didn't mean python-ldap distribution to turn on SSL by default. Redhat = 7.3 OpenLDAP libraries ship with SSL option compiled in. So it makes sense fo= r the RPM to be built with the option turned on. Again, this is an issue fo= r the package maintainer. --=20 Ganesan R |
From: <mi...@st...> - 2002-12-17 11:35:55
|
Ganesan R wrote: > > 2.0.0pre6. First, the binary rpm depends on python-devel and openldap-devel > which are not needed. python-devel and openldap-devel should be in > BuildRequires, not in Requires or Prereq lines of the spec file. Note that you have to contact the package maintainer if you think something's wrong with dependencies of a particular package. > Second, I need SSL support which doesn't seem to be enabled by default. Is > it possible to turn on SSL support by default? What do you mean with "by default"? If you build python-ldap yourself you can tweak setup.cfg to reflect your needs and configuration. Note that OpenLDAP also has to be built and installed with option --with-tls before. When shipping python-ldap one cannot foresee your particular system configuration. Ciao, Michael. |
From: <mi...@st...> - 2002-12-17 11:23:09
|
Rakesh Naidu wrote: > michael...can u throw some light on this error..... > > 2002-12-17T10:50:45 ERROR(200) Zope Could not import Products.LDAPUserFolder > Traceback (innermost last): > [..] > ImportError: No module named ldap This was recently discussed here. I've attached a posting by Jens before he has to repeat it. Furthermore you can search the mailing list archive for 'Zope'. Ciao, Michael -------- Original Message -------- Subject: Re: Problems importing ldap in Zope Date: Fri, 29 Nov 2002 20:12:57 -0500 From: Jens Vagelpohl <je...@zo...> To: Jorge Loureiro Dias <lou...@dt...> CC: pyt...@li... this problem has nothing to do with zope. the ldap module zope is trying to import is messed up. the one zope is trying to import is most likely not the same one that gets imported if you run python itself from the command line. you need to locate the exact python binary zope uses and rebuild the python-ldap module with that binary. jens |
From: Ganesan R <rga...@my...> - 2002-12-17 11:19:28
|
Hi, 2.0.0pre6. First, the binary rpm depends on python-devel and openldap-devel which are not needed. python-devel and openldap-devel should be in BuildRequires, not in Requires or Prereq lines of the spec file. Second, I need SSL support which doesn't seem to be enabled by default. Is it possible to turn on SSL support by default? Thanks. Ganesan -- Ganesan R |
From: Rakesh N. <rn...@ze...> - 2002-12-17 11:11:17
|
michael...can u throw some light on this error..... 2002-12-17T10:50:45 ERROR(200) Zope Could not import Products.LDAPUserFolder Traceback (innermost last): File /home/zeo/Zope-2.5.1-linux2-x86/lib/python/OFS/Application.py, line 531, in import_product File /home/zeo/zope/lib/python/Products/LDAPUserFolder/__init__.py, line 13, in ? File /home/zeo/zope/lib/python/Products/LDAPUserFolder/LDAPUserFolder.py, line 34, in ? File /home/zeo/zope/lib/python/Products/LDAPUserFolder/LDAPUser.py, line 19, in ? (Object: aq_inner) File /home/zeo/zope/lib/python/Products/LDAPUserFolder/utils.py, line 32, in ? ImportError: No module named ldap as of now python-ldap 2.0.0pre05 / OpenLDAP 2.0.12 /on SuSe Linux (on client machine)..... your suggestions are welcome.....please confirm if upgradation to OpenLDAP 2.0.13 is a must taking in to consideration the above conf. thanks, Rakesh Naidu. ----- Original Message ----- From: "Michael Ströder" <mi...@st...> To: "Ganesan R" <rga...@my...> Cc: "python-ldap" <pyt...@li...> Sent: Tuesday, December 17, 2002 4:02 PM Subject: Re: error installing ldapmodule1.8 Ganesan R wrote: >>>>>>"Michael" == Michael Ströder <mi...@st...> writes: > >>Please go for python-ldap 2.0.0pre06 compiled against OpenLDAP 2.x >>libs. 1.8 is pretty ancient. > > Is OpenLDAP 2.0 supported? Not only supported. Since python-ldap 2.x OpenLDAP 2.x is REQUIRED. > I faced some problems compiling python-ldap with > it. Which version of python-ldap? Which version of OpenLDAP? AFAIK you need at least OpenLDAP 2.0.13 when building with TLS support. Ciao, Michael. ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ Python-LDAP-dev mailing list Pyt...@li... https://lists.sourceforge.net/lists/listinfo/python-ldap-dev |
From: Ganesan R <rga...@my...> - 2002-12-17 11:04:11
|
>>>>> "Michael" =3D=3D Michael Str=F6der <mi...@st...> writes: > Ganesan R wrote: >> Is OpenLDAP 2.0 supported? > Not only supported. Since python-ldap 2.x OpenLDAP 2.x is REQUIRED. >> I faced some problems compiling python-ldap with >> it. > Which version of python-ldap? pre6. > Which version of OpenLDAP? AFAIK you need at least OpenLDAP 2.0.13 > when building with TLS support. OpenLDAP 2.0.25. The verified that the problem is still present with with the "full-featured" build. I checked the mailing list and found the reaso= n for my problem - "full-featured" build uses ldap_r which appears to be broken with OpenLDAP 2.0.* versions (at least till 2.0.25).=20 By the way, I had a funny experience dealing with this problem. The error message said cannot find symbol ldap_first_reference. For some reason, I assumed that python is complaining about not able to resolve the first reference in the LDAP library and went about debugging with ldd :-) :-). Finally, I realized that it's the name of an actual symbol! By the way, I am extremely pleased with python-ldap. I have always been reluctant to code to the C API and even when I started using python, I us= ed initially the external tools like ldapsearch and ldapmodify. Then I found python-ldap. It has really made LDAP programming a breeze. Thanks a lot! Ganesan --=20 Ganesan R |
From: <mi...@st...> - 2002-12-17 10:32:33
|
Ganesan R wrote: >>>>>>"Michael" =3D=3D Michael Str=F6der <mi...@st...> writes: >=20 >>Please go for python-ldap 2.0.0pre06 compiled against OpenLDAP 2.x >>libs. 1.8 is pretty ancient. >=20 > Is OpenLDAP 2.0 supported? Not only supported. Since python-ldap 2.x OpenLDAP 2.x is REQUIRED. > I faced some problems compiling python-ldap with > it. Which version of python-ldap? Which version of OpenLDAP? AFAIK you need at least OpenLDAP 2.0.13 when=20 building with TLS support. Ciao, Michael. |
From: <mi...@st...> - 2002-12-17 10:29:23
|
Rakesh Naidu wrote: > > do you think python-ldap 2.0.0pre05...should work fine with openldap 2.0.12 > > and also will python-ldap 2.0.0pre06 work fine with openldap 2.0.12 > > coz as of now i have asked my client's sys admin to instal python-ldap > 2.0.0pre05 I'd strongly recommend 2.0.0pre06 with very recent OpenLDAP 2.0.x or 2.1.x libs. Try to convince your sys admin. Or try to compile it in your home directory and build an RPM with 'python setup bist_rpm'. Ciao, Michael. |
From: Rakesh N. <rn...@ze...> - 2002-12-17 10:15:30
|
thanks for the reply,michael, do you think python-ldap 2.0.0pre05...should work fine with openldap 2.0.12 and also will python-ldap 2.0.0pre06 work fine with openldap 2.0.12 coz as of now i have asked my client's sys admin to instal python-ldap 2.0.0pre05 with regards, Rakesh Naidu ----- Original Message ----- From: "Michael Ströder" <mi...@st...> To: "Rakesh Naidu" <rn...@ze...> Cc: "python-ldap" <pyt...@li...> Sent: Tuesday, December 17, 2002 2:52 PM Subject: Re: error installing ldapmodule1.8 > Rakesh Naidu wrote: > > I hear that ldapmodule-1.8.tar.gz is not installable on suse linux 7.x > > Please go for python-ldap 2.0.0pre06 compiled against OpenLDAP 2.x libs. 1.8 > is pretty ancient. > > Ciao, Michael. > > > > ------------------------------------------------------- > This sf.net email is sponsored by: > With Great Power, Comes Great Responsibility > Learn to use your power at OSDN's High Performance Computing Channel > http://hpc.devchannel.org/ > _______________________________________________ > Python-LDAP-dev mailing list > Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-ldap-dev > |
From: Ganesan R <rga...@my...> - 2002-12-17 10:08:32
|
>>>>> "Michael" =3D=3D Michael Str=F6der <mi...@st...> writes: > Rakesh Naidu wrote: >> I hear that ldapmodule-1.8.tar.gz is not installable on suse linux 7.x > Please go for python-ldap 2.0.0pre06 compiled against OpenLDAP 2.x > libs. 1.8 is pretty ancient. Is OpenLDAP 2.0 supported? I faced some problems compiling python-ldap wi= th it. The problems went away when I used OpenLDAP 2.1. This may be due to = a bug in the local environment, I was playing around with both OpenLDAP 2.0 and 2.1. Ganesan --=20 Ganesan R |
From: <mi...@st...> - 2002-12-17 09:23:05
|
Rakesh Naidu wrote: > I hear that ldapmodule-1.8.tar.gz is not installable on suse linux 7.x Please go for python-ldap 2.0.0pre06 compiled against OpenLDAP 2.x libs. 1.8 is pretty ancient. Ciao, Michael. |
From: Rakesh N. <rn...@ze...> - 2002-12-17 09:15:40
|
hello all, I hear that ldapmodule-1.8.tar.gz is not installable on suse linux 7.x since it uses an API which was not standardised(it references a member mod_next in the LDAPMod structure which was present in UM LDAP and = early OpenLDAP) can any one confirm this or comment on this.... i have been trying to get the sys admin of my customer's ...to install = this.....and i get this reply that it is not compatible... Rakesh Naidu. _o _\<_ __(_)/(_) life's a journey not a destination.... |