Hi,
Version 1.5.6 does not have this problem, so I'll package it. Anyway, I found the way upstream fixed it, so if the packaging of 1.5.6 is not successful, I can retrofit the patch.
Thanks, Fabrice
Hi,
Version 1.5.6 does not have this problem, so I'll package it. Anyway, I found the way upstream fixed it, so if the packaging of 1.5.6 is not successful, I can retrofit the patch.
Thanks,
Fabrice