Not sure what happened, I just rebaselined and recreated the patch.  New patch attached.  Note this also includes possible fix for bug 138.