[From nobody Thu Oct 22 08:41:07 2026
Received: (at submit) by bugs.debian.org; 25 Sep 2026 09:03:51 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-122.2 required=4.0 tests=ALL_TRUSTED,BAYES_00,
 BODY_INCLUDES_PACKAGE,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,
 DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,HAS_PACKAGE,SPF_HELO_NONE,
 SPF_PASS,USER_IN_DKIM_WELCOMELIST,XMAILER_REPORTBUG autolearn=ham
 autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 14; hammy, 141; neutral, 36; spammy,
 0. spammytokens:
 hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin,
 0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311,
 0.000-+--H*RT:311, 0.000-+--H*RT:108
Return-path: &lt;dparsons@debian.org&gt;
Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]:58516)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from &lt;dparsons@debian.org&gt;) id 1xA1qR-00Dxht-1f
 for submit@bugs.debian.org; Fri, 25 Sep 2026 09:03:51 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; 
 s=smtpauto.stravinsky;
 h=X-Debian-User:Date:Message-ID:Subject:To:From:
 Content-Transfer-Encoding:MIME-Version:Content-Type:Reply-To:Cc:Content-ID:
 Content-Description:In-Reply-To:References;
 bh=uQqEOZpS+hfjI4xwOaxtHRYoQ4lGFZUhghoM30+ZyJU=; b=u35ATQ/aLMSK7+II6DMH+jUFkh
 eH/2S3DquuZuzYKUlAz9+ZYf9+evbPX6/sln9o9UAGdx/YS7rFCreiEr7Emg7vWbDAA3GBLM04nFd
 ZBvhW9VGCBX4laXZ5hHWtqFWSDUJJYwzpcBdVn4eDAJlaF81WnO+5Bkz/xU/nhRwu1bjPv50Ie2M1
 QuaYRmg2IVy90QIX6wMRMZk4/BdmInqifHgcgICuDWYuojKVoEnQT4QmKUBLCra8saBNxpTRhNSzN
 QdGqCil24Lzv3Q7qXFpNTzLPTlNVaSD4Gb3Ycz3bwAg4twyCCkSAt5M3B96WEYGDTLKrNDi5VGNRP
 XNDO9e2w==;
Received: from authenticated-user by stravinsky.debian.org with esmtpsa
 (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from &lt;dparsons@debian.org&gt;)
 id 1xA1qP-005Bw9-0p; Fri, 25 Sep 2026 09:03:50 +0000
Received: from drew by gelly with local (Exim 4.100)
 (envelope-from &lt;dparsons@debian.org&gt;) id 1xA1qN-00000003hKW-1cuQ;
 Fri, 25 Sep 2026 11:03:47 +0200
Content-Type: text/plain; charset=&quot;us-ascii&quot;
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Drew Parsons &lt;dparsons@debian.org&gt;
To: Debian Bug Tracking System &lt;submit@bugs.debian.org&gt;
Subject: test failure due to stderr warning schizo_proxy deprecated by
 personality
Message-ID: &lt;179032702737.878243.4679196997934727383.reportbug@gelly&gt;
X-Mailer: reportbug 13.2.0+nmu1
Date: Fri, 25 Sep 2026 11:03:47 +0200
X-Debian-User: dparsons
Delivered-To: submit@bugs.debian.org

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?
]