[389-devel] please review ticket #55 - limit of 1024 chars in nsMatchingRule

This fix is now correctly tested. https://fedorahosted.org/389/attachment/ticket/55 https://fedorahosted.org/389/attachment/ticket/55/0001-Ticket-55-Limit-of-1024-characters-for-nsMatchingRul.patch Thanks, Mark -- 389-devel mailing list 389-devel@lists.fedoraproject.org

[389-devel] please review ticket 38 - nisDomain schema is incorrect

https://fedorahosted.org/389/attachment/ticket/38 https://fedorahosted.org/389/attachment/ticket/38/0001-Ticket-38-nisDomain-schema-is-incorrect.patch Thanks, Mark -- 389-devel mailing list 389-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel

[389-devel] please review revision to ticket 6 - protocol error with proxied authentication

https://fedorahosted.org/389/attachment/ticket/6 https://fedorahosted.org/389/attachment/ticket/6/0001-Ticket-6-protocol-error-when-doing-a-proxied-auth.patch Thanks, Mark -- 389-devel mailing list 389-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel

[389-devel] Please review: [389 Project] #274: Reindexing entryrdn fails if ancestors are also tombstoned

https://fedorahosted.org/389/ticket/274 https://fedorahosted.org/389/attachment/ticket/274/0001-Trac-Ticket-274-Reindexing-entryrdn-fails-if.patch Bug description: Inserting/traversing entryrdn fails if a parent entry is tombstoned and the rdn in the entryrdn index includes nsuniqueid. In DIT