Hi,
On 24-04-2025 11:24, Paul Gevers wrote:
On 24-04-2025 10:32, Alastair McKinstry wrote:
My perference was to leave 4.3.0. in unstable, but given the valgrind
issue, it looks like an upload 4.3.0_really4.2.1 is needed. Anyone
think differently?
I agree that a 4.3.0_really4.2.1 looks best
Hi,
On 24-04-2025 10:32, Alastair McKinstry wrote:
My perference was to leave 4.3.0. in unstable, but given the valgrind
issue, it looks like an upload 4.3.0_really4.2.1 is needed. Anyone think
differently?
I agree that a 4.3.0_really4.2.1 looks best at this moment.
Paul
OpenPGP_signatur
(presumably with some substitutions in the source code to get the
appropriate multiarch tuple for the relevant architecture) would be
enough to fix what we're now calling #1102928. I haven't verified that
but it seems plausible.
See also #1088919 and #1089694 which involve packaging changes
Control: clone 1102928 -2
Control: retitle 1102928 mpich: mpi-c.pc no longer available, causing
mpi-defaults autopkgtest regression
Control: retitle -2 mpich: mpi-fort.pc no longer available, causing
mpi-defaults autopkgtest regression
On Wed, 23 Apr 2025 at 10:58:30 +0100, Alastair McKinstry w
On 23/04/2025 10:47, Simon McVittie wrote:
On Sun, 13 Apr 2025 at 13:14:49 +0300, Adrian Bunk wrote:
214s autopkgtest [01:51:54]: test mpi-compile-run-cc-pkgconf-mpi-c:
[---
214s Package mpi-c was not found in the pkg-config search path.
...
This is related to two lines
On Sun, 13 Apr 2025 at 13:14:49 +0300, Adrian Bunk wrote:
214s autopkgtest [01:51:54]: test mpi-compile-run-cc-pkgconf-mpi-c:
[---
214s Package mpi-c was not found in the pkg-config search path.
...
This is related to two lines disappearing from the
libmpich-dev postinst:
Source: buildd=mpich
Version: 4.3.0-5
Severity: serious
X-Debbugs-Cc: Alastair McKinstry
Control: affects src:mpi-defaults
https://tracker.debian.org/pkg/mpich
Issues preventing migration:
∙ ∙ autopkgtest for mpi-defaults/1.18: amd64: No tests, superficial or marked
flaky ♻ (reference ♻), arm64
7 matches
Mail list logo
