>>> ---------- Forwarded message ----------
>>>
>>> From: Lenore Horner <lenorehor...@sbcglobal.net>
>>> Subject: Install failed but didn't?
>>> Date: March 9, 2022 at 20:50:39 EST
>>> To: MacPorts Users <macports-users@lists.macports.org>
>>>
>>>
>>> This set of responses seems peculiar.
>>>
>>> sudo port selfupdate
>>> Password:
>>> ---> Updating MacPorts base sources using rsync
>>> MacPorts base version 2.7.1 installed,
>>> MacPorts base version 2.7.2 downloaded.
>>> ---> Updating the ports tree
>>> ---> MacPorts base is outdated, installing new version 2.7.2
>>> Installing new MacPorts release in /opt/local as root:wheel; permissions
>>> 0755
>>>
>>> Error: Error installing new MacPorts base: command execution failed
>>> Please run `port -v selfupdate' for details.
>>> Error: /opt/local/bin/port: port selfupdate failed: Error installing new
>>> MacPorts base: command execution failed
>>> sudo port selfupdate
>>> Password:
>>> ---> Updating MacPorts base sources using rsync
>>> MacPorts base version 2.7.2 installed,
>>> MacPorts base version 2.7.2 downloaded.
>>> ---> Updating the ports tree
>>> ---> MacPorts base is already the latest version
>>>
>>> The ports tree has been updated. To upgrade your installed ports, you
>>> should run
>>> port upgrade outdated
>
> I agree, that is peculiar.
>
> Does "port version" now show that 2.7.2 is installed? If so, it probably is.
>
> You could run "sudo port -fv selfupdate" to force MacPorts to reinstall 2.7.2
> even though it thinks it already has. If you try that and it experiences some
> error, let us know.
>
I did that and it failed but then I remembered that things like sudo periodic
weekly also fail unless I’m at the top level of my personal hierarchy (~) so I
repeated the command from there and it worked. I’m not sure if that is the way
things are supposed to behave, but at least there’s an obvious pattern and a
simple solution.
Lenore
