This bug is fixed in version 1.6-1, I errenously set the version of
the bug to 1.6-1 when it only applies to 1.5-1.

Should the bug be closed then?

Ólafur Jens Sigurðsson

Reply via email to