Your message dated Thu, 22 Oct 2026 09:38:47 +0200
with message-id <E1xJnNv-00000009vGd-1qeM@gelly>
and subject line Re: Bug#1148924 openmpi: test failure due to stderr warning
schizo_proxy deprecated by personality
has caused the Debian Bug report #1148924,
regarding test failure due to stderr warning schizo_proxy deprecated by
personality
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1148924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1148924
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libopenmpi-dev
Version: 5.0.11-2
Severity: important
The current version is causing debci test failure since it is emitting
a warning to stderr:
https://ci.debian.net/packages/o/openmpi/unstable/amd64/76038487/
515s --------------------------------------------------------------------------
515s A deprecated MCA variable value was specified in the environment or
515s on the command line. Deprecated MCA variables should be avoided;
515s they may disappear in future releases.
515s
515s Deprecated variable: schizo_proxy
515s New variable: personality
515s --------------------------------------------------------------------------
This causes openmpi's own debci tests to fail.
It also affects all other packages using openmpi.
The problem can be seen in mpi4py tests at
https://ci.debian.net/data/autopkgtest/unstable/amd64/m/mpi4py/75910556/log.gz
mpi4py is only passing debci circumstantially since it happens to be
using Restrictions: allow-stderr in debian/tests/control
But this is not a good solution in general. Packages without
allow-stderr are failing because of the warning message,
including scifem, netgen, and openmpi itself.
The message says schizo_proxy is being set in the environment, but the
client packages are not setting it explicitly. It must be in the
openmpi configuration. Wherever the variable is being set, can it be
updated, to save the sanity of all the client packages?
--- End Message ---
--- Begin Message ---
fixed 1148924 6.0.0~rc2-2
thanks
This issue seems to be fixed in openmpi 6,
so closing the bug as fixed.
Drew
--- End Message ---
