This appears to have been fixed in version 2:1.07-2.  I encourage the 
maintainer to close this bug.

Reply via email to