> On Feb 3, 2016, at 5:02 PM, Clemens Lang <c...@macports.org> wrote:
>
> Hi,
>
> On Wed, Feb 03, 2016 at 04:44:45PM -0600, Adam Dershowitz wrote:
>> Port outdated correctly shows that there is a new upgrade:
>> port outdated
>> openmodelica-devel 1.9.4~dev.beta1-13-g632349b_0 <
>> 1.9.4~dev.beta1-24-g38d8642_0
>>
>> But upgrade doesn’t do anything:
>>
>> sudo port upgrade openmodelica-devel
>> Password:
>> ---> Scanning binaries for linking errors
>> ---> No broken files found.
>
> This behavior happens on purpose if the version you had activated at the
> time of the upgrade is not the most recent version (i.e. you had a newer
> version installed, but deactivated). Please check if that was the case
> for you. This is not a bug, but actually a supported feature that can be
> used as poor man's pinning.
>
>
> --
> Clemens
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.
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 “@1.9.4~dev-613-ga36a93f_0” 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.
—Adam
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
