On 04/15/2016 05:29 AM, Emmanuel Dreyfus wrote:
On Fri, Apr 15, 2016 at 01:32:23PM +0530, Kaushal M wrote:
Or,
2. Revert the IPv6 patch that exposed this problem
IMO the good practice when a change breaks a stable release
is to back it out, and work on a betterfix on master for later
pull up t
On Fri, Apr 15, 2016 at 2:36 PM, Niels de Vos wrote:
> On Fri, Apr 15, 2016 at 01:32:23PM +0530, Kaushal M wrote:
>> Some more (bad) news on the status of 3.7.11.
>>
>> I've been doing some more tests with release-3.7, and found that the
>> fix for solving daemons failing to start when management
On Fri, Apr 15, 2016 at 01:32:23PM +0530, Kaushal M wrote:
> Some more (bad) news on the status of 3.7.11.
>
> I've been doing some more tests with release-3.7, and found that the
> fix for solving daemons failing to start when management encryption is
> enabled doesn't work in all cases.
>
> Now
On 04/15/2016 01:32 PM, Kaushal M wrote:
> Some more (bad) news on the status of 3.7.11.
>
> I've been doing some more tests with release-3.7, and found that the
> fix for solving daemons failing to start when management encryption is
> enabled doesn't work in all cases.
>
> Now I've got 2 opti
