No. We *could* have fixed 6.1-000 before (and it would have migrated to
testing then) but since you immediately started working on 6.2 I
considered it more sensible to fix it in 6.2 which can close the bug
in the same manner.
Hmm, strictly speaking the bug is in 6.1-000 and won't be fixed by
uploading 6.2-000. I think the bug should not be assigned to package
fis-gtm but rather fis-gtm-6.1-000 (and of course be fixed in
fis-gtm-6.2-000 as well)
Hmmm, the affected fis-gtm-6.1-000 will vanish from Debian mirror, after
fis-gtm-6.2-000 will be accepted.