Your message dated Sat, 17 Oct 2026 19:15:20 +0200
with message-id <E1xI808-00000005tg5-3DsW@gelly>
and subject line Re: Bug#1149728: netgen: autopkgtest needs update for new
version of (open)mpi(ch)
has caused the Debian Bug report #1149728,
regarding netgen: autopkgtest needs update for new version of (open)mpi(ch)
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.)
--
1149728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1149728
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: netgen
Version: 6.2.2606+dfsg1-1
Severity: serious
Tags: sid forky
User: [email protected]
Usertags: needs-update
Control: affects -1 src:mpich src:openmpi
Dear maintainer(s),
With a recent upload of mpich and openmpi the autopkgtest of netgen
fails in testing when that autopkgtest is run with either the binary
packages of mpich or openmpi from unstable. It passes when run with only
packages from testing. In tabular form:
pass fail
mpich from testing 5.0.2-1
netgen from testing 6.2.2606+dfsg1-1
all others from testing from testing
I copied some of the output at the bottom of this report. The
autopkgtest actually doesn't fail because the test fails, but because
there is a deprecation warning on stderr. If you don't care about output
to stderr in the future, you can add the allow-stderr restriction to the
tests.
Currently this regression is blocking the migration of mpich to testing
[1]. Of course, mpich shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in mpich was
intended and your package needs to update to the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from mpich should really add a
versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=mpich
https://ci.debian.net/data/autopkgtest/testing/arm64/n/netgen/76265643/log.gz
260s 260s =============== 214 passed, 114 skipped, 9 deselected in
45.84s ================
261s 261s 261s Run MPI python test
261s ************************************************
261s We have detected that the runtime version
261s of the PMIx library we were given is binary
261s incompatible with the version we were built against:
261s 261s Runtime: 0x70000
261s Build: 0x50009
261s 261s Please update your LD_LIBRARY_PATH to point
261s us to the same PMIx version used to build PRRTE.
261s ************************************************
261s autopkgtest [17:35:21]: test netgen-test-python
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
I think the problem was fixed in OpenMPI 6
--- End Message ---
