Comment 6 for bug 300006

Thanks. This looks like an issue with a roundtripped revision in the past. Any chance you can run this again with the attached patch? That should give a somewhat better error message.