Re: external PRRTE library alongside external PMix?

[Drew Parsons <dparsons@emerall.com>]

On 2025-11-12 10:31, Alastair McKinstry wrote:
> On 11/11/2025 12:06, Drew Parsons wrote:
> > On 2025-11-11 10:38, Alastair McKinstry wrote:
> > > Hi Drew
>
> So I've submitted an ITP for PRRTE and started to package it.
>
> But more immediately openmpi 5.0.9 is "officially" released, and it 
> moves to PRRTE 3.0.12 (the latest).
>
> This looks like a trivial bugfix release so I'll upload directly to 
> unstable soon.

Fantastic, thanks Alastair!

Drew


> Regards
>
> Alastair
>
> > > Best regards
> > >
> > > Alastair
> > >
> > > On 10/11/2025 13:52, Drew Parsons wrote:
> > > > Hi Alastair
> > > > (and cc: Debian Science)
> > > >
> > > > I raised our current pmix problem (Bug#1120424, #1120413)
> > > > upstream.
> > > >
> > > > Ralph Castain upstream raises an interesting question,
> > > > https://github.com/openpmix/openpmix/issues/3717#issuecomment-3511548113 
> > > > He suspect PRRTE might be at the heart of the problems we've got
> > > > running in buildd chroots with not internet interface (lo only).
> > > > His recommendation is to package PRRTE separately instead of using
> > > > the bundled source that comes with openmpi, just as we've started 
> > > > doing
> > > > with PMIx.
> > > >
> > > > Would that work for us? Hard to say if it would make MPI packaging
> > > > harder or simpler, but might make it easier to backport upstream 
> > > > patches.
> > > >
> > > > Cheers,
> > > > Drew