For the reference, this issue is fixed as of version 4.13.2-1, available in both testing and unstable. This bug may be now closed (I would do it myself, but I am unsure whether it would break some rule here and how to do it). -- Best regards Mirosław Zalewski