port version reports 2.4.2 when built from tag v2.4.3

Ryan Schmidt ryandesign at macports.org
Thu Apr 12 22:44:05 UTC 2018


On Apr 12, 2018, at 17:42, Jack Howarth wrote:

> This issue

"This issue" isn't an issue, it's just a misunderstanding of how the shell caches information.

> might also be impacting the High Sierra macports 2.4.3 installer image as well. After installing it on a machine with no /opt/local, I get the following from 'sudo port self update'...
> 
> --->  Updating MacPorts base sources using rsync
> MacPorts base version 2.4.3 installed,
> MacPorts base version 2.4.2 downloaded.
> --->  Updating the ports tree
> --->  MacPorts base is probably trunk or a release candidate
> 
> The ports tree has been updated. To upgrade your installed ports, you should run
>   port upgrade outdated
> 
> When I execute 'sudo port upgrade outdated', I get...
> 
> Nothing to upgrade.

That's a server problem that should be resolved within the hour.



More information about the macports-dev mailing list