This appears to have been fixed in #812207 so this probably needs to be merged or otherwise closed (incidentally, it appears that reporting the bug against a real package wasn't enough for it to get attention ;) Cheers, Dominic.