Re: curl and openSSL

2022-04-13 Thread James Secan
Thanks. I’ll pass that along to the person from NASA who contacted me. Jim > On Apr 13, 2022, at 1:07 AM, Clemens Lang wrote: > > On Tue, Apr 12, 2022 at 02:16:08PM -0700, James Secan wrote: >> It’s a US Gov’t site (NASA): cddis.nasa.gov. I’m accessing data on >> their Space Geodesy Data

Re: During Migration to Arm64 mac, should I null out archs='x86_64' from installed ports list?

2022-04-13 Thread Peter Serocka
FWIW, I have found it useful to install MacPorts under a new prefix with every MacOS/Darwin release (like /opt/macports##). This offers a soft transition, as installed stuff usually keeps working after OS upgrades. It has even made sense to hack the port command a little bit, to allow plain

Re: curl and openSSL

2022-04-13 Thread Clemens Lang
On Tue, Apr 12, 2022 at 02:16:08PM -0700, James Secan wrote: > It’s a US Gov’t site (NASA): cddis.nasa.gov. I’m accessing data on > their Space Geodesy Data archive, pulling files from directory > archive/gnss/products/ionex. I filed an initial complaint with them > yesterday before I knew in

Re: Corrupted ports.tar file?

2022-04-13 Thread Joshua Root
Bill Cole wrote: Theory: it's a problem related to running the reclaim from the prompt at the tail end of a selfupdate. Incomplete 'portindex' run perhaps? Good theory. It's likely that when the periodic reclaim run at exit was added, it wasn't considered that it might be running after code

Re: Corrupted ports.tar file?

2022-04-13 Thread Bill Cole
On 2022-04-13 at 00:34:02 UTC-0400 (Tue, 12 Apr 2022 23:34:02 -0500) Ryan Schmidt is rumored to have said: > On Apr 11, 2022, at 17:02, Dave Horsfall wrote: > >> On Mon, 11 Apr 2022, Ryan Schmidt wrote: >> >>> Run "sudo port selfupdate" to get the most recent ports.tar. Do you >>> still see the