9:53 a.m.
https://bugs.openldap.org/show_bug.cgi?id=9846
Issue ID: 9846
Summary: Provide ppm v2.2
Product: OpenLDAP
Version: 2.6.2
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: contrib
Assignee: bugs(a)openldap.org
Reporter: david.coutadeur(a)gmail.com
Target Milestone: ---
Provide the new release of ppm: v2.2:
- implement a maximum number of characters for each class #18
- upgrade documentation for new olcPPolicyCheckModule in OpenLDAP 2.6 #30
- Make one unique code of development for 2.5 and 2.6 OpenLDAP versions #35
- fix segmentation fault in ppm_test #36
- various minor fixes and optimizations
See: https://github.com/ltb-project/ppm/milestone/5
I am going to propose a MR soon.
--
You are receiving this mail because:
You are on the CC list for the issue.
8:47 a.m.
New subject: [Issue 9846] Provide ppm v2.2
https://bugs.openldap.org/show_bug.cgi?id=9846
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
head:
• c34d419f
by David Coutadeur at 2022-05-17T11:02:14+02:00
provide ppm v2.2 (#9846)
RE26:
• 225940d9
by David Coutadeur at 2022-05-19T15:33:18+00:00
provide ppm v2.2 (#9846)
--
You are receiving this mail because:
You are on the CC list for the issue.
8:44 a.m.
New subject: [Issue 9846] Provide ppm v2.2
https://bugs.openldap.org/show_bug.cgi?id=9846
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|2.5.13 |2.6.3
--
You are receiving this mail because:
You are on the CC list for the issue.
8:33 a.m.
New subject: [Issue 9846] Provide ppm v2.2
https://bugs.openldap.org/show_bug.cgi?id=9846
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs_review |
--
You are receiving this mail because:
You are on the CC list for the issue.
8:32 a.m.
New subject: [Issue 9846] Provide ppm v2.2
https://bugs.openldap.org/show_bug.cgi?id=9846
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |2.5.13
--
You are receiving this mail because:
You are on the CC list for the issue.
1:14 p.m.
New subject: [Issue 9846] Provide ppm v2.2
https://bugs.openldap.org/show_bug.cgi?id=9846
--- Comment #5 from David Coutadeur <david.coutadeur(a)gmail.com> ---
The ppm source code is being managed in a github repository where it is much
easier to maintain one unique branch for the development. Especially because
the ppm code is not so different between 2.5 and 2.6 versions.
Also when I submit a new release to you, it makes more work at your side for
merging this into the two branches 2.5 and 2.6.
So this can be an opportunity to have a simpler process.
For 2.6 branch of openldap, you have no change in the building.
And now you can also merge the same ppm code in 2.5 branch, adding
OLDAP_VERSION=25
Is there a problem with this integration approach ?
--
You are receiving this mail because:
You are on the CC list for the issue.
11:26 a.m.
New subject: [Issue 9846] Provide ppm v2.2
https://bugs.openldap.org/show_bug.cgi?id=9846
--- Comment #4 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
(In reply to Quanah Gibson-Mount from comment #3)
(In reply to David Coutadeur from comment #2)
> Note that the new 2.2 release is also compatible with OpenLDAP 2.5 without
> any modification.
>
> A new variable "SLAPD_VERSION" is available to choose the appropriate
> version at compilation. (2.6 being the default)
Why would such a variable be necessary?
In other words, it is shipped in the contrib/ directory for a given release
stream. There should be no such variable in the PPM source.
--
You are receiving this mail because:
You are on the CC list for the issue.
11:25 a.m.
New subject: [Issue 9846] Provide ppm v2.2
https://bugs.openldap.org/show_bug.cgi?id=9846
--- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
(In reply to David Coutadeur from comment #2)
Note that the new 2.2 release is also compatible with OpenLDAP 2.5
without
any modification.
A new variable "SLAPD_VERSION" is available to choose the appropriate
version at compilation. (2.6 being the default)
Why would such a variable be necessary?
--
You are receiving this mail because:
You are on the CC list for the issue.
10:32 a.m.
New subject: [Issue 9846] Provide ppm v2.2
https://bugs.openldap.org/show_bug.cgi?id=9846
--- Comment #2 from David Coutadeur <david.coutadeur(a)gmail.com> ---
Note that the new 2.2 release is also compatible with OpenLDAP 2.5 without any
modification.
A new variable "SLAPD_VERSION" is available to choose the appropriate version
at compilation. (2.6 being the default)
--
You are receiving this mail because:
You are on the CC list for the issue.
10:19 a.m.
New subject: [Issue 9846] Provide ppm v2.2
https://bugs.openldap.org/show_bug.cgi?id=9846
--- Comment #1 from David Coutadeur <david.coutadeur(a)gmail.com> ---
Proposition done in
https://git.openldap.org/openldap/openldap/-/merge_requests/525
--
You are receiving this mail because:
You are on the CC list for the issue.
47
days inactive
55
days old
9 comments
1 participants
participants (1)
-
openldap-its＠openldap.org