As noted in comment #8, this bug has been fixed in the upstream 1.7.0 release. I am unsure how this should be reflected in the status.
As noted in comment #8, this bug has been fixed in the upstream 1.7.0 release. I am unsure how this should be reflected in the status.