# -*- text -*-
#
# Copyright (c) 2020      Intel, Inc.  All rights reserved.
# Copyright (c) 2022      Cisco Systems, Inc.  All rights reserved.
# Copyright (c) 2026      NVIDIA Corporation.  All rights reserved.
# $COPYRIGHT$
#
# Additional copyrights may follow
#
# $HEADER$
#
#
#
[deprecated-converted]
WARNING: A deprecated MPI_Info key was used.

  Deprecated key:   %s
  Corrected key:    %s

We have updated this for you and will proceed. However, this will be treated
as an error in a future release. Please update your application.
#
[deprecated-inform]
WARNING: A deprecated MPI_Info key was used.

  Deprecated option:   %s
  Reason: %s

This has been ignored as it is no longer meaningful. Please update
your application.
#
[deprecated-fail]
WARNING: A deprecated MPI_Info key was used. It is unclear how to update
this option. Please contact the community for how best to resolve this issue.

  Deprecated info key:  %s
  Updated option:   %s
  Reason: %s

We are not able to proceed. Please update your application.
#
[bad-ppr]
The proc-per-resource MPI_Info key is not correct. The value must include both
the number of procs for each resource and the type of resource to be used.

  Specified value:  %s

We are not able to proceed. Please correct your application.
#
[version-mismatch]
The two jobs being connected are running different versions of Open
MPI, which is not a supported configuration:

  This job is:          %s
  The other job is:     %s

Connecting two jobs requires both to be running the same version of
Open MPI. The information the two exchange over the port is internal
to the implementation and has never been compatible across versions.

"The other job is: not stated" means the other job is running a
version old enough that it does not say -- Open MPI v6.0.x or
earlier. Such a version cannot read what this one publishes either,
and may well fail in a less orderly way than this.

We are not able to proceed.
#
[pml-mismatch]
The two jobs being connected selected different point-to-point
messaging layers (PMLs), and cannot exchange messages:

  This job selected:    %s
  The other selected:   %s

Both jobs must select the same PML. This usually means the two were
started with different settings for the "pml" MCA parameter, or in
environments whose available networks led each to a different choice.

We are not able to proceed.
#
[execv-error]

The singleton application was not able to find an executable in your
PATH or in the directory where PRTE was initially installed, and
therefore cannot continue.

For reference, we tried the following command:

  %s

and got the error %s.

This could mean that your PATH or executable name is wrong, or that
you do not have the necessary permissions.  Please ensure that the
executable is able to be found and executed as it is required for
singleton operations.
