On Mon, Mar 19, 2018 at 05:04:17PM +0100, Rene Engelhard wrote:
> I am not going over the .-release procedure for this, I'd have uploaded
> to security, though, but...
>
> I don't think we should special-case our oldest,
> soon-to-be-not-supported release.
Agreed, it doesn't make sense to fix this bug on it's own. We can
simply piggyback it on the next more severe graphite update.
Cheers,
Moritz