https://bugs.openldap.org/show_bug.cgi?id=6104
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kangyang126(a)gmail.com
--- Comment #16 from Howard Chu <hyc(a)openldap.org> ---
*** Issue 10444 has been marked as a duplicate of this issue. ***
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6104
OndÅ™ej KuznÃk <ondra(a)mistotebe.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=10444
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10358
Issue ID: 10358
Summary: syncrepl can revert an entry's CSN
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: ondra(a)mistotebe.net
Target Milestone: ---
Created attachment 1080
--> https://bugs.openldap.org/attachment.cgi?id=1080&action=edit
Debug log of an instance of this happening
There is a sequence of operations which can force a MPR node to apply changes
out of order (essentially reverting an operation). Currently investigating
which part of the code that should have prevented this has let it slip.
A sample log showing how this happened is attached.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6916
OndÅ™ej KuznÃk <ondra(a)mistotebe.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=10440
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10434
Issue ID: 10434
Summary: mdb.c error: use of undeclared identifier 'fd' in
0.9.34?
Product: LMDB
Version: unspecified
Hardware: aarch64
OS: Mac OS
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: liblmdb
Assignee: bugs(a)openldap.org
Reporter: artkiver(a)gmail.com
Target Milestone: ---
Hi!
I may be jumping the gun a bit, but noticed via repology.org that some distros
had updated to LMDB 0.9.34 though I acknowledge the tagged commit reads:
" 03d56d53 · Prep for release (0.9.34) · 2 days ago "
From: https://gitlab.com/openldap/openldap/-/tags/LMDB_0.9.34
Regardless, I thought I would download the tarball and give it a whirl?
For reference I am using macOS, more specifically:
macOS 26.2 25C56 arm64
Command Line Tools 26.2.0.0.1.1764812424
Alas, I encountered the following errors when I attempted to build it:
% make
gcc -pthread -O2 -g -W -Wall -Wno-unused-parameter -Wbad-function-cast
-Wuninitialized -c mdb.c
mdb.c:2589:33: error: use of undeclared identifier 'fd'
2589 | else if (flags == MS_SYNC &&
MDB_FDATASYNC(env->me_fd))
| ^
mdb.c:132:32: note: expanded from macro 'MDB_FDATASYNC'
132 | # define MDB_FDATASYNC fcntl(fd, F_FULLFSYNC)
| ^
mdb.c:2599:8: error: use of undeclared identifier 'fd'
2599 | if (MDB_FDATASYNC(env->me_fd))
| ^
mdb.c:132:32: note: expanded from macro 'MDB_FDATASYNC'
132 | # define MDB_FDATASYNC fcntl(fd, F_FULLFSYNC)
| ^
2 errors generated.
make: *** [mdb.o] Error 1
A little bit more longwinded version (of basically the same error, though using
MacPorts as it is my intention to update the Portfile for that project once
it's functioning correctly) I've documented within MacPorts here, mentioning it
more for reference: https://trac.macports.org/ticket/73204#comment:3
My apologies in advance if I am being too eager and 0.9.34 isn't officially
released yet! Perhaps this is already known and planned to be fixed. I hope I'm
not wasting anyone's time or attention erroneously.
Thanks!
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10429
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10429
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Group|OpenLDAP-devs |
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10375
Issue ID: 10375
Summary: [patch] minor patch to const up oids array
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: caolanm(a)gmail.com
Target Milestone: ---
Created attachment 1084
--> https://bugs.openldap.org/attachment.cgi?id=1084&action=edit
minor patch to const up oids array
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10379
Issue ID: 10379
Summary: lastbind change prevents ppolicy response from
reaching accesslog
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: ondra(a)mistotebe.net
Target Milestone: ---
When "lastbind on" and ppolicy are configured together, the pwdLastSuccess
update triggers an accesslog entry (using op->o_time, op->o_tincr), then
ppolicy_bind_response issues its own modification and since the time was copied
in lastbind, an entry of the same name already exists. This means the ppolicy
change is lost (and e.g. won't replicate).
Note that slapo-lastbind (=the contrib overlay) probably has the same impact.
--
You are receiving this mail because:
You are on the CC list for the issue.