Browsing through the code of 0.67-1 and 0.69-2 I see upstream basically covers this issue via a different implementation of sanity checks, so I guess this bug can be closed.
Using the version tracking feature of the BTS a mail to <[EMAIL PROTECTED]> with the body starting with | Package: mtr | Version: 0.67-1 | and adding an explanation will probably suffice. HTH, Flo
signature.asc
Description: Digital signature
