Hi Drew
On Mon, 12 Oct 2020 at 04:42, Drew Parsons wrote:
> I think petsc 3.13.6+dfsg1-1 needs to be marked again for binNMU
> "Rebuild against MUMPS 5.3.3" on armel, mipsel (i.e. versioned binNMU).
Scheduled, thanks.
Regards
Graham
I uploaded petsc 3.13.6+dfsg1-1 (one of mumps' reverse dependencies) to
unstable in order to clear the way for PETSc 3.14 in experimental.
It built "successfully" against the old mumps on armel and mipsel but
the openmpi inconsistency causes dolfin to FTBFS on these failing
arches.
I think
Hi Alastair, I'm getting a PMIX undefined symbol in new builds of MUMPS
5.3.3 amd armel and mipsel,
see https://buildd.debian.org/status/package.php?p=mumps
The armel log at
https://buildd.debian.org/status/fetch.php?pkg=mumps=armel=5.3.3-2=1601578910=0
reports:
...
mpifort -o c_example
On 2020-09-30 17:38, Sebastian Ramacher wrote:
So let's proceed with the MUMPS 5.3.3 transition on its own and get
the mumps upgrade into the archives
Please go ahead.
Thanks Sebastian.
Interestingly, upstream has just released MUMPS 5.3.4.
And at the same time upstream has just
Control: forwarded -1
https://release.debian.org/transitions/html/auto-mumps.html
Control: tags -1 confirmed
On 2020-09-29 13:48:30, Drew Parsons wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
>
> I wanted to make a
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
I wanted to make a combo transition with superlu-dist 5.3.1 and hypre
2.20. But the hypre upgrade requires superlu-dist 5.3 and
superlu-dist 5.3 FTBFS (see
6 matches
Mail list logo
