<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">This ticket is showing the same error, although the situation is slightly different, since it is using the older version that worked fine for me:<div class=""><a href="https://trac.macports.org/ticket/52289" class="">https://trac.macports.org/ticket/52289</a></div><div class=""><br class=""><div class="">
<div class=""><br class="khtml-block-placeholder"></div><div class="">--Adam</div><div class=""><br class="khtml-block-placeholder"></div><div class=""><br class="khtml-block-placeholder"></div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Oct 13, 2016, at 12:07 PM, Ryan Schmidt <<a href="mailto:ryandesign@macports.org" class="">ryandesign@macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class=""><blockquote type="cite" class="">On Oct 13, 2016, at 11:05 AM, Eric A. Borisch <<a href="mailto:eborisch@macports.org" class="">eborisch@macports.org</a>> wrote:<br class=""><br class="">As the error message points out, you can set HDF5_DISABLE_VERSION_CHECK=1 (or 2) to make things run. As they say, don't blame them if it crashes.<br class=""><br class="">There are plenty of reports out there (outside of MP) on this HDF5 feature. As far as I can tell, the HDF5 group's position is that they are used for storing critical data (output from experiments that you don't want to have to "re-do"), so they don't ever want to be the cause of errors from unintentional / unexpected behavior, even if the program can happily link.<br class=""><br class="">It would be nice if we had some centralized way to handle this rather than rev-bumping each dependent port, but that is where we are currently at. Is it possible to have an hdf5 PortGroup where we could centrally bump an epoch?<br class=""></blockquote><br class="">No; bumping the epoch is not sufficient; you must change the revision or version for MacPorts to see it as an upgrade.<br class=""><br class=""><br class=""><br class=""></div></div></blockquote></div><br class=""></div></body></html>