Haha. I finally worked out that the issue was with one of the patches applied to the sources for the debian package, worked out which one, and emailed the author. What I didn't work out until he replied was that he'd already fixed the problem, and the new version of the package had been in debian unstable for a couple of days. D'oh!
Anyway, thanks everybody for the helpful comments.
Rupert