This has been fixed upstream since version 0.9.1.

Reply via email to