Hello Philippe,
Thanks for looking to contribute to the OpenLDAP project. Your submission
does not appear to have followed the submission guidelines for the project,
located at:
<http://www.openldap.org/devel/contributing.html>
In addition, I would note the following:
a) How does this submission differ from, or improve upon, the ldapc++ API
that is already shipped with OpenLDAP?
b) Your chosen license may cause your contribution to be rejected (See
contribution guidelines).
If you would still like your work to be included with the OpenLDAP project,
please review the contribution guidelines and follow up to the ITS with the
proper format, etc.
Regards,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Hi Soichi,
I was curious if you still encounter this issue using current OpenLDAP and
back-mdb. I would note the back-bdb/hdb backends are now deprecated. It
also occurred to me that the issue may have been related to lack of lock
resources, etc (which are generally set in DB_CONFIG).
Regards,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Just wanted to follow up and let you know that these issues have been
addressed for the 2.4.45 release. Thanks for the report!
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Hi Jan,
I've applied the SASL_NOCANON patch that was missed previously. Thanks for
the submission!
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
--On Saturday, February 11, 2017 9:46 PM +0000
sca+openldap(a)andreasschulze.de wrote:
> Full_Name: Andreas Schulze
> Version: RE24 testing call (2.4.45)
> OS: Linux
> URL: ftp://ftp.openldap.org/incoming/andreas-schulze-20170211-2.patch
> Submission from: (NULL) (2001:a60:f0b4:e502:80b6:610b:8fc2:abfe)
>
>
> there are 4 occurrence of "emtpy" which are supposed to be written as
> "empty"
Thanks for the report. In the future, please use git-format-patch, as
noted in the contributing guidelines:
<http://www.openldap.org/devel/contributing.html#patches>
Thanks!
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
After a brief review by Howard, there's a new patch available at
ftp://ftp.openldap.org/incoming/Ondrej-Kuznik-20170329c-Separate-Avlnode-=
and-TAvlnode-types.patch
The attached patch file is derived from OpenLDAP Software. All of the
modifications to OpenLDAP Software represented in the following
patch(es) were developed by Ond=C5=99ej Kuzn=C3=ADk <okuznik(a)symas.com>. =
I have
not assigned rights and/or interest in this work to any party.
The attached modifications to OpenLDAP Software are subject to the
following notice:
Copyright 2017, Ond=C5=99ej Kuzn=C3=ADk <okuznik(a)symas.com>, Symas Corpor=
ation
Redistribution and use in source and binary forms, with or without
modification, are permitted only as authorized by the OpenLDAP Public
License.=20
Full_Name: Ondrej Kuznik
Version: master
OS:
URL: ftp://ftp.openldap.org/incoming/Ondrej-Kuznik-20170329a-Separate-Avlnode-an…
Submission from: (NULL) (2a02:c7f:2247:ec00:a3e:8eff:fe52:dac5)
Since it is not safe to run any of the avl_* functions on a tavl node, it would
be useful to separate the types to prevent hard to diagnose issues caused by a
simple typo.
The provided patch against master separates the two types and adjusts the tavl
users.