On 8/1/2026 08:41, Fred Wright wrote:

12:25:59.130:: Error: Failed to fetch py313-meson: Failed connect to lis.pt.distfiles.macports.org:80; Operation now in progress

I've seen the last error multiple times lately on that particular mirror. It happens after a delay (timeout?).  I'm not sure if that mirror just happens to be the last one in the list, or if MacPorts is treating that error as fatal (the debug output suggests the latter).  In any case, that particular mirror seems to be broken right now.  Since it's an http fetch, it's obviously not an SSL/TLS issue.  I suppose the seven years of bad luck go to its owner rather than to MacPorts. :-)

Failing to fetch from all possible mirrors is what is considered fatal. Only the error from the last one is returned. That one was tried last precisely because it is not responding. I removed it from the list just now.

A separate issue is that this distfile doesn't seem to be getting to *any* of the mirrors, suggesting a problem with the mirroring mechanism.  It may not be a coincidence that GitHub fetches from 10.9 with the OS tools stopped working recently (01-Jan?), apparently due to a root CA issue on 10.9.  They do work with fetch.ignore_sslcert=yes, and of course normal SSH-based GitHub access works fine.  So perhaps the distfile mirror distributor has an expired root CA.

Indeed, the error fetching from GitHub on 10.11 is:

Fetching distfile failed: SSL certificate problem: Invalid certificate chain

- Josh

Reply via email to