On Wed, Jun 06, 2018 at 01:22:26PM +1000, Dean Hamstead wrote: > Rolling it in to the official release would be much appreciated as it > will spare us maintaining our own patched version, plus might help a > few lonely travelers who are stumped on a segfault.
I'm sorry that we weren't able to get to this in a timely fashion. Given that this is now fixed in current stable (and anyone affected must surely have worked around it by now), I think it's unlikely that applying this fix now will be that helpful (even if an oldstable update is going to happen at this stage). Therefore, I'm inclined to close this bug now. Let me know if you disagree. Best Dominic
