According to upstream this patch has been included starting with 0.68,
and indeed 0.69 still has the patched code, so I guess this bug could
simply be closed using the version tracking feature of the BTS via a
mail to <[EMAIL PROTECTED]> starting with
| Package: mtr
| Version: 0.69-1
|
and adding an explanation.

HTH,
Flo

Attachment: signature.asc
Description: Digital signature

Reply via email to