Thanks for reporting.

It has been fixed in version 2:2.0.3-3.

Cheers,
JL

Reply via email to