Now that 8.3.0-2 has landed in testing, I can confirm that the bug
has been fixed.

  Thanks, Detlef

Reply via email to