On Sun, Aug 10, 2025 at 03:07:43PM -0400, Tom Lane wrote:
> Noah Misch <noah@leadboat.com> writes:
> > On Sun, Mar 09, 2025 at 10:23:55AM -0700, Noah Misch wrote:
> >> Yep. I put the tree in the necessary state, and [...]
>
> > https://metacpan.org/dist/IPC-Run is now a fresh release, and
> > https://ports.macports.org/search/?q=ipc-run&name=on shows that version.
>
> That's great news, but apparently there is some lag in new packages
> actually becoming available for download:
>
> $ sudo port selfupdate
> ---> Checking for newer releases of MacPorts
> MacPorts base version 2.11.4 installed,
> MacPorts base version 2.11.4 available.
> ---> MacPorts base is already the latest version
> ---> Updating the ports tree
>
> The ports tree has been updated.
> All installed ports are up to date.
> $ port installed | grep ipc
> p5.34-ipc-run @20231003.0.0_0 (active)
Hmm. I've never used MacPorts, so I'll probably not be an informed
commentator on its release flow. If relevant (probably not):
https://ports.macports.org/port/p5.34-ipc-run/details/ does show missing "Port
Health" for Sequoia (x86_64), Sonoma (arm64), and Sonoma (x86_64). Meanwhile,
https://ports.macports.org/port/p5.34-ipc-run/builds/ shows all builds of this
version happening in a <10min span, with no failures. If there's some "port"
command mode to force an install from source, that might bypass the blockage.
