https://pagure.io/389-ds-base/pull-request/49841
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
https://pagure.io/389-ds-base/pull-request/49839
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
https://pagure.io/389-ds-base/pull-request/49836
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
https://pagure.io/389-ds-base/pull-request/49831
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
https://pagure.io/389-ds-base/pull-request/49825
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
https://pagure.io/389-ds-base/pull-request/49823
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
https://pagure.io/389-ds-base/pull-request/49809
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
https://pagure.io/389-ds-base/pull-request/49819
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
https://pagure.io/389-ds-base/pull-request/49812
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
https://pagure.io/389-ds-base/pull-request/49809
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
Also added cli autocomplete...
https://pagure.io/389-ds-base/pull-request/49805
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
Forwarded Message
Subject: [389-devel] please review: Ticket 49751 - passwordMustChange
attribute is not honored by a RO consumer if using "Chain on Update"
Date: Tue, 5 Jun 2018 13:34:09 -0400
From: Mark Reynolds
Reply-To: 389 Directory server developer
Forwarded Message
Subject: [389-devel] please review: Ticket 49734 - Fix various issues
with Disk Monitoring
Date: Wed, 6 Jun 2018 14:57:42 -0400
From: Mark Reynolds
Reply-To: 389 Directory server developer discussion.
<389-devel@lists.fedoraproject.
https://pagure.io/389-ds-base/pull-request/49785
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
https://pagure.io/389-ds-base/pull-request/49779
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://pagure.io/389-ds-base/pull-request/49776
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
https://pagure.io/389-ds-base/pull-request/49774
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
https://pagure.io/389-ds-base/pull-request/49773
___
389-devel mailing list -- 389-de...@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
https://pagure.io/389-ds-base/pull-request/49770
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
https://pagure.io/389-ds-base/issue/49745
https://pagure.io/389-ds-base/pull-request/49764
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://pagure.io/389-ds-base/issue/49702
https://pagure.io/389-ds-base/pull-request/49763
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://pagure.io/389-ds-base/issue/49754
https://pagure.io/389-ds-base/pull-request/49760
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://pagure.io/389-ds-base/issue/49734
https://pagure.io/389-ds-base/pull-request/49759
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://pagure.io/389-ds-base/pull-request/49733
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
https://pagure.io/389-ds-base/pull-request/49699
On 05/17/2018 10:34 PM, Mark Reynolds wrote:
> https://pagure.io/389-ds-base/issue/49683
>
> https://pagure.io/389-ds-base/pull-request/49699
> ___
> 389-devel mailing li
https://pagure.io/389-ds-base/pull-request/49729
On 05/22/2018 12:51 PM, Mark Reynolds wrote:
> https://pagure.io/389-ds-base/issue/49675
> ___
> 389-devel mailing list -- 389-devel@lists.fedoraproject.org
> To unsubscribe send an email to
https://pagure.io/389-ds-base/issue/49704
https://pagure.io/389-ds-base/pull-request/49711
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://pagure.io/389-ds-base/issue/49706
https://pagure.io/389-ds-base/pull-request/49707
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://pagure.io/389-ds-base/issue/49675
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List
https://pagure.io/389-ds-base/issue/49576
https://pagure.io/389-ds-base/pull-request/49700
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://pagure.io/389-ds-base/issue/49683
https://pagure.io/389-ds-base/pull-request/49699
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://pagure.io/389-ds-base/issue/49665
https://pagure.io/389-ds-base/pull-request/49695
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
https://pagure.io/389-ds-base/issue/49689
https://pagure.io/389-ds-base/pull-request/49694
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
https://pagure.io/389-ds-base/issue/49669
https://pagure.io/389-ds-base/pull-request/49688
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
https://pagure.io/389-ds-base/issue/49675
https://pagure.io/389-ds-base/pull-request/49676
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
https://pagure.io/389-ds-base/issue/49671
https://pagure.io/389-ds-base/pull-request/49672
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
https://pagure.io/389-ds-base/issue/49665
PBKDF2
https://pagure.io/389-ds-base/issue/raw/files/6b9e353bdac563698d9fa3294353c6fbc6173cd93e9291f9b7ca1a4d96015487-0001-Ticket-49665-Upgrade-script-doesn-t-enable-PBKDF2-pa.patch
New CRYPT schemes
https://pagure.io/389-ds-base/issue/49649
https://pagure.io/389-ds-base/issue/raw/files/3ad1acd301463922e58025ffd5b0326009deddf1eb26d7b1655da07571012a01-0001-Ticket-49649-Use-reentrant-crypt_r.patch
___
389-devel mailing list --
https://pagure.io/389-ds-base/issue/48377
https://pagure.io/389-ds-base/issue/raw/files/56accf80cb18a78eff15eabaefb6fcb942b2c9a7414432b8e36c0d2307e45fc8-0001-Ticket-48377-Bundle-jemalloc.patch
___
389-devel mailing list --
On 04/05/2018 07:02 AM, Florian Weimer wrote:
> On 03/29/2018 10:59 PM, Mark Reynolds wrote:
>> I believe it's our cmocka tests that occur at rpm package time that
>> brought this to our attention. So it is easy to reproduce.
>
> Well, I tried, but the package no longer bu
On 03/29/2018 04:45 PM, Florian Weimer wrote:
> On 03/29/2018 10:25 PM, Mark Reynolds wrote:
>> We can not back out the atomic work
>> because it's needed to address several issues in our server.
First of all, I updated the request wiki page to answer some of John's
questions
On 03/28/2018 12:29 AM, John Reiser wrote:
> On 03/27/2018 14:17 UTC, Jan Kurik wrote:
>> = Proposed Self Contained Change: Stop building 389-ds-base on i686 =
>> https://fedoraproject.org/wiki/Changes/389-ds-base-remove-686
>>
>>
>> Owner(s):
>> * M
Thanks!
Forwarded Message
Subject:[389-devel] please review: Ticket 49618 - Fix compiler
warnings on arm
Date: Wed, 21 Mar 2018 16:47:28 -0400
From: Mark Reynolds <mreyno...@redhat.com>
Reply-To: 389 Directory server developer discussion.
<
Note - this did pass coverity scans.
https://pagure.io/389-ds-base/pull-request/49621
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
https://pagure.io/389-ds-base/issue/49599
https://pagure.io/389-ds-base/issue/raw/files/615a6b5b74bae5d55189fdebd8841095eb2c02ad629101d50d450b129932d91f-0001-Ticket-49599-Revise-replication-total-init-status-me.patch
___
389-devel mailing list --
master branch only
https://pagure.io/389-ds-base/issue/49596
https://pagure.io/389-ds-base/issue/raw/files/f6a2c1a621d1612d23e113bb064d63f5ee86a6ebf7818515bd2c4ac9b25c3e9c-0001-Ticket-49596-repl-monitor.pl-fails-to-find-db-tombst.patch
___
389-devel
https://pagure.io/389-ds-base/issue/raw/files/e98427f971fd29c6d7ead1d975b71aef25c2b7b6e441c59cc3c04a82196dad73-0001-Ticket-49296-Fix-race-condition-in-connection-code-w.patch
On 02/17/2018 06:45 PM, Mark Reynolds wrote:
> https://pagure.io/389-ds-base/issue/49296
>
> https://pagure.io/38
Fixed typos in commit message
https://pagure.io/389-ds-base/issue/raw/files/5fe67b5583f885d5954485320da3eb3fd0dc11b6d3be4fc0e2d6146232db0b9e-0001-Ticket-49296-Fix-race-condition-in-connection-code-w.patch
On 02/17/2018 06:45 PM, Mark Reynolds wrote:
> https://pagure.io/389-ds-base/issue/49
https://pagure.io/389-ds-base/issue/49296
https://pagure.io/389-ds-base/issue/raw/files/e472a4a1d560bb5fdad852a5d6097ec4ffa8d87dc67416524d36ecfdbc1ff488-0001-Ticket-49296-Fix-race-condition-in-connection-code-w.patch
___
389-devel mailing list --
Add support for hidden conflict entries, add option to prompt for user
password, and improve man page
https://pagure.io/389-ds-base/issue/49566
https://pagure.io/389-ds-base/issue/49568
https://pagure.io/389-ds-base/issue/raw/files/bdc1e16ec6b026be823802df25197fd121be666398b3a4f3ede4f71bee280ba9-0001-Ticket-49568-Fix-integer-overflow-on-32bit-platforms.patch
___
389-devel mailing list --
https://pagure.io/389-ds-base/issue/49557
https://pagure.io/389-ds-base/issue/raw/files/ba054169314bb68d0f63783c7c431835dfd60b36325f1bb34577e21ec6ee69cf-0001-Ticket-49557-Add-config-option-for-checking-CRL-on-o.patch
___
389-devel mailing list --
Fixes regression from previous patch for this ticket
https://pagure.io/389-ds-base/issue/49370
https://pagure.io/389-ds-base/issue/raw/files/f5d011cc871fd8b3ff31ba20f3e52ca972fa47a308150779cbd7f847e8fdfc32-0001-Ticket-49370-Crash-when-using-a-global-and-local-pw-.patch
https://pagure.io/389-ds-base/issue/49552
https://pagure.io/389-ds-base/issue/raw/files/a6b4b07908e33fc7089ef028f8b21accc7e05428bd0d344392e4ea3051a077cf-0001-Ticket-49552-Fix-build-issues-on-F28.patch
___
389-devel mailing list --
https://pagure.io/389-ds-base/issue/49546
https://pagure.io/389-ds-base/issue/raw/files/bc8f1f8028b29a03455aaf6bc0bf170ddf2b5441fd6f7a8588fb1b930097a9e9-0001-Ticket-49546-Fix-broken-snmp-MIB-file.patch
___
389-devel mailing list --
https://pagure.io/389-ds-base/issue/raw/files/1487a0f5a5664a56a03fc9d685fa66e8effaab30136fbf0f5287c74a3ba6cb99-0001-Ticket-49370-Add-all-the-password-policy-defaults-to.patch
On 01/17/2018 08:44 AM, Mark Reynolds wrote:
> https://pagure.io/389-ds-base/issue/49370
>
> https://pagure.io/38
https://pagure.io/389-ds-base/issue/49531
https://pagure.io/389-ds-base/issue/raw/files/2d6562461cb0532229373dcbc06c31994286b46f647a767111fdd9551f5e76a4-0001-Ticket-49531-coverity-issues-fix-memory-leaks.patch
___
389-devel mailing list --
https://pagure.io/389-ds-base/issue/49529
https://pagure.io/389-ds-base/issue/raw/files/60c50df29914ff67f8d99b1ac717941c6913bb069a6552cf7318f4c49877881d-0001-Ticket-49529-Fix-Coverity-warnings-invalid-deference.patch
___
389-devel mailing list --
On 01/10/2018 12:17 PM, Máirín Duffy wrote:
>
>
> On 01/10/2018 10:58 AM, Mark Reynolds wrote:
>> So you could do a filter like this for your example above:
>>
>> "(|(sn=*brown")(sn=*brown west"))"
>
> So the case I'm thinking of for the
On 01/10/2018 10:53 AM, Máirín Duffy wrote:
>
>
> On 01/10/2018 10:20 AM, Mark Reynolds wrote:
>>> Would this miss someone who had two surnames, say Sally Brown West,
>>> who chooses not to hyphenate?
>> "(sn=*brown*)"
>
> Wouldn't that al
On 01/09/2018 07:25 PM, William Brown wrote:
> Hi all,
>
> It's time that I'm looking at:
> https://pagure.io/389-ds-base/issue/49425
+1 for 1.4.0!
>
> There are some great reasons to freshen up the default objects we
> install. The current design isn't really reflective of modern directory
>
On 01/10/2018 10:08 AM, Máirín Duffy wrote:
> Hi William,
>
>> With displayname you can only sort by "order of the displaynames".
>> So we can at least consistently sort this given the scenario above!
>
> Imagine a phone book sorted this way. In the US in any given town
> there would be 50
https://pagure.io/389-ds-base/issue/raw/files/1e329597283ab242ecfe42394e817e7b408e215b73a8fc3dd715e0ed303d6a2b-0001-Ticket-49524-Password-policy-minimum-token-length-fa.patch
On 01/05/2018 12:47 PM, Mark Reynolds wrote:
> https://pagure.io/389-ds-base/issue/49524
>
> https://pagure.io/38
https://pagure.io/389-ds-base/issue/49524
https://pagure.io/389-ds-base/issue/raw/files/fb4a688293da923749d296ea9e9750645194928c258fd1d2c1264ad1759c5c45-0001-Ticket-49524-Password-policy-minimum-token-length-fa.patch
___
389-devel mailing list --
On 01/03/2018 07:33 PM, William Brown wrote:
> Hi all,
>
> We recently have completed two PR based merges, both went successfully.
>
> I think it's time we bring up again the option of allowing PR's as a
> main workflow for the project.
>
> I think we can allow both PR + patch for the time, they
https://pagure.io/389-ds-base/issue/49454
https://pagure.io/389-ds-base/issue/raw/files/8b1980ae745f8bb53766ea9dc4a0961b8fd10540d54fb11d19b1b4199218218e-0001-Ticket-49454-SSL-Client-Authentication-breaks-in-FIP.patch
___
389-devel mailing list --
https://pagure.io/389-ds-base/issue/raw/files/1bdcc745ac3c90a38f016f8d908fff397a6dfd333adccf73d81a3004c29dcaa4-0001-Ticket-49441-Import-crashes-with-large-indexed-binar.patch
On 11/06/2017 10:26 AM, Mark Reynolds wrote:
> https://pagure.io/389-ds-base/issue/49441
>
> https://pagure.
https://pagure.io/389-ds-base/issue/49441
https://pagure.io/389-ds-base/issue/raw/files/83486808065fe371fb0d253ff46503783e8494da7953a049f01baac3e51eee5e-0001-Ticket-49441-Import-crashes-with-large-indexed-binar.patch
___
389-devel mailing list --
https://pagure.io/389-ds-base/issue/raw/files/28c932acf4a8d53b1d29eb40ba83e773d145bcae7f6790ab2dd5b5b6f3fa3a2f-0001-Ticket-48393-Improve-replication-config-validation.patch
On 10/31/2017 09:42 AM, Mark Reynolds wrote:
>
>
>
> Forwarded Message
> Subject: [389
https://pagure.io/389-ds-base/issue/49439
https://pagure.io/389-ds-base/issue/raw/files/f8ce257c8c7e5f03b6b4dafb127ec86eba88dc9d9d387e35866c9144182abc1e-0001-Ticket-49439-cleanallruv-is-not-logging-information.patch
___
389-devel mailing list --
https://pagure.io/389-ds-base/issue/48007
https://pagure.io/389-ds-base/issue/raw/files/42bed2336bbecbbea60d78ffad58e727f58785854fa1c679af235384911e4b12-0001-Ticket-48007-CI-test-to-test-changelog-trimming-inte.patch
___
389-devel mailing list --
Forwarded Message
Subject:[389-devel] revised: Ticket 48393 - Improve replication
configuration validation
Date: Tue, 24 Oct 2017 16:10:39 -0400
From: Mark Reynolds <marey...@redhat.com>
Reply-To: 389 Directory server developer discussion.
<
ou!
>
> -jeaton
>
>> On Oct 26, 2017, at 12:50 PM, Mark Reynolds <marey...@redhat.com
>> <mailto:marey...@redhat.com>> wrote:
>>
>>
>>
>> On 10/26/2017 12:16 PM, Jeffrey Eaton wrote:
>>> I recently updated to 389-ds-base-1.2.11.15-91
On 10/26/2017 12:16 PM, Jeffrey Eaton wrote:
> I recently updated to 389-ds-base-1.2.11.15-91.el6_9.x86_64 (from
> 389-ds-base-1.2.11.15-50.el6_6.x86_64) and have uncovered a bug with
> large paged searches blocking all other searches on the server. I
> tried to access
Forgot to check repl agreement port:
new patch:
https://pagure.io/389-ds-base/issue/raw/files/0d57b7a929a7b10606c5a77e00830b3a0216c5c3eee146df86e35b7557a7233b-0001-Ticket-48393-Improve-replication-config-validation.patch
On 10/24/2017 03:45 PM, Mark Reynolds wrote:
> https://pagure.io/389
https://pagure.io/389-ds-base/issue/48393
https://pagure.io/389-ds-base/issue/raw/files/c8e2c41df8b62afd501fa7acc40f796051ba37b93be411828b959396eafae578-0001-Ticket-48393-Improve-replication-config-validation.patch
___
389-devel mailing list --
https://pagure.io/389-ds-base/issue/49408
https://pagure.io/389-ds-base/issue/raw/files/19e8a656064e14c0eeff89c3adcbe8b71aaa70aec3a339792b71be3004c7ada5-0001-Ticket-49408-Server-allows-to-set-any-nsds5replicaid.patch
___
389-devel mailing list --
https://pagure.io/389-ds-base/issue/49374
https://pagure.io/389-ds-base/issue/raw/files/98d8adb2064c95cf41b1d6b9cad78430d75d154fc224cb64e3fc92a837f26d60-0001-Ticket-49374-server-fails-to-start-because-maxdisksi.patch
___
389-devel mailing list --
Forwarded Message
Subject:[389-devel] please review: Ticket 48006 - Missing warning for
invalid replica backoff configuration
Date: Thu, 12 Oct 2017 16:48:16 -0400
From: Mark Reynolds <marey...@redhat.com>
Reply-To: 389 Directory server developer disc
https://pagure.io/389-ds-base/issue/49402
https://pagure.io/389-ds-base/issue/raw/files/07495973b43685a1828e7f760e135f6cefc477afff348ae2c460dcfe2c882fbd-0001-Ticket-49402-Adding-a-database-entry-with-the-same-d.patch
___
389-devel mailing list --
https://pagure.io/389-ds-base/issue/48006
https://pagure.io/389-ds-base/issue/raw/files/cf1cef181ca218da231f86950e1a9f59397e1f7d22c4c7f55fbd7d3d18ff-0001-Ticket-48006-Missing-warning-for-invalid-replica-bac.patch
___
389-devel mailing list --
https://pagure.io/389-ds-base/issue/49038
https://pagure.io/389-ds-base/issue/raw/files/6f76fa2018f45c3099a992a647afc415b917962273e81e2dacb6895efc28c401-0001-Ticket-49038-remove-legacy-replication-change-cleanu.patch
___
389-devel mailing list --
udwig
>
> On 07/12/2017 09:48 PM, Mark Reynolds wrote:
>> https://pagure.io/389-ds-base/issue/49038
>>
>> https://pagure.io/389-ds-base/issue/raw/fd4fec903b65d4a7cb32861012f24f5be76d1b1804823c972bc02963de9a3d20-0001-Ti
https://pagure.io/389-ds-base/issue/49320
https://pagure.io/389-ds-base/issue/raw/files/7cfbeb0330a5dca83d82f04f6795d0eb71f9053e2e1f4faf77e73de9b4c61c1b-0001-Ticket-49320-Activating-already-active-role-returns-.patch
___
389-devel mailing list --
https://pagure.io/389-ds-base/issue/49388
https://pagure.io/389-ds-base/issue/raw/files/c228847c7da44f3a4cd1c410506a5ec952e2d5533c80ee148538b819a31a89eb-0001-Ticket-49388-repl-monitor-matches-null-string-many-t.patch
___
389-devel mailing list --
https://pagure.io/389-ds-base/issue/49092
https://pagure.io/389-ds-base/issue/raw/files/cf6f75525dc4eca61a79ab5e093ea0b92d81512025b169ded542c818f08be196-0001-Ticket-49092-Add-CI-test-for-schema-reload.patch
___
389-devel mailing list --
Revised:
https://pagure.io/389-ds-base/issue/raw/files/582c7d6904a1723a8b561ac1b821e26836fad529c81f8355119c74af174de184-0001-Ticket-49385-Fix-coverity-warnings.patch
On 09/29/2017 11:28 AM, Mark Reynolds wrote:
> https://pagure.io/389-ds-base/issue/49385
>
> https://pagure.io/389-ds-b
https://pagure.io/389-ds-base/issue/49385
https://pagure.io/389-ds-base/issue/raw/files/ee9f6ff34fcd4d54094c8b4883397bd21d2affaaecb3a53c82fe117600b593f2-0001-Ticket-49385-Fix-coverity-warnings.patch
___
389-devel mailing list --
Revised...
https://pagure.io/lib389/issue/raw/files/b3226661ff80e1253908fa74aef8603b25eb06c6179b52bf1902eb1968bc7621-0001-Ticket-100-Add-ENV-var-for-preserving-core-files.patch
On 09/28/2017 04:57 PM, Mark Reynolds wrote:
> https://pagure.io/lib389/issue/100
>
> https://pagure.io/lib
https://pagure.io/lib389/issue/100
https://pagure.io/lib389/issue/raw/files/520cb8277ae20eff1f5b791976d696d32481bb4e79a3ea111210c17324e405fc-0001-Ticket-100-Add-ENV-var-for-preserving-core-files.patch
___
389-devel mailing list --
https://pagure.io/389-ds-base/issue/49305
https://pagure.io/389-ds-base/issue/raw/files/cc4ec2d39d7beeb323184e53ae04af91dd31c37d16beb5985a7ba213a5f1e70c-0001-Ticket-49305-Need-to-wrap-atomic-calls.patch
___
389-devel mailing list --
https://pagure.io/389-ds-base/issue/raw/files/f0e5b0ab8e60c3e86dbb47c2bad9aaaec116161220bdfbd3c89459d85a54051b-0001-Ticket-49327-Add-CI-test-for-password-expiration-con.patch
Added more tests to the script...
On 09/20/2017 12:09 PM, Mark Reynolds wrote:
> https://pagure.io/389-ds-base/is
https://pagure.io/389-ds-base/issue/49327
https://pagure.io/389-ds-base/issue/raw/files/29d1d8592045b32fe8a7f5a0e65410228e17cdc7bb0c63d449bc3b2d7b98bfed-0001-Ticket-49327-Add-CI-test-for-password-expiration-con.patch
___
389-devel mailing list --
https://pagure.io/389-ds-base/issue/49327
https://pagure.io/389-ds-base/issue/raw/files/f247b3545fab542b24f88aae6dbd320bb0a3236c6bc72178614178df2516f7df-0001-Ticket-49327-password-expired-control-not-sent-durin.patch
___
389-devel mailing list --
CI Test
https://pagure.io/389-ds-base/issue/raw/files/deb567b0489df055329680573d24f60b0593e2c29506d7fbfe113d0821bbb806-0001-Ticket-49380-Add-CI-test.patch
On 09/13/2017 09:30 AM, Mark Reynolds wrote:
> https://pagure.io/389-ds-base/issue/49380
>
> https://pagure.io/389-ds-base/issue/
https://pagure.io/389-ds-base/issue/49295
https://pagure.io/389-ds-base/issue/raw/files/7b69103cff33e97cc76bf6ef7743076ab23c7197bc48a608f4c5fee3e1e62f23-0001-Ticket-49295-Fix-CI-Tests.patch
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
https://pagure.io/389-ds-base/issue/49370
https://pagure.io/389-ds-base/issue/raw/files/0df9672144d4292371ad05d722e9f444756e2f4536248ef984234663114044bc-0001-Ticket-49370-local-password-policies-should-use-the-.patch
___
389-devel mailing list --
https://pagure.io/389-ds-base/issue/49295
https://pagure.io/389-ds-base/issue/raw/files/feca1c383cf621a2101301aff434eb7fea620222513834530f8147f671fda751-0001-Ticket-49295-Fix-CI-tests.patch
___
389-devel mailing list --
https://pagure.io/389-ds-base/issue/49038
https://pagure.io/389-ds-base/issue/raw/files/e95b7815ec6de03ea3dbec6bdad8b48006beeaf8224ed25c7c99aedbd14a23b4-0001-Ticket-49038-Fix-regression-from-legacy-code-cleanup.patch
___
389-devel mailing list --
On 08/02/2017 11:49 AM, Ilias Stamatis wrote:
> Hello,
>
> I would like some help in order to understand entryrdn.db. When I do
> "dbscan -f entryrdn.db" I get something like:
>
> 3
> ID: 3; RDN: "ou=Groups"; NRDN: "ou=groups"
>
> C3
> ID: 6; RDN: "cn=Accounting Managers"; NRDN:
301 - 400 of 936 matches
Mail list logo