<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">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.<div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">port -d selfupdate</div><div class=""><br class=""></div><div class="">(which impiles -v and also adds debugging messages) should provide more detail what failed.<br class=""><div><br class=""></div><div>"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.</div><div><br class=""></div><div>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.</div><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class="">On Mar 7, 2024, at 07:30, <a href="mailto:xmartin@iqf.csic.es" class="">xmartin@iqf.csic.es</a> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Sorry for such an stupid question…<div class=""><br class=""></div><div class="">I was running an older MacPorts version on my High Sierra and wanted to upgrade the version just installing the newest one (<a class="link" href="https://github.com/macports/macports-base/releases/download/v2.9.1/MacPorts-2.9.1-10.13-HighSierra.pkg" target="_top">MacPorts-2.9.1-10.13-HighSierra.pkg</a>) existing for my iMac. I did it and and it was made with getting no errors or warnings. </div><div class=""><br class=""></div><div class="">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. </div><div class=""><br class=""></div><div class="">And when I try to run “sudo port selfupdate” I get the following error:</div><div class=""><br class=""></div><div class=""><div class="" style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);"><span class="" style="font-variant-ligatures: no-common-ligatures;">---> Updating MacPorts base sources using rsync</span></div><div class="" style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);"><span class="" style="font-variant-ligatures: no-common-ligatures;">Error: Error synchronizing MacPorts sources: command execution failed</span></div><div class="" style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);"><span class="" style="font-variant-ligatures: no-common-ligatures;">Please run `port -v selfupdate' for details.</span></div><div class="" style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);"><span class="" style="font-variant-ligatures: no-common-ligatures;">Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed</span></div></div><div class=""><span class="" style="font-variant-ligatures: no-common-ligatures;"><br class=""></span></div><div class=""><span class="" style="font-variant-ligatures: no-common-ligatures;">Rerunning it with the -v option I get exactly the same error and my question is:</span></div><div class=""><span class="" style="font-variant-ligatures: no-common-ligatures;">What can I do to have the newest MacPorts binaries being upgraded?</span></div><div class=""><span class="" style="font-variant-ligatures: no-common-ligatures;"><br class=""></span></div><div class=""><span class="" style="font-variant-ligatures: no-common-ligatures;">Any help would be kindly appreciated….</span></div><div class=""><span class="" style="font-variant-ligatures: no-common-ligatures;">All the best,</span></div><div class=""><span class="" style="font-variant-ligatures: no-common-ligatures;">Martin</span></div><div class="">
<div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">____________________________________</div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">Dr. Martin Martinez-Ripoll<br class="">Research Professor Emeritus<br class=""><a href="mailto:xmartin@iqf.csic.es" class="">xmartin@iqf.csic.es</a><br class="">Dept. of Crystallography & Structural Biology<br class=""><a href="http://www.xtal.iqfr.csic.es" class="">www.xtal.iqfr.csic.es</a><br class="">Consejo Superior de Investigaciones Científicas<br class="">Spanish National Research Council<br class="">www.csic.es</div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><br class="Apple-interchange-newline"></div></div><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br class=""></div></div></blockquote></div><br class=""></div></body></html>