On 2024-12-04 20:53, Emilio Pozuelo Monfort wrote:
On 04/12/2024 17:52, Drew Parsons wrote:
Looks like britney sorted it out eventually anyway.
If you mean the autopkgtest, that was Graham scheduling tests with
cmake/sid upon my request.
Ah, now the pixies behind the music in the garden
On 04/12/2024 17:52, Drew Parsons wrote:
On 2024-12-04 17:42, Emilio Pozuelo Monfort wrote:
Hi Drew,
On 03/12/2024 16:25, Emilio Pozuelo Monfort wrote:
On 03/12/2024 14:33, Drew Parsons wrote:
All the hypre and petsc uploads for this transition are done,
and packages built against the new ope
On 2024-12-04 17:42, Emilio Pozuelo Monfort wrote:
Hi Drew,
On 03/12/2024 16:25, Emilio Pozuelo Monfort wrote:
On 03/12/2024 14:33, Drew Parsons wrote:
All the hypre and petsc uploads for this transition are done,
and packages built against the new openmpi 5.
Looks like the sundials autopkgt
Hi Drew,
On 03/12/2024 16:25, Emilio Pozuelo Monfort wrote:
On 03/12/2024 14:33, Drew Parsons wrote:
All the hypre and petsc uploads for this transition are done,
and packages built against the new openmpi 5.
Looks like the sundials autopkgtest failure is going to be a blocker, could you
tak
On 03/12/2024 14:33, Drew Parsons wrote:
All the hypre and petsc uploads for this transition are done,
and packages built against the new openmpi 5.
Looks like the sundials autopkgtest failure is going to be a blocker, could you
take a look at it? Some tests are timing out on a few architectur
All the hypre and petsc uploads for this transition are done,
and packages built against the new openmpi 5.
On 30/11/2024 12:40, Drew Parsons wrote:
On 2024-11-29 16:29, Drew Parsons wrote:
On 2024-11-29 16:20, Adrian Bunk wrote:
On Fri, Nov 29, 2024 at 04:10:35PM +0100, Drew Parsons wrote:
...
I'll upload hypre after scalapack and superlu-dist are
rebuilt,
and petsc after mumps.
There is no need
On 2024-11-29 16:29, Drew Parsons wrote:
On 2024-11-29 16:20, Adrian Bunk wrote:
On Fri, Nov 29, 2024 at 04:10:35PM +0100, Drew Parsons wrote:
...
I'll upload hypre after scalapack and superlu-dist are
rebuilt,
and petsc after mumps.
There is no need to wait, since libopenmpi40 breaks libopen
On 2024-11-29 16:20, Adrian Bunk wrote:
On Fri, Nov 29, 2024 at 04:10:35PM +0100, Drew Parsons wrote:
...
I'll upload hypre after scalapack and superlu-dist are
rebuilt,
and petsc after mumps.
There is no need to wait, since libopenmpi40 breaks libopenmpi3t64 the
builds will automatically wait
On Fri, Nov 29, 2024 at 04:10:35PM +0100, Drew Parsons wrote:
>...
> I'll upload hypre after scalapack and superlu-dist are
> rebuilt,
> and petsc after mumps.
There is no need to wait, since libopenmpi40 breaks libopenmpi3t64 the
builds will automatically wait for earlier packages to be rebuilt.
On 2024-11-29 15:38, Emilio Pozuelo Monfort wrote:
If Emilio and Sebastian don't object, I'd like to extend this (petsc)
transition to
hypre 2.32.0
petsc 3.22 + slepc/petsc4py/slepc4py
I can upload them later in the day once the new openmpi is built,
to build new hypre, petsc & friends ra
On 29/11/2024 13:00, Drew Parsons wrote:
On 2024-11-29 07:38, Alastair McKinstry wrote:
On 28/11/2024 19:40, Emilio Pozuelo Monfort wrote:
I think the openmpi40 transition should proceed to clear up the build
issues. mpi-defaults is essentially done, and openmpi-rm won't progress
without the r
On 2024-11-29 07:38, Alastair McKinstry wrote:
On 28/11/2024 19:40, Emilio Pozuelo Monfort wrote:
I think the openmpi40 transition should proceed to clear up the build
issues. mpi-defaults is essentially done, and openmpi-rm won't
progress without the rebuilds. The only issue with openmpi-5.06.
On 28/11/2024 20:00, Drew Parsons wrote:
On 2024-11-28 20:40, Emilio Pozuelo Monfort wrote:
On 28/11/2024 20:13, Alastair McKinstry wrote:
(5) mpi4py fails to build with py3.13 (due to cffi dependency).
Builds ok with 'nocheck' allowing more of the stack to build.
Are you sure? It looks li
On 28/11/2024 19:40, Emilio Pozuelo Monfort wrote:
On 28/11/2024 20:13, Alastair McKinstry wrote:
en filing bugs, doing NMUs and requesting removal for NBS binaries,
and we're at a point I think where we can get rid of openmpi on
armel/armhf/i386. However, the autopkgtest regressions are stil
On 2024-11-28 20:40, Emilio Pozuelo Monfort wrote:
On 28/11/2024 20:13, Alastair McKinstry wrote:
(5) mpi4py fails to build with py3.13 (due to cffi dependency). Builds
ok with 'nocheck' allowing more of the stack to build.
Are you sure? It looks like it was already built with py3.13, see e.g
On 28/11/2024 20:13, Alastair McKinstry wrote:
en filing bugs, doing NMUs and requesting removal for NBS binaries, and we're
at a point I think where we can get rid of openmpi on armel/armhf/i386.
However, the autopkgtest regressions are still an issue for openmpi migration
to testing, and that
en filing bugs, doing NMUs and requesting removal for NBS binaries,
and we're at a point I think where we can get rid of openmpi on
armel/armhf/i386. However, the autopkgtest regressions are still an
issue for openmpi migration to testing, and that I think is blocked on
the libopenmpi40 transit
On 16/11/2024 12:21, Alastair McKinstry wrote:
On 07/11/2024 11:31, Emilio Pozuelo Monfort wrote:
On 01/11/2024 11:43, Emilio Pozuelo Monfort wrote:
On 22/10/2024 08:44, Alastair McKinstry wrote:
On 21/10/2024 13:25, Drew Parsons wrote:
All uploads for this transition are now done.
We're wa
On 07/11/2024 11:31, Emilio Pozuelo Monfort wrote:
On 01/11/2024 11:43, Emilio Pozuelo Monfort wrote:
On 22/10/2024 08:44, Alastair McKinstry wrote:
On 21/10/2024 13:25, Drew Parsons wrote:
All uploads for this transition are now done.
We're waiting for openmpi to be fixed so petsc and reve
On 01/11/2024 11:43, Emilio Pozuelo Monfort wrote:
On 22/10/2024 08:44, Alastair McKinstry wrote:
On 21/10/2024 13:25, Drew Parsons wrote:
All uploads for this transition are now done.
We're waiting for openmpi to be fixed so petsc and reverse dependencies can
build.
Build is done for amd64
On 22/10/2024 08:44, Alastair McKinstry wrote:
On 21/10/2024 13:25, Drew Parsons wrote:
All uploads for this transition are now done.
We're waiting for openmpi to be fixed so petsc and reverse dependencies can
build.
Build is done for amd64 (and i386).
For that reason I suggest triggering th
On 21/10/2024 13:25, Drew Parsons wrote:
All uploads for this transition are now done.
We're waiting for openmpi to be fixed so petsc and reverse dependencies can
build.
Build is done for amd64 (and i386).
For that reason I suggest triggering the last binNMUs, for dolfinx-mpc and
fenicsx-perf
All uploads for this transition are now done.
We're waiting for openmpi to be fixed so petsc and reverse dependencies can
build.
Build is done for amd64 (and i386).
For that reason I suggest triggering the last binNMUs, for dolfinx-mpc and
fenicsx-performance-tests. They should be able to (re)bu
On 2024-10-14 10:39:47 +0200, Drew Parsons wrote:
> basix is rebuilt to deal with the nanobind issue.
>
> A broken new upload of catch2 is blocking dolfinx rebuilds.
> There is also a rogue upload of openmpi 5 which is not making
> this transition simpler.
The upload of openmpi 5 was not a rogue
basix is rebuilt to deal with the nanobind issue.
A broken new upload of catch2 is blocking dolfinx rebuilds.
There is also a rogue upload of openmpi 5 which is not making
this transition simpler.
The nanobind upgrade is interfering with the dolfinx rebuild.
See Bug#1085019
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085019
Actually octave 9.2.0 supporting sundials 7 is already uploaded.
It builds fine, though drops some ode15 support (Bug#1082580) but is
otherwise ready for the transition.
Note that sundials 7 introduces some API changes.
dyssol will need patching (bugs files)
deal.ii and octave have new upstream releases that will need to be uploaded.
opendrop will be easily patched (just needs mpicxx as compiler)
29 matches
Mail list logo
