Nonexistent mpi.default variable lets port upgrade fail

[David Strubbe]

Discussed and resolved here: https://trac.macports.org/ticket/49669

David

On Thu, Nov 12, 2015 at 3:33 AM, David Evans <devans at macports.org> wrote:

> On 11/11/15 11:36 PM, Marko Käning wrote:
> > Ooops, what does this error suddenly happen?
> >
> > ---
> > --->  Updating MacPorts base sources using rsync
> > MacPorts base version 2.3.4 installed,
> > MacPorts base version 2.3.4 downloaded.
> > --->  Updating the ports tree
> > --->  MacPorts base is already the latest version
> >
> > The ports tree has been updated. To upgrade your installed ports, you
> should run
> >   port upgrade outdated
> > The following installed ports are outdated:
> > kdetoys4                       4.10.5_0 < 4.10.5_1
> > Error: Unable to open port: can't read "mpi.default": no such variable
> > To report a bug, follow the instructions in the guide:
> >     http://guide.macports.org/#project.tickets
> > ---
> >
> > Greets,
> > Marko
> > _______________________________________________
> > macports-dev mailing list
> > macports-dev at lists.macosforge.org
> > https://lists.macosforge.org/mailman/listinfo/macports-dev
> >
>
> The error appears to come from port boost (may be others) which is broken
> (Portfile fails to parse) after
> the recent update to mpi portgroup in r142438.
>
> Dave
>
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20151112/44a2ba98/attachment.html>