That's strange, in that /opt/local/var should have been part of the original MacPorts install, too. /opt/local/var/macports is workspace for MacPorts plus information about what's installed; all the other subdirectories of /opt/local/var are for the ports to use instead of using subdirectories of /var, esp. if they might conflict with a similar program that comes with the OS.
So something may have been wrong before you did the install of the new pkg. Among other things, I'm wondering if the previous version was for an earlier version of MacOS, in which case problems could be expected. port -d selfupdate (which impiles -v and also adds debugging messages) should provide more detail what failed. "port" depends on some other commands, and will use the system version if you don't have a MacPorts version installed. Like rsync for sure (for selfupdate) and curl to fetch individual files when needed. And others like tar or cpio or gzip (and maybe additional commands) to deal with archives and compressed files, openssl to check digital signatures, etc. If any of those are missing or not working, that will be a problem. Other than that, I have no idea. I've never dug deep into how it all works, just glanced for a couple minutes at the tcl code for the "port" command and the macports specific components that it uses. There are people here who know much more, but they probably have day jobs too, so please be patient. > On Mar 7, 2024, at 07:30, xmar...@iqf.csic.es wrote: > > Sorry for such an stupid question… > > I was running an older MacPorts version on my High Sierra and wanted to > upgrade the version just installing the newest one > (MacPorts-2.9.1-10.13-HighSierra.pkg > <https://github.com/macports/macports-base/releases/download/v2.9.1/MacPorts-2.9.1-10.13-HighSierra.pkg>) > existing for my iMac. I did it and and it was made with getting no errors or > warnings. > > However, after this installation I only see that there appeared a new > directory called /opt/local/var/, but the existing executables are still the > old ones (the ones existing in the old /opt/local/bin directory. > > And when I try to run “sudo port selfupdate” I get the following error: > > ---> Updating MacPorts base sources using rsync > Error: Error synchronizing MacPorts sources: command execution failed > Please run `port -v selfupdate' for details. > Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing > MacPorts sources: command execution failed > > Rerunning it with the -v option I get exactly the same error and my question > is: > What can I do to have the newest MacPorts binaries being upgraded? > > Any help would be kindly appreciated…. > All the best, > Martin > ____________________________________ > Dr. Martin Martinez-Ripoll > Research Professor Emeritus > xmar...@iqf.csic.es <mailto:xmar...@iqf.csic.es> > Dept. of Crystallography & Structural Biology > www.xtal.iqfr.csic.es > Consejo Superior de Investigaciones Científicas > Spanish National Research Council > www.csic.es > > > > > >
