The fix for this bug seems to have been inadvertently dropped from the current development release as far as I can tell. Something happened between 2.6.0-0ubuntu7 and 2.7.1-0ubuntu1 - 2.6.0-0ubuntu8, 2.6.0-0ubuntu9 and 2.6.0-0ubuntu10 are missing from debian/changelog in 2.7.1-0ubuntu1, and the fix for this bug was in 2.6.0-0ubuntu10 but vanished in 2.7.1-0ubuntu1. It looks like other fixes were also dropped somewhere, but I haven't investigated further.
Please could you investigate, fix up as needed, and explain what happened and how it was resolved so I can understand how to review this?
The fix for this bug seems to have been inadvertently dropped from the current development release as far as I can tell. Something happened between 2.6.0-0ubuntu7 and 2.7.1-0ubuntu1 - 2.6.0-0ubuntu8, 2.6.0-0ubuntu9 and 2.6.0-0ubuntu10 are missing from debian/changelog in 2.7.1-0ubuntu1, and the fix for this bug was in 2.6.0-0ubuntu10 but vanished in 2.7.1-0ubuntu1. It looks like other fixes were also dropped somewhere, but I haven't investigated further.
Please could you investigate, fix up as needed, and explain what happened and how it was resolved so I can understand how to review this?