https://fedorahosted.org/389/ticket/353
https://fedorahosted.org/389/attachment/ticket/353/0001-Ticket-353-coverity-12625-12629-leaks-dead-code-unch.patch
--
389-devel mailing list
389-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-devel
On 04/21/2012 07:18 AM, Jeroen van Meeuwen (Kolab Systems) wrote:
Hi there,
In a scenario where I'm trying to setup a 389 Directory Server automatically,
I ran into an issue with checking ports - no ports nor any networking, are
available when I execute the setup. FWIW, I'm bootstrapping the
I pushed the 389-ds-base-1.2.11 branch and released 389-ds-base-1.2.11.1
Unless you have fixes that are required to get into 1.2.11, just
continue to use master
--
389-devel mailing list
389-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-devel