On Sun, Jan 18, 2026 at 3:45 PM Clemens Lang <[email protected]> wrote:
> Hi, > > On 18. Jan 2026, at 18:40, Fred Wright <[email protected]> wrote: >> >> >> On Wed, 14 Jan 2026, Clemens Lang wrote: >>> this is a heads-up that I’m planning to land OpenSSL 3.6 ( >>> https://github.com/macports/macports-ports/pull/29589) in a day or two. >> >> >> Since this has now happened before fixing the certificate problem, the >> openssl3 port is now based on unmirrored distfiles, ensuring that it won't >> build on <10.12 without manual intervention. > > > I wasn’t aware of this problem, but it’s certainly something we should > generally fix. Any other foundational port would have triggered the same > problem. Not just foundational ports. Based on my anecdotal observations, right now, ALL ports are failing to build on the <10.12 buildbot builders due to the certificate problem. -- Jason Liu On Sun, Jan 18, 2026 at 3:45 PM Clemens Lang <[email protected]> wrote: > Hi, > > > On 18. Jan 2026, at 18:40, Fred Wright <[email protected]> wrote: > > > > > > On Wed, 14 Jan 2026, Clemens Lang wrote: > > > >> this is a heads-up that I’m planning to land OpenSSL 3.6 ( > https://github.com/macports/macports-ports/pull/29589) in a day or two. > > > > Since this has now happened before fixing the certificate problem, the > openssl3 port is now based on unmirrored distfiles, ensuring that it won't > build on <10.12 without manual intervention. > > I wasn’t aware of this problem, but it’s certainly something we should > generally fix. Any other foundational port would have triggered the same > problem. > > > >> The changes should be ABI- and API-compatible, so no revbump of > dependent ports would be required (except the ones we always bump as > documented in the Portfile). > > > > And since the revbump doesn't involve new distfiles, the revbummped > ports will often be updated without updating the openssl3 port, probably > creating inconsistencies. > > This only happens if you run `port upgrade` with `-p`. The manpage > explicitly tells you not to do that for exactly this reason: > > WARNING: This option is harmful to upgrade and should be avoided at all > cost. Often, MacPorts ports are only upgraded to rebuild them against > updated dependencies. Specifying this flag will cause a spurious rebuild if > a dependency of a port fails to build and leave your system in a broken > state once the dependent port is fixed. > > https://man.macports.org/port-upgrade.1.html > > > If you didn’t know that, you do now and you should stop using that flag. > If you did know and are using it anyway, you get to keep the broken pieces. > > > >
