We have identified at least one problem with this patch: the packages seem to be tagged as "3.1" instead of "3.0.1". Our sustaining group is validating the rest of the content and the package will likely be re-generated.