On 16-12-14 22:53, Kurt Roeckx wrote: > Which upstream? I meant openssl, as I thought William was referring to that.
> Upsteam openssl is saying that this is intentional behaviour, and > as such I won't be fixing this. Ok. So I suggest to tag this bug as wontfix, and depending on how you as a team handle wontfixes, also close the bug. >> Also, I am not sure that the current bug is really RC. What is the >> justification for it? > > I assume the FTBFS of nodejs makes this an RC bug for nodejs. It > cleary is not an RC bug in openssl. That was also my judgment. So I suggest to lower the severity as well. Although, if you close the bug, that won't be necessary. > I suggest we just reassign this to nodejs? nodejs already has an RC bug for this (#766484) including a patch. Paul
signature.asc
Description: OpenPGP digital signature
