Hey all,
Environment files are updated. Please download and reinstall like normal.
Things should be working again.
We identified the issue, it involved a few pieces.
The first piece was that bioconda did a reasonably routine "bulk update" of their packages, which included unifrac-binaries. This happened 3 days and 4 hours ago according to the site, which is consistent with the timeline.
The next issue, was that unifrac-binaries does not set hdf5 as a dependency in its host or run section of the recipe.
This means that while a particular version of HDF5 is pulled in during compilation of unifrac-binaries, that version is not referenced during installation. So conda allows any version of hdf5, hence:
ImportError: libhdf5_cpp.so.200: cannot open shared object file: No such file or directory
This particular libhdf5_cpp.so.200 shared-object is only available with hdf5=1.12 (the version that this new build was compiled against). However our environment is configured to use hdf5=1.10 which was the version that the previous build compiled was against.
To avoid these issues, conda provides a run_exports directive which can inflict a pinning on downstream dependencies if they set them as a host (or in some cases run) dependency. This would prevent conda from installing a new build if it knew that it required a different host dependency than what was available.
Fortunately, the hdf5 recipe also sets a run_exports which would have worked had hdf5 been included as a host dependency in unfrac-binaries.
We've applied a quick fix to pin unifrac-binaries at the last build. So this should be resolved for now. But ultimately, the unfrac-binaries recipe will need to be updated with additional dependencies to avoid this happening next time there's a recompile between releases.
(There's an additional issue of OS X builds not currently compiling which is why this situation didn't impact OS X as far as we can tell. There were no new builds to cause the HDF5 mismatch on OS X.)