Hi, According to John Goerzen, this bug should have been fixed since upstream version 2.0-beta2. Considering versions > 2.0 are available in stable, testing, and unstable, maybe this bug can be closed, now ?
Regards Regis -- "While a monkey can be a manager, it takes a human to be an engineer" Erik Zapletal
