On Sat, Mar 24, 2018 at 10:22 PM, Pelle Hjek <h...@mail.com> wrote:
> I'm not sure this bug has been resolved yet.

It is fixed in 1:3.28.0-2. Wait a few hours for the new version to
build and publish.

Thanks,
Jeremy Bicha

Reply via email to