On Mar 9, 2022, at 19:55, Lenore Horner wrote: > Begin forwarded message: > >> From: mailer-dae...@yahoo.com >> Subject: Failure Notice >> Date: March 9, 2022 at 20:50:45 EST >> To: lenorehor...@sbcglobal.net >> >> Sorry, we were unable to deliver your message to the following address. >> >> <macports-users@lists.macports.org>: >> 554: 5.7.1 Service unavailable
I'm not sure why service was unavailable. Maybe there was a temporary server problem. Clemens or Rainer would be the ones who could check the server logs to find out. Obviously whatever problem existed no longer exists, since you were able to send this next message. >> ---------- 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.
