<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class="">
<br class=""><div><blockquote type="cite" class=""><div class="">On Feb 3, 2016, at 5:12 PM, Adam Dershowitz <<a href="mailto:dersh@alum.mit.edu" class="">dersh@alum.mit.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class="">
<br class=""><div class=""><blockquote type="cite" class=""><div class="">On Feb 3, 2016, at 5:02 PM, Clemens Lang <<a href="mailto:cal@macports.org" class="">cal@macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi,<br class=""><br class="">On Wed, Feb 03, 2016 at 04:44:45PM -0600, Adam Dershowitz wrote:<br class=""><blockquote type="cite" class="">Port outdated correctly shows that there is a new upgrade:<br class="">port outdated<br class="">openmodelica-devel 1.9.4~dev.beta1-13-g632349b_0 < 1.9.4~dev.beta1-24-g38d8642_0<br class=""><br class="">But upgrade doesn’t do anything:<br class=""><br class="">sudo port upgrade openmodelica-devel <br class="">Password:<br class="">---> Scanning binaries for linking errors<br class="">---> No broken files found. <br class=""></blockquote><br class="">This behavior happens on purpose if the version you had activated at the<br class="">time of the upgrade is not the most recent version (i.e. you had a newer<br class="">version installed, but deactivated). Please check if that was the case<br class="">for you. This is not a bug, but actually a supported feature that can be<br class="">used as poor man's pinning.<br class=""><br class=""><br class="">-- <br class="">Clemens<br class=""></div></div></blockquote></div><br class=""><div class=""><div class="">That is not the case here. I had the newest version installed and active (beta1-13). I then did a port sync and it found that beta1-24 was now available, as shown above. But, it will not perform that upgrade! If I want to have the newest version I need to first deactivate. </div><div class="">Until recently they did not have beta in the name (I think that they are getting ready for a release version, so have started calling these versions “beta”). Prior versions had names like “<span class="" style="font-family: Menlo; font-size: 11px;">@1.9.4~dev-613-ga36a93f_0</span>” And in those cases macports did upgrade. For every other port, and this one until recently, sudo port upgrade outdated would upgrade to the newest version if I had the prior newest version active. </div></div><div class=""><br class=""></div><div class="">—Adam</div></div><br class=""></div></blockquote><br class=""></div><div>But, I think that I do see what is going on. </div><div>It seems that it is a unix sort issue. Macports thinks that "<font face="Menlo" class=""><span style="font-size: 11px;" class="">@1.9.4~dev.beta1-13-g632349b_0” comes before "@1.9.4~dev-613-ga36a93f_0” and therefore it think that I don’t have the newest version active (it happens to be wrong about that). </span></font></div>So, this “feature” is stopping the newest version from being installed. One solution would be to delete all of my old versions, but I would prefer not to do that. Is there any other way to tell macports to do the upgrade anyway? <div class=""><br class=""></div><div class="">—Adam<br class=""><div class=""><br class=""></div></div></body></html>