Source: mpich
Version: 5.0.1-5
Severity: serious
X-Debbugs-CC: [email protected]
Tags: sid forky
User: [email protected]
Usertags: needs-update
Control: affects -1 src:gcc-defaults

Dear maintainer(s),

With a recent upload of gcc-defaults the autopkgtest of mpich fails in testing when that autopkgtest is run with the binary packages of gcc-defaults from unstable. It passes when run with only packages from testing. In tabular form:

                       pass            fail
gcc-defaults           from testing    1.233
mpich                  from testing    5.0.1-5
all others             from testing    from testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of gcc-defaults to testing [1]. Of course, gcc-defaults shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in gcc-defaults 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 gcc-defaults 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=gcc-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/m/mpich/74064720/log.gz

112s /usr/bin/mpif90: line 395: gfortran-15: command not found
112s Error: Command not found
112s autopkgtest [00:21:37]: test hello2

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to