[389-devel] Please review 48081: CI test - password :: regression tests

https://pagure.io/389-ds-base/issue/48081 https://pagure.io/389-ds-base/issue/raw/files/4a3379af00a39ca1d2ed42411d983f77c3c61d027e48b91152786773949518b9-0001-CI-tests-PasswordCheckSyntax-ou-givenname.patch ___ 389-devel mailing list -- 389-devel@lists.fed

[389-devel] Please review: [lib389] Issue 93 - Fix test cases in ctl_dbtasks_test.py

https://pagure.io/lib389/issue/93 https://pagure.io/lib389/issue/raw/files/1a03a98186d2d713fb306f28cf12837728454d20867aa618fe37392acf1c7ab9-0001-Issue-93-Fix-test-cases-in-ctl_dbtasks_test.py.patch ___ 389-devel mailing list -- 389-devel@lists.fedoraproj

[389-devel] Please review: Issue 49349 - global name 'imap' is not defined

https://pagure.io/389-ds-base/issue/49349 https://pagure.io/389-ds-base/issue/raw/files/afdefcb51b7da430e34ec8830a94c4c5c592edd7a1972adb3c1df8df27208b2d-0001-Issue-49349-global-name-imap-is-not-defined.patch signature.asc Description: PGP signature ___

[389-devel] Re: Strategy proposal for making DB dump in LDIF format from dbscan

On Fri, 2017-08-11 at 17:49 +0300, Ilias Stamatis wrote: > Hi everybody, > > Following Ludwig's and Mark's suggestions on how to perform a database dump > in LDIF format from dbscan, I have come up with a strategy. I'm talking > about ticket #47567: https://pagure.io/389-ds-base/issue/47567 > > I