https://pagure.io/389-ds-base/pull-request/50248
https://pagure.io/389-ds-base/issue/50230
--
Sincerely,
William
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
> On 27 Feb 2019, at 10:34, William Brown wrote:
>
> I did a merge for a PR, and now everything on pagure seems to have locked up?
Pagure reset, and when I tried again it froze again.
https://pagure.io/389-ds-base/pull-request/50244 is the PR I’m trying to merge.
I may just cherry-pick to
On 2/26/19 4:26 PM, William Brown wrote:
On 26 Feb 2019, at 18:32, Ludwig Krispenz wrote:
Hi, I need a bit of time to read the docs and clear my thoughts, but one
comment below
On 02/25/2019 01:49 AM, William Brown wrote:
On 23 Feb 2019, at 02:46, Mark Reynolds wrote:
I want to start a
> On 26 Feb 2019, at 18:32, Ludwig Krispenz wrote:
>
> Hi, I need a bit of time to read the docs and clear my thoughts, but one
> comment below
> On 02/25/2019 01:49 AM, William Brown wrote:
>>
>>> On 23 Feb 2019, at 02:46, Mark Reynolds wrote:
>>>
>>> I want to start a brief discussion
There is already features in lib389 for managing aci, but due to the design of
aci in DS they are *super hard* to represent correctly in DSLdapObjects. I
think the existing lib389 aci code could be adapted to extend dsldapobject to
have some aci tranform capabilities, but they wouldn’t be
On 2/11/19 10:03 AM, Mark Reynolds wrote:
https://pagure.io/389-ds-base/pull-request/50216
___
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:
@Matus Honek
Yes, I agree.
Perhaps we should open one ticket in pagur to track this issue ?
Regards
Anuj Borah
On Tue, Feb 26, 2019 at 9:12 PM Matus Honek wrote:
> This kinda leads me to thinking we should implement ACIs management
> within the DSLdapObjects like this (probably specific
This kinda leads me to thinking we should implement ACIs management
within the DSLdapObjects like this (probably specific to a particular
subclass, to a degree). One that would take care of this added
requirement for objectclass ACIs because of hidden .filter's behavour.
Because that is currently
Hi, I need a bit of time to read the docs and clear my thoughts, but one
comment below
On 02/25/2019 01:49 AM, William Brown wrote:
On 23 Feb 2019, at 02:46, Mark Reynolds wrote:
I want to start a brief discussion about a major problem we have backend
transaction plugins and the entry
