Ryan is correct; I had been sync'ing my port index successfully, but MacPorts itself grew stale due to my being unable to run selfupdate. The MacPorts Migration Guide suggested a manual update (i.e. reinstall) which I believe got me going again. Thanks guys! ~SeaQuench
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, December 10th, 2021 at 3:35 AM, Ryan Schmidt <[email protected]> wrote: > On Dec 10, 2021, at 02:29, Chris Jones wrote: > > > On 9 Dec 2021, at 10:49 pm, SeaQuench wrote: > > > > > After downloading and installing the latest MacPorts for Catalina, I > > > followed the instructions to migrate MacPorts: > > > https://trac.macports.org/wiki/Migration > > > > > > Reinstalling the ports went without issue until Step 3e: `sudo > > > ./restore_ports.tcl myports.txt` > > > > > > Executing that command resulted in the error I presented initially: > > > > > > ---> Computing dependencies for python38 > > > > > > Error: Dependency 'openssl3' not found. > > > > > > ---> Computing dependencies for python39 > > > > > > Error: Dependency 'openssl3' not found. > > > > > > Is that to be expected on a fresh install (before performing a sync)? I > > > acknowledge that this outcome may result from the use of git versus rsync > > > in keeping MacPorts up to date. I am behind a firewall, so i must use git > > > to sync rather than use rsync. > > > > > > https://trac.macports.org/wiki/howto/SyncingWithGit > > > > > > If i substitute the command `sudo port -v sync` for the command `sudo > > > port selfupdate` - as usual - I can now install openssl without error, > > > and all dependencies are found after re-executing: `sudo > > > ./restore_ports.tcl myports.txt` > > > > We need to see why you are not finding the openssl3 port, as that has been > > available for some time. > > > > Please run > > > > sudo port -d sync > > > > And post what you get back to the list > > They already said that after running "sudo port sync", everything is working. > > "sudo port selfupdate" should selfupdate (update MacPorts base) and sync > (update ports tree). If updating base failed for some reason, then it might > not update the ports tree either. You mentioned being behind a firewall that > prevents you from syncing with rsync. selfupdate has no option but to use > rsync, so that would be a likely explanation for why selfupdate doesn't work > for you, and why you should not use selfupdate and should instead (i) update > MacPorts base manually when a new version is available, using an installer > from our web site and (ii) sync to update ports.
