[389-devel] Build failed in Jenkins: 389-ds-base #1208

See Changes: [William Brown] Ticket 49165 pw_verify did not handle external auth -- Started by an SCM change Building remotely on F25 (Fedora25 fedora Fedora fedora25) in workspace

[389-devel] Urgent: please review external bind fix

https://pagure.io/389-ds-base/issue/49165 https://pagure.io/389-ds-base/issue/raw/files/9c8c82e1a43e1adf854e0857e5b12ad6de4c7bdc1f1836c1c6ae064ed57ee37b-0001-Ticket-49165-pw_verify-did-not-handle-external-auth.patch -- Sincerely, William Brown Software Engineer Red Hat, Australia/Brisbane

[389-devel] Re: Questions related to lib389 issue #1 cn=config

On Mon, 2017-03-13 at 06:06 +, Ankit Yadav wrote: > Hello Everyone, > > I am currently working on one of the issue of lib389 issue #1 cn=config. > Below are some steps that I did to help myself and a question related to > these steps. > > lib389 issue #1 Description: > Once we have enough

[389-devel] please review: Issue 49062 - Reset replication agreement status after total init

https://pagure.io/389-ds-base/issue/49062 https://pagure.io/389-ds-base/issue/raw/files/c1454c1a2b025d750a3bf4722983a397dc140489ffae63a72f7bcceb86d82c8b-0001-Issue-49062-Reset-agmt-update-staus-and-total-init.patch ___ 389-devel mailing list --

[389-devel] Questions related to lib389 issue #1 cn=config

Hello Everyone, I am currently working on one of the issue of lib389 issue #1 cn=config. Below are some steps that I did to help myself and a question related to these steps. lib389 issue #1 Description: Once we have enough plugin and index code, we should be able to use dsconf to compare the