Yes, this was a workaround for  an upstream issue, which has since been
corrected.   However, I forgot about it and neglected to remove it with
the last upload.

Thanks for the reminder/patch.

Reply via email to