On Wed, Jan 7, 2026 at 8:13 PM Fred Wright <[email protected]> wrote:
> > On Wed, 7 Jan 2026, Dave Allured - NOAA Affiliate via macports-dev wrote: > > > This is *not* a mirrors problem. All mirrors take their distfiles from > > distfiles.macports.org/PORTNAME/. The problem is that this primary > > MacPorts site is NOT getting updated correctly. Look in > > https://distfiles.macports.org/py-meson/ for example. The new distfile > > "meson-1.10.0.tar.gz" should be there following yesterday's port update, > > but that file is MISSING. Same is true for octave-dicom. The mirrors > are > > all doing what they are supposed to do. They can not make up content > that > > was never there in the first place. > > The problem with 'lis' *is* a mirror problem, since it shouldn't get > "Operation now in progress" from a missing file, and it shouldn't hang for > ~25 seconds in the process. > Yes agreed for 'lis'. > > So look for a problem in the MacPorts merge/update process. > > Yes, for other mirrors, the problem is presumably: > > >> On Jan 7, 2026, at 4:21 PM, Joshua Root <[email protected]> wrote: > >> > >> Indeed, the error fetching from GitHub on 10.11 is: > >> > >> Fetching distfile failed: SSL certificate problem: Invalid certificate > >> chain > > Assuming (as suggested above) that the distfile mirror distributor is > running on 10.11 and not using MacPorts curl, then all distfile mirroring > from GitHub is now broken. > Okay. I made naive assumptions about how the update and mirror processes work. I find it hard to believe that all distfile propagation is depending on MacPorts infrastructure running on a macOS as old as 10.11, so I misunderstood your analysis. I will not comment further, and hope that the problem will get resolved soon. Thanks Fred for your feedback.
